test
Offline 47.93.210.25:28015 checked 35d 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 67% 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- 330/300
- 22/250
- 19/250
- 200/200
- 97/200
- 31/100
Quick answers
from the figures on this pageReset cycle
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. 53 days 15 hours 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: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): Build 162929; 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. 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.
Population
What position does test hold among Rust servers?
Ranking for test: #15,497 on seven-day player hours, top 67% of all ranked servers.
How full does test get?
Status for test: offline. Last seen 35 days 3 hours ago.
Server
Which location does test run from?
No region tag on test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 47.93.210.25:28015.
What Rust version is test on?
Reading: test, Rust network protocol 2633 and build 162929, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is test up, and how often does it stay up?
test reports offline. The last reading came 35 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 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, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is test on?
Check: map. Procedural, generated by the game, on test.
How to join
How do you connect to test?
To join: start Rust, press F1 and type client.connect 47.93.210.25:28015. Or press Launch Rust here and Steam opens the game and connects you.