Test
Offline 46.138.157.237:28015 checked 14d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 61% 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 pageReset cycle
How often does Test wipe, and when?
Its rhythm cannot be told from the wipes of Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 20 days 21 hours ago the current world was made.
Tag meanings
How should you read the tags on Test?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Test?
On Rust Metrics, Test sits in these lists: 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.
Player count
What position does Test hold among Rust servers?
Ranking for Test: #13,072 on seven-day player hours, top 61% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 14 days 20 hours ago.
Server
Which location does Test run from?
No region comes from Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 46.138.157.237:28015.
What Rust version is Test on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by Test. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is Test, and is it online now?
Check: connection. Test is offline at this moment. Last contact was 14 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 9 October 2026.
Settings and map
What settings and rules apply on Test?
Reading the name gives no gather rate for Test. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Check: map. Procedural, generated by the game, on Test.
Join
What do you do to join Test?
Check: join. Open Rust, press F1, then enter client.connect 46.138.157.237:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.