Offline 157.85.86.101:28871 checked 37d ago
Server Unavailable!
Connect
srv = rust.server("157.85.86.101:28872")
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 17 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 bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Sat 19 Sep, 19:58 UTC39d ago | 1 | NaN | running | 1 |
| 1 | Thu 17 Sep, 16:49 UTC41d ago | 1 | held half | 2.1 days | 1 |
| 2 | Tue 15 Sep, 17:03 UTC43d ago | 3 | NaN | 2 days | 0 |
| 3 | Sun 13 Sep, 19:02 UTC45d ago | 3 | NaN | 1.9 days | 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
4250 · seed 1509017534
- map
- Procedural Map
- size
- 4250
- seed
- 1509017534
Server
srv.info()- address
- 157.85.86.101:28871
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Sep 2026, 19:58 UTC
- hostname
- –
- first seen
- 13 Sep 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 | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 52/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population
How does Server Unavailable! compare in the rankings?
Player hours over seven days put Server Unavailable! at #15,503, in the top 67% of the ranked set.
What population does Server Unavailable! carry?
Offline now for Server Unavailable!, with the last sample 37 days 22 hours ago.
About the server
What is the Rust version on Server Unavailable!?
The build is Rust network protocol 2633 and build 164530 on Linux, run by Server Unavailable!. The protocol has to match before you can join, and Steam does the updating.
How reliable is Server Unavailable!, and is it up?
Server Unavailable! is offline at this refresh; the last response came 37 days 22 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 13 September 2026.
In which location is Server Unavailable! hosted?
For Server Unavailable!, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.86.101:28871 is its address.
Settings and map
Which rules apply on Server Unavailable!, and what settings?
The name Server Unavailable! carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Server Unavailable! selected?
Server Unavailable! runs a procedural map of size 4,250 with seed 1509017534, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does Server Unavailable! wipe, and on what schedule?
Server Unavailable! wipes on no fixed rhythm, so there is nothing to predict. 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 39 days 8 hours ago, and that is the one in play.
On Server Unavailable!, what happens on wipe day?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Where does Server Unavailable! appear among Rust Data lists and filters?
These Rust Data lists include Server Unavailable!: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Server Unavailable!?
The game's server browser reads these tags from Server Unavailable!: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.
How to join
How can I connect to Server Unavailable!?
In Rust, F1 opens the console: type client.connect 157.85.86.101:28871. Launch Rust on this page does the same by opening the game through Steam and connecting.