Offline 68.103.106.192:28015 checked 21d ago
Test Server
Connect
srv = rust.server("68.103.106.192: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 bestTop 72% 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 | Wed 7 Oct, 22:17 UTC21d ago | 0 | NaN | running | 0 |
| 1 | Tue 29 Sep, 22:20 UTC29d ago | 2 | halved by day 1 | 8 days | 1 |
| 2 | Mon 28 Sep, 12:20 UTC31d ago | 1 | NaN | 1.4 days | 0 |
| 3 | Fri 25 Sep, 09:34 UTC34d ago | 0 | NaN | 3.1 days | 0 |
| 4 | Thu 24 Sep, 11:12 UTC35d ago | 0 | NaN | 0.9 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
- 68.103.106.192:28015
- region
- –
- max players
- 200
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 22:17 UTC
- hostname
- –
- first seen
- 22 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 | 171/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/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 · 94 on average | 80/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 253/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 344/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Test Server rank?
Player hours over seven days put Test Server at #15,912, in the top 72% of the ranked set.
How full does Test Server run?
Test Server returns no live count at this refresh, having last been seen 21 days 16 hours ago.
About the server
What is the Rust version on Test Server?
Version Rust network protocol 2634 and build 167058 on Windows is reported by Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Test Server, and is it up?
The latest sample has Test Server offline, with a last sighting 21 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 22 September 2026.
Where does Test Server sit?
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. 68.103.106.192:28015 is its address.
Settings and map
Which settings and rules does Test Server run?
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. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Test Server loaded?
A procedural map runs on Test Server, generated by the game.
Wipe schedule
When does Test Server wipe, and on what schedule?
Test Server wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 21 days 17 hours ago.
On Test Server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 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 0% of recent wipes. The drop under half arrived by day 1 in the other cases.
Tags, lists
Which lists on Rust Data hold Test Server, and which filters?
The Rust Data lists that Test Server fits are: 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?
The game's server browser reads these tags from Test Server: gmrust (Game mode): Rust survival in its standard form; mp200 (Max players): 200 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
How to join
What is the way to join Test Server?
In Rust, F1 opens the console: type client.connect 68.103.106.192:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.