Offline 122.57.114.209:28015 checked 16d ago
TEST
Connect
srv = rust.server("122.57.114.209: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 best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 122.57.114.209:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 09:06 UTC
- hostname
- –
- first seen
- 13 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 · 149 on average | 167/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 70/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TEST rank?
Over the last seven days TEST sits at #13,213 on player hours, in the top 61% of ranked servers.
What population does TEST carry?
Offline now for TEST, with the last sample 16 days ago.
Server data
What Rust version does TEST run?
Rust network protocol 2634 and build 167584 on Windows is what TEST runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST, and is it up?
The latest sample has TEST offline, with a last sighting 16 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 October 2026.
In which location is TEST hosted?
No region is published by TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 122.57.114.209:28015.
Settings and map
Which settings and rules does TEST run?
No gather rate appears in the name: TEST. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on TEST?
TEST runs a procedural map, which the game generates.
Wipe data
When does TEST wipe, and on what schedule?
The record for TEST holds too few wipes to show a rhythm. 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 16 days 3 hours ago.
Tags, lists
Where does TEST appear among Rust Data lists and filters?
The Rust Data lists that TEST fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TEST?
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): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to TEST?
Enter client.connect 122.57.114.209:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.