Offline 217.60.240.126:25570 checked 27d ago
Test
Connect
srv = rust.server("217.60.240.126:27017")
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 · 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:32 UTC FW28d ago | 0 | NaN | running | 0 |
| 1 | Mon 28 Sep, 17:53 UTC31d ago | 4 | held half | 3 days | 0 |
| 2 | Sun 13 Sep, 12:14 UTC46d ago | 1 | halved by day 1 | 15.2 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.60.240.126:25570
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:52 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 | 68/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 115/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 38/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 124/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 346/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Test rank?
Rank #15,917 on seven-day player hours for Test, within the top 69% of all ranked servers.
What population does Test carry?
Offline now for Test, with the last sample 27 days 12 hours ago.
Server data
What is the Rust version on Test?
Version Rust network protocol 2634 and build 166494 on Linux is reported by Test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Test, and is it up?
Offline now for Test, last seen 27 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does Test run from?
There is no region published for Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 217.60.240.126:25570 is its address.
Settings and map
What rules and settings are recorded for Test?
The name Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Test loaded?
Test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Test wipe?
No next wipe can be predicted for Test, which wipes at irregular times. 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 28 days 2 hours ago.
On Test, 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. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Tags and filters
Which lists on Rust Data hold Test, and which filters?
These Rust Data lists include Test: 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.
Which meanings do the tags on Test hold?
The game's server browser reads these tags from Test: 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): The server speaks protocol 2634, so match your game version; cs166494 (Build): The server runs build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^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.
Join steps
What is the way to join Test?
The manual route: launch Rust, F1, then client.connect 217.60.240.126:25570. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.