Test Server
Offline 68.103.106.192:38015 checked 12d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 6/ 100
- 85/ 400
- 46/ 245
- 121/ 100
- 129/ 1000
- 14/ 700
Quick answers
Tags and listings
Where does Test Server appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Test Server are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on Test Server?
gmrust (Game mode): This is the standard Rust survival experience; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166722 (Build): The build number is 166722; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): Plugins are handled by Carbon — that is the tag list Test Server puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Where can you find Test Server?
Test Server does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 68.103.106.192:38015.
Is Test Server up, and how often does it stay online?
Test Server is down at the moment; it was last up 12 days 12 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 1 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Test Server?
On Windows, Test Server runs Rust network protocol 2634 and build 166722. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
How often does Test Server wipe?
The wipes recorded for Test Server are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 22 days 16 hours.
Rules and settings
What settings are in place on Test Server?
Its name does not state a gather rate for Test Server. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Carbon plugins are running here. The server runs Valve's anti-cheat, VAC.
Which map is active on Test Server?
A procedural map, generated by the game, is in play on Test Server.
Population
Is Test Server busy?
Test Server was last seen 12 days 12 hours ago and is offline as you read this.
What's Test Server's rank among Rust servers?
For player hours in the last seven days, Test Server ranks #15,982, within the top 71% of ranked servers.
Getting in
What's the way to join Test Server?
Open Rust and press F1, then type client.connect 68.103.106.192:38015. Alternatively, click Launch Rust on this page to join via Steam.