Offline 204.93.237.12:28435 checked 7d ago
npc freeze local test
Connect
srv = rust.server("204.93.237.12:28436")
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. 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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 21 Oct, 23:09 UTC7d ago | 0 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 204.93.237.12:28435
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Oct 2026, 23:10 UTC
- hostname
- –
- first seen
- 21 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 · 151 on average | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 176/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 70/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 211/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
How does npc freeze local test compare in the rankings?
Over the last seven days npc freeze local test sits at #15,344 on player hours, in the top 69% of ranked servers.
How full does npc freeze local test run?
Offline now for npc freeze local test, with the last sample 7 days 19 hours ago.
Server data
Which Rust version is npc freeze local test on?
Rust network protocol 2634 and build 167781 on Linux is what npc freeze local test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is npc freeze local test, and is it online now?
Offline now for npc freeze local test, last seen 7 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 21 October 2026.
In which location is npc freeze local test hosted?
There is no region published for npc freeze local test. Rust Data does not look up where the machine stands; it shows where a server says it is. 204.93.237.12:28435 is its address.
Settings and map
Which settings and rules does npc freeze local test run?
The name npc freeze local test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.
What is the map on npc freeze local test?
A procedural map runs on npc freeze local test, generated by the game.
Wipe data
When does npc freeze local test wipe, and how often?
Too few wipes are on record for npc freeze local test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 7 days 20 hours ago.
What is wipe day on npc freeze local test like?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold npc freeze local test, and which filters?
On Rust Data, npc freeze local test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on npc freeze local test hold?
These tags are published by npc freeze local test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to npc freeze local test?
Enter client.connect 204.93.237.12:28435 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.