Test Server
Offline 138.199.34.152:28015 checked 38d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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- 213/250
- 129/200
- 26/250
- 14/250
- 23/100
- 32/225
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test Server follow?
To tell the rhythm of Test Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 55 days 5 hours ago the current world was made.
Lists and filters
How should you read the tags on Test Server?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): The server runs game build 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Test Server. 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?
On Rust Metrics, Test Server sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does Test Server sit in the rankings?
Ranking for Test Server: #15,463 on seven-day player hours, top – of all ranked servers.
What is the population on Test Server?
Status for Test Server: offline. Last seen 38 days 2 hours ago.
Server details
Which location does Test Server run from?
No region comes from Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 138.199.34.152:28015.
What Rust version is Test Server on?
Version check: Rust network protocol 2633 and build 162929 on Windows, run by Test Server. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Test Server, and is it online?
Reading: offline. Test Server last answered 38 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 September 2026, recorded by Rust Metrics.
Settings and map
How is Test Server configured, and what rules are in force?
Check: gather rate. The name Test Server does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.
Which map is live on Test Server?
Procedural map on Test Server, made by the game's generator.
How to join
How can you get onto Test Server?
Check: join. Open Rust, press F1, then enter client.connect 138.199.34.152:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.