Test
Offline 85.193.35.184:28015 checked 31d 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 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- 328/375
- 215/250
- 38/250
- 30/250
- 56/100
- 74/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 44 days 8 hours ago the current world was made.
Tag meanings
How should you read the tags on Test?
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): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Test appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does Test sit in the rankings?
Ranking for Test: #16,956 on seven-day player hours, top 71% of all ranked servers.
What is the population on Test?
Status for Test: offline. Last seen 31 days 4 hours ago.
Server
Where does Test sit?
Reading: location. Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 85.193.35.184:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Test reports offline. The last reading came 31 days 4 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 21 September 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
No gather rate appears in the name: Test. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
Check: map. Procedural, generated by the game, on Test.
Connection
How can you get onto Test?
To join: start Rust, press F1 and type client.connect 85.193.35.184:28015. Or press Launch Rust here and Steam opens the game and connects you.