Offline 168.100.160.35:28039 checked 7d ago
Test Server
Connect
srv = rust.server("168.100.160.35:28031")
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 · 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 | Mon 5 Oct, 16:18 UTC23d 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
3500 · seed 1331288570
- map
- Procedural Map
- size
- 3500
- seed
- 1331288570
Server
srv.info()- address
- 168.100.160.35:28039
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 16:18 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 · 150 on average | 74/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 | 112/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 40/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 12/1000 |
Quick answers
From the figures on this page.
Population
What position does Test Server take in the server rankings?
Player hours over seven days put Test Server at #15,432, in the top 69% of the ranked set.
How full does Test Server run?
Test Server returns no live count at this refresh, having last been seen 7 days 17 hours ago.
Server facts
What Rust version does Test Server run?
Rust network protocol 2634 and build 167781 on Linux is what Test Server runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Test Server, and is it up?
Test Server is offline at this refresh; the last response came 7 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is Test Server hosted?
There is no region published for Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 168.100.160.35:28039.
Map and rules
Which rules apply on Test Server, and what settings?
The name Test Server carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and 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. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Test Server loaded?
Size 3,500, seed 1331288570: the procedural map on Test Server, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
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. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 23 days 15 hours ago.
What is wipe day on Test Server like?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which Rust Data filters and lists contain Test Server?
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?
Read by the game's server browser, the tags Test Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
How to join
How can I connect to Test Server?
The manual route: launch Rust, F1, then client.connect 168.100.160.35:28039. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.