TEST
Offline 212.3.149.11:28015 checked 27d 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 bestTop 66% 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- 229/250
- 14/250
- 18/250
- 145/200
- 44/200
- 40/100
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
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. The world in play was created 27 days 14 hours ago.
Lists and filters
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): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under 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?
Player hours over seven days put TEST at #15,705, in the top 66% of all ranked servers.
What player count does TEST carry?
Status for TEST: offline. Last seen 27 days 14 hours ago.
Operator and location
Which location does TEST run from?
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 212.3.149.11:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 165217 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
TEST reports offline. The last reading came 27 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 30 September 2026.
Settings and map
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. 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.
How to join
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 212.3.149.11:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.