Offline 185.207.214.176:35000 checked 28d ago
test
Connect
srv = rust.server("185.207.214.176:35001")
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 best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. # The force wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 243/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 261/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 106 on average | 76/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 59 on average | 24/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 42/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 46 on average | 53/250 |
Quick answers
From the figures on this page.
Population
How does test compare in the rankings?
Player hours over seven days put test at #16,275, in the top 69% of the ranked set.
How full does test run?
The current row shows test offline; the last response was 28 days 4 hours ago.
Server data
Which Rust version is test on?
The build is Rust network protocol 2633 and build 163794 on Windows, run by test. Joining needs the same protocol on your game; Steam handles the update.
Is test up, and what does its uptime show?
The latest sample has test offline, with a last sighting 28 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
In which location is test hosted?
No region is published by test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 185.207.214.176:35000 is its address.
Rules, settings, map
Which settings and rules does test run?
No gather rate appears in the name: test. The group limit sits at the default of 8 players. Game mode pve, with this note: player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has test selected?
The game generates the map on test: procedural, size 4,500, seed 46464646. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe schedule
When does test wipe, and on what schedule?
An estimate from the force wipe gives test's next wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 56 days 3 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
Tags, lists
Which Rust Data filters and lists contain test?
The Rust Data lists that test fits are: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
How should you read the server tags on test?
Read by the game's server browser, the tags test publishes are: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): Slot count: 0; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to test?
Enter client.connect 185.207.214.176:35000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://rust-z.gamestores.app/ is the website recorded for it.