Test
Offline 31.70.149.136:28015 checked 36d 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 bestWipe 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- 650/700
- 45/250
- 87/250
- 365/400
- 165/200
- 157/225
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 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 54 days ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163493 (Build): The server runs game build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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?
Rust Metrics lists featuring 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.
Player count
What position does Test hold among Rust servers?
Ranking for Test: #13,280 on seven-day player hours, top – of all ranked servers.
What player count does Test carry?
Test is not responding; status offline, last seen 36 days 23 hours ago.
Operator and location
What location is Test hosted in?
No region comes from Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 31.70.149.136:28015.
What Rust version is Test on?
Version check: Rust network protocol 2633 and build 163493 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?
Test reports offline. The last reading came 36 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 September 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. 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. 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.
What map is Test on?
Check: map. Procedural, generated by the game, on Test.
Connection
What do you do to join Test?
Check: join. Open Rust, press F1, then enter client.connect 31.70.149.136:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.