Offline 45.157.118.153:28015 checked 47m ago
Rust 170 Devblog
Connect
srv = rust.server("45.157.118.153:28015")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 37% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 23:28 UTC2d ago | 1 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())Map
4000 · seed 170- map
- Procedural Map
- size
- 4000
- seed
- 170
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 34/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 11/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 2/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Rust 170 Devblog rank?
Over the last seven days Rust 170 Devblog sits at #8,143 on player hours, in the top 37% of ranked servers.
How full does Rust 170 Devblog run?
Rust 170 Devblog returns no live count at this refresh, having last been seen 47 minutes ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 16:00 UTC is the busiest, at 1 players.
Server data
How smoothly does Rust 170 Devblog run?
Averaged over 48 hours: 257 server fps, never under 226. The entity count peaked at 36,565, covering buildings, deployables and the rest of the world. Memory peaked at 539 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does Rust 170 Devblog run?
Rust network protocol 2001 on Windows is what Rust 170 Devblog runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Rust 170 Devblog, and is it online now?
The latest sample has Rust 170 Devblog offline, with a last sighting 47 minutes ago. The uptime it reports puts the last restart about 5 hours ago. Uptime of 21% across the last 2 full days: 10 hours of 48. Its earliest recorded date in Rust Data is 26 October 2026.
Which location does Rust 170 Devblog run from?
No region is published by Rust 170 Devblog. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 45.157.118.153:28015.
Settings and map
Which rules apply on Rust 170 Devblog, and what settings?
No gather rate appears in the name: Rust 170 Devblog. No group limit is published. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. VAC is running: Valve's anti-cheat is on.
Which map has Rust 170 Devblog selected?
Rust 170 Devblog runs a procedural map of size 4,000 with seed 170, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does Rust 170 Devblog wipe, and how often?
The record for Rust 170 Devblog holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 2 days 4 hours ago.
What is wipe day on Rust 170 Devblog like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold Rust 170 Devblog, and which filters?
On Rust Data, Rust 170 Devblog appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Last wipe: In the last 3 days.
How should you read the server tags on Rust 170 Devblog?
Read by the game's server browser, the tags Rust 170 Devblog publishes are: mp200 (Max players): Slot count: 200; v2001 (Protocol): The server speaks protocol 2001, so match your game version; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): The Modded section lists it, because plugins or settings change the game; h6de18208 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; stok (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Rust 170 Devblog?
In Rust, F1 opens the console: type client.connect 45.157.118.153:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.