Offline 185.216.144.73:28080 checked 25d ago
Unstable Rust
Connect
srv = rust.server("185.216.144.73: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 22 Sep. 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 best
Top 71% 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 21 Sep, 20:17 UTC37d 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
3000 · seed 69420
- map
- Procedural Map
- size
- 3000
- seed
- 69420
Server
srv.info()- address
- 185.216.144.73:28080
- region
- –
- max players
- 120
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Sep 2026, 20:17 UTC
- hostname
- –
- first seen
- 21 Sep 2026
About this server · in its own words
print(srv.description)
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 · 151 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 191/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 96/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 234/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Population data
How does Unstable Rust compare in the rankings?
Player hours over seven days put Unstable Rust at #16,009, in the top 71% of the ranked set.
How many players does Unstable Rust hold at once?
Unstable Rust returns no live count at this refresh, having last been seen 25 days 5 hours ago.
Server facts
Which Rust version is Unstable Rust on?
The build is Rust network protocol 2633 and build 164530 on Windows, run by Unstable Rust. Joining needs the same protocol on your game; Steam handles the update.
Is Unstable Rust up, and what does its uptime show?
Unstable Rust is offline at this refresh; the last response came 25 days 5 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 21 September 2026.
In which location is Unstable Rust hosted?
No region is published by Unstable Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 185.216.144.73:28080.
Settings and map
What rules and settings are recorded for Unstable Rust?
You will not find a gather rate in the string Unstable Rust. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Unstable Rust selected?
Unstable Rust runs a procedural map of size 3,000 with seed 69420, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Unstable Rust wipe, and how often?
The record for Unstable Rust holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 37 days 21 hours ago, and that is the one in play.
On Unstable Rust, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold Unstable Rust, and which filters?
The Rust Data lists that Unstable Rust fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Unstable Rust?
These tags are published by Unstable Rust and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp120 (Max players): Slot count: 120; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to Unstable Rust?
In Rust, F1 opens the console: type client.connect 185.216.144.73:28080. Launch Rust on this page does the same by opening the game through Steam and connecting.