Offline 209.87.167.200:28015 checked 46d ago
Test Server
Connect
srv = rust.server("209.87.167.200:28017")
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 bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 209.87.167.200:28015
- region
- –
- max players
- 200
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 05:02 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 · 149 on average | 31/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 19/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 55/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 254/260 |
Quick answers
From the figures on this page.
Population
How many players does Test Server hold at once?
Test Server returns no live count at this refresh, having last been seen 46 days 17 hours ago.
Server facts
What is the Rust version on Test Server?
Rust network protocol 2633 and build 163794 on Windows is what Test Server runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Test Server, and is it online now?
The latest sample has Test Server offline, with a last sighting 46 days 17 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Test Server run from?
For Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 209.87.167.200:28015 is its address.
Map and rules
What rules and settings are recorded for Test Server?
You will not find a gather rate in the string Test Server. No custom cap; the default of 8 players per group stands. Recorded as survival, 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. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Test Server selected?
The game generates its map: procedural, on Test Server.
Wipe data
When does Test Server wipe, and how often?
A rhythm cannot be read from the wipes of Test Server on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 55 days 18 hours ago.
Tags, lists
Which lists on Rust Data hold Test Server, and which filters?
These Rust Data lists include Test Server: 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 Test Server?
The game's server browser reads these tags from Test Server: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
What is the way into Test Server?
In Rust, F1 opens the console: type client.connect 209.87.167.200:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.