Test Server
Offline 138.199.34.155:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 204/250
- 123/200
- 25/250
- 14/250
- 25/100
- 30/225
Quick answers
from the figures on this pageWipe schedule
How often does Test Server wipe, and when?
To tell the rhythm of Test Server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 55 days 5 hours ago.
Tags
How should you read the tags on Test Server?
These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Test Server?
Rust Metrics lists featuring Test Server: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does Test Server sit in the rankings?
Player hours over seven days put Test Server at #13,334, in the top – of all ranked servers.
What player count does Test Server carry?
Test Server is not responding; status offline, last seen 43 days 2 hours ago.
Server
Which location does Test Server run from?
Reading: location. Test Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 138.199.34.155:28015.
What Rust version is Test Server on?
Reading: Test Server, Rust network protocol 2633 and build 162929, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test Server, and is it online now?
Reading: offline. Test Server last answered 43 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 15 September 2026.
Rules and settings
How is Test Server configured, and what rules are in force?
Reading the name gives no gather rate for Test Server. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.
Which map is live on Test Server?
Procedural map on Test Server, made by the game's generator.
How to join
What do you do to join Test Server?
Press F1 in Rust and enter client.connect 138.199.34.155:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.