Test
Offline 94.243.10.136:28015 checked 30d 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- 616/700
- 41/250
- 76/250
- 316/400
- 140/200
- 138/225
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
To tell the rhythm of Test, too few of its wipes 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 in play was created 30 days 20 hours ago.
Tags
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Test appear in Rust Metrics lists and filters?
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.
Player count
Where does Test sit in the rankings?
Ranking for Test: #15,852 on seven-day player hours, top 67% of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 30 days 19 hours ago.
Operator and location
Where does Test sit?
No region comes from Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 94.243.10.136:28015.
What Rust version is Test on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by Test. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Check: connection. Test is offline at this moment. Last contact was 30 days 19 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 27 September 2026.
Settings and map
What settings and rules apply on Test?
Check: gather rate. The name Test does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
Check: map. Procedural, generated by the game, on Test.
Join
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 94.243.10.136:28015. Or press Launch Rust here and Steam opens the game and connects you.