Offline 106.219.122.121:28015 checked 38d ago
Solo Test Server
Connect
srv = rust.server("106.219.122.121:28016")
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 67% 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 21 Sep, 17:30 UTC38d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 106.219.122.121:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Sep 2026, 17:30 UTC
- hostname
- –
- first seen
- 21 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 · 151 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 201/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 79/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 229/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 351/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Solo Test Server rank?
Over the last seven days Solo Test Server sits at #15,482 on player hours, in the top 67% of ranked servers.
How full does Solo Test Server run?
Offline now for Solo Test Server, with the last sample 38 days ago.
About the server
What Rust version does Solo Test Server run?
Rust network protocol 2633 and build 164530 on Windows is what Solo Test Server runs. Steam updates your game for you, but the protocol must match to join.
Is Solo Test Server up, and what does its uptime show?
Offline now for Solo Test Server, last seen 38 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 21 September 2026.
Where does Solo Test Server sit?
No region is published by Solo Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 106.219.122.121:28015.
Rules, settings, map
What rules and settings are recorded for Solo Test Server?
The name Solo Test Server carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Solo Test Server loaded?
Solo Test Server runs a procedural map, which the game generates.
Wipe schedule
On what schedule does Solo Test Server wipe?
A rhythm cannot be read from the wipes of Solo Test Server on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 38 days ago, and that is the one in play.
What is wipe day on Solo Test Server like?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold Solo Test Server, and which filters?
The Rust Data lists that Solo Test Server fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Solo Test Server hold?
Read by the game's server browser, the tags Solo Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. 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.
Connecting
How can I connect to Solo Test Server?
Enter client.connect 106.219.122.121:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.