Test
Offline 77.83.246.143:28015 checked 33d 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- 107/500
- 122/100
- 182/225
- 60/700
- 5/200
- 24/1000
Quick answers
from the figures on this pageWipe schedule
How often does Test wipe, and when?
To tell the rhythm of Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 68 days 1 hours ago.
Tag meanings
Which tags does Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; v2556 (Protocol): Match the game version: protocol 2556 is required; cs104071 (Build): Build 104071; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $reu2 (Region code): eu2 is the region code on record; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Test. 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?
These Rust Metrics lists carry Test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o.
Occupancy
Where does Test sit in the rankings?
Ranking for Test: #16,503 on seven-day player hours, top 71% of all ranked servers.
What is the population on Test?
Reading for Test: offline at this moment; last seen 33 days 11 hours ago.
Operator and location
Where does Test sit?
Reading: location. Test gives no region, with region code eu2. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 77.83.246.143:28015.
What Rust version is Test on?
Rust network protocol 2556 and build 104071 on Windows is the build Test runs. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Check: connection. Test is offline at this moment. Last contact was 33 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 25 September 2026.
Map and rules
How is Test configured, and what rules are in force?
No gather rate appears in the name: Test. No group limit is published. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Check: map. Procedural, generated by the game, on Test.
Connection
What do you do to join Test?
To join: start Rust, press F1 and type client.connect 77.83.246.143:28015. Or press Launch Rust here and Steam opens the game and connects you.