Test Server
Offline 82.131.186.135:28088 checked 36d 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 bestTop 67% 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageWipe timing
How often does Test Server wipe, and when?
To tell the rhythm of Test Server, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 53 days 2 hours ago.
Lists and filters
How should you read the tags on Test Server?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Game build reading: 163207; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Test Server appear in Rust Metrics lists and filters?
These Rust Metrics lists carry 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 #15,443, in the top 67% of all ranked servers.
How full does Test Server get?
Test Server is not responding; status offline, last seen 36 days ago.
Operator and location
Where does Test Server sit?
No region comes from Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 82.131.186.135:28088.
What Rust version is Test Server on?
Version check: Rust network protocol 2633 and build 163207 on Linux, run by Test Server. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is Test Server, and is it online now?
Test Server reports offline. The last reading came 36 days 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?
No gather rate appears in the name: Test Server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Join
What do you do to join Test Server?
To join: start Rust, press F1 and type client.connect 82.131.186.135:28088. Or press Launch Rust here and Steam opens the game and connects you.