Online 193.34.77.22:28015 checked 11m ago
Test Server
Connect
srv = rust.server("193.34.77.22: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 63% 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 1, 47 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 11:31 UTC24d ago | 1 | 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
- 193.34.77.22:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:31 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 · 155 on average | 155/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 190/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 120/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 51/1000 |
Quick answers
From the figures on this page.
Population data
How does Test Server compare in the rankings?
Player hours over seven days put Test Server at #14,093, in the top 63% of the ranked set.
How many players does Test Server hold at once?
The sample now reads 0 players for Test Server, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 21:00 UTC, averaging 0 players.
About the server
What is the Rust version on Test Server?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Test Server. Steam updates your game for you, but the protocol must match to join.
How reliable is Test Server, and is it up?
The current sample puts Test Server online. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 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 193.34.77.22:28015.
Map and rules
What rules and settings are recorded for Test Server?
You will not find a gather rate in the string Test Server. The group limit sits at the default of 8 players. survival is the game mode here, and 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 Carbon. VAC is not running; Valve's anti-cheat is off.
What is the map on Test Server?
A procedural map runs on Test Server, generated by the game.
Wipe schedule
On what schedule does Test Server wipe?
The record for Test Server holds too few wipes to show a rhythm. 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 24 days 22 hours ago, and that is the one in play.
On Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 47 hours after it began.
Tags and filters
Where does Test Server appear among Rust Data lists and filters?
These Rust Data lists include Test Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Test Server?
These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Test Server?
In Rust, F1 opens the console: type client.connect 193.34.77.22:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.