Test
Offline 46.138.98.204:28015 checked 12d 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 59% 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 schedule
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. 20 days 22 hours ago the current world was made.
Tag meanings
How should you read the tags on Test?
Tags published by Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Test: 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.
Population
Where does Test sit in the rankings?
Ranking for Test: #12,839 on seven-day player hours, top 59% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 12 days 22 hours ago.
Server details
Where does Test sit?
Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.138.98.204:28015.
What Rust version is Test on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by Test. Matching protocol is required to join. Let Steam update your game.
Is Test up, and how often does it stay up?
Reading: offline. Test last answered 12 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 October 2026.
Settings and map
What settings and rules apply on Test?
Check: gather rate. The name Test does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. 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?
The game generates a procedural map for Test.
How to join
What do you do to join Test?
To join: start Rust, press F1 and type client.connect 46.138.98.204:28015. Or press Launch Rust here and Steam opens the game and connects you.