TEST
Offline 185.107.125.210:28015 checked 43d 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 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- 427/500
- 455/475
- 975/1000
- 60/100
- 990/1000
- 30/250
Quick answers
from the figures on this pageWipe timing
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. 58 days ago the current world was made.
Lists and filters
Which tags does TEST carry, and what do they mean?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Your game must run protocol 2632 to get in; cs162434 (Build): Build 162434; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TEST?
These Rust Metrics lists carry TEST: 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.
Occupancy
Where does TEST sit in the rankings?
Ranking for TEST: #15,498 on seven-day player hours, top – of all ranked servers.
What player count does TEST carry?
Status for TEST: offline. Last seen 43 days 3 hours ago.
Server
Where does TEST sit?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.107.125.210:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2632 and build 162434 on Windows, run by TEST. To get in, your game needs the same protocol; Steam applies the update.
Is TEST up, and how often does it stay up?
Reading: offline. TEST last answered 43 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.
Rules and settings
What settings and rules apply on TEST?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. 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. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
The game generates a procedural map for TEST.
Join
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 185.107.125.210:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.