Statistical profileOnline
Rust 170 Devblog
45.157.118.153:28015 checked 8m ago
Connect to this server
1. Main points
Players now
0/ 200
0% full
7-day average
1
peak 1
Rank
#8,143
top 37%
Last wipe
2d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 0 players on it, 0% of its 200 slots.
- Over the last seven days it averaged 1 players, with a peak of 1.
- It ranks #8,143 of all ranked servers, the top 37%, on player hours over the last seven days.
- Its current map went up 2d ago.
2. Players
Figure 1: Players on Rust 170 Devblog
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 37% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 23:28 UTC2d ago | 1 | – | running | 0 |
Notes
- Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below.
- A new world less than six hours after a wipe is a restart, not a wipe of its own.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Rust 170 Devblog
4000 · seed 170
8. Server characteristics
Table 3: Characteristics of Rust 170 Devblog
What the server publishes and what was recorded
| Address | 45.157.118.153:28015 |
|---|---|
| Region | – |
| Max players | 200 |
| Group limit | not published |
| Wipe schedule | – |
| Last wipe | 26 Oct 2026, 23:28 UTC |
| Hostname | – |
| First seen | 26 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 153 on average | 36 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 56 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3 / 1000 |
10. Quick answers
From the figures on this page.
Wipe details
When does Rust 170 Devblog wipe, and how often?
Too few wipes of Rust 170 Devblog are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 2 days 5 hours ago.
What should you expect on wipe day at Rust 170 Devblog?
Recent wipes drew an average peak of 1 players. 0 hours after the latest wipe, the crowd peaked.
About the server
Is Rust 170 Devblog up, and how well has it held up?
This release records Rust 170 Devblog as online. The uptime it reports puts the last restart at about 5 hours ago. 10 of 48 hours on across the last 2 full days gives an uptime of 21%. The first sighting of it by Rust Census was on 26 October 2026.
How well does Rust 170 Devblog perform?
Average server fps over the last 48 hours was 257, with a low of 226. The world carried up to 36,565 entities, including buildings, deployables and all else. The peak memory use recorded was 539 MB. Players feel low fps and a rising entity count as lag.
Which location does Rust 170 Devblog run from?
No region is given by Rust 170 Devblog. Rust Census does not look up where the machine stands; it shows where a server says it is. 45.157.118.153:28015 is its address.
On which Rust version does Rust 170 Devblog operate?
Rust network protocol 2001 on Windows is the version Rust 170 Devblog runs. Steam updates your game for you, but it has to be on the same protocol to join.
Player counts
What are the current player figures for Rust 170 Devblog?
Rust 170 Devblog stands at 0 players from 200 slots in this release. This release records a seven-day average of 1 players and a peak of 1. An average of 1 players was recorded at 16:00 UTC, the busiest hour of the last 48.
How does Rust 170 Devblog compare with other servers in the rankings?
The rank for Rust 170 Devblog is #8,143 on seven-day player hours, in the top 37% of ranked servers.
Lists and tags
On Rust Census, which lists and filters carry Rust 170 Devblog?
These Rust Census lists include Rust 170 Devblog: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Last wipe: In the last 3 days.
Which meanings do the tags on Rust 170 Devblog carry?
These are the tags Rust 170 Devblog publishes for the game's server browser to read: mp200 (Max players): The server holds 200 slots; v2001 (Protocol): Your game must run protocol 2001 to join; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Plugins or settings alter the game on this modded server; h6de18208 (Custom tag): The tag is custom: it was set by the owner or by a plugin; stok (Custom tag): The tag is custom: it was set by the owner or by a plugin. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Map and rules
Which map is in use on Rust 170 Devblog?
Rust 170 Devblog runs a procedural map of size 4,000 with seed 170, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.
What settings and rules have been listed for Rust 170 Devblog?
The name of Rust 170 Devblog carries no gather rate. No group limit is published. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. The server runs VAC, Valve's anti-cheat.
How to join
What steps are needed to join Rust 170 Devblog?
Enter client.connect 45.157.118.153:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asoxide,modded,mp200,v2001,h6de18208,stok
Game
mp200 | Max players The server holds 200 slots. |
|---|---|
v2001 | Protocol Your game must run protocol 2001 to join. |
Mods and access
oxide | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
modded | Modded Plugins or settings alter the game on this modded server. |
Other
h6de18208 | Custom tag The tag is custom: it was set by the owner or by a plugin. |
|---|---|
stok | Custom tag The tag is custom: it was set by the owner or by a plugin. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.