Test
Offline 31.76.113.156:28015 checked 11d 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 70% 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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
The rhythm of Test's wipes cannot be told yet: too few 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 59 days 13 hours ago.
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; mp1 (Max players): 1 slots in total; v2556 (Protocol): Your game must run protocol 2556 to get in; cs104046 (Build): Build 104046; ptrak (Networking): Network layer: RakNet, the standard for the game; $rfra (Region code): The code for this server's region is fra; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?
These Rust Metrics lists carry Test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o.
Occupancy
Where does Test sit in the rankings?
Ranking for Test: #15,153 on seven-day player hours, top 70% of all ranked servers.
What is the population on Test?
Status for Test: offline. Last seen 11 days 20 hours ago.
Server
What location is Test hosted in?
No region comes from Test, and its region code is fra. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 31.76.113.156:28015.
What Rust version is Test on?
Rust network protocol 2556 and build 104046 on Windows is the build Test runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 11 days 20 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 16 October 2026.
Settings and map
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. The group limit is not published. 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: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Procedural map on Test, made by the game's generator.
Connection
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 31.76.113.156:28015. Or press Launch Rust here and Steam opens the game and connects you.