Test Server
Offline 138.199.34.146:28015 checked 41d 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- 164/250
- 170/200
- 18/250
- 15/250
- 14/100
- 76/200
Quick answers
from the figures on this pageWipe schedule
How often does Test Server wipe, and when?
The rhythm of Test Server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 55 days 10 hours ago.
Tag meanings
Which tags does Test Server carry, and what do they mean?
Tags published by Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): Game build reading: 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test Server appear in Rust Metrics lists and filters?
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
What position does Test Server hold among Rust servers?
Player hours over seven days put Test Server at #13,264, in the top – of all ranked servers.
How full does Test Server get?
Test Server is not responding; status offline, last seen 41 days 5 hours ago.
Operator and location
Where does Test Server sit?
No region tag on Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 138.199.34.146:28015.
What Rust version is Test Server on?
Rust network protocol 2633 and build 162929 on Windows is the build Test Server runs. To get in, your game needs the same protocol; Steam applies the update.
Is Test Server up, and how often does it stay up?
Reading: offline. Test Server last answered 41 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 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. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.
What map is Test Server on?
Check: map. Procedural, generated by the game, on Test Server.
Join
What do you do to join Test Server?
Check: join. Open Rust, press F1, then enter client.connect 138.199.34.146:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.