TEST
Offline 139.100.251.67:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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- 527/550
- 419/450
- 66/250
- 73/250
- 53/100
- 181/200
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 40 days 21 hours ago the current world was made.
Tags
How should you read the tags on TEST?
Tags published by TEST, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; 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?
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.
Player count
Where does TEST sit in the rankings?
Ranking for TEST: #15,027 on seven-day player hours, top – of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 40 days 5 hours ago.
Server
What location is TEST hosted in?
No region comes from TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 139.100.251.67:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by TEST. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on TEST, and is it online?
TEST reports offline. The last reading came 40 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 18 September 2026.
Map and rules
What rules does TEST enforce, and what are its settings?
No gather rate appears in the name: TEST. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.
What map is TEST on?
The game generates a procedural map for TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 139.100.251.67:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.