Test
Offline 46.48.248.134:28015 checked 27d 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 60% 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- 241/275
- 20/250
- 18/250
- 162/200
- 65/200
- 36/100
Quick answers
from the figures on this pageWipe schedule
When does Test wipe?
To tell the rhythm of Test, 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 30 days ago.
Tags
How should you read the tags on Test?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs165982 (Build): The server runs game build 165982; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
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.
Population
Where does Test sit in the rankings?
Ranking for Test: #14,465 on seven-day player hours, top 60% of all ranked servers.
How full does Test get?
Reading for Test: offline at this moment; last seen 27 days 23 hours ago.
Server
Where does Test sit?
No region comes from Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 46.48.248.134:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 165982, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Check: connection. Test is offline at this moment. Last contact was 27 days 23 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 28 September 2026.
Map and rules
How is Test configured, and what rules are in force?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; 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.
Which map is live on Test?
The game generates a procedural map for Test.
Join
What do you do to join Test?
Check: join. Open Rust, press F1, then enter client.connect 46.48.248.134:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.