test
Offline 145.224.74.5:20000 checked 36d 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- 164/250
- 148/200
- 15/250
- 20/250
- 16/100
- 64/200
Quick answers
from the figures on this pageReset cycle
How often does test wipe, and when?
Its rhythm cannot be told from the wipes of test on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 47 days 15 hours ago the current world was made.
Tag meanings
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; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from test. 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?
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.
Population
What position does test hold among Rust servers?
Player hours over seven days put test at #15,443, in the top 67% of all ranked servers.
What is the population on test?
Status for test: offline. Last seen 36 days 11 hours ago.
Server details
What location is test hosted in?
Reading: location. test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 145.224.74.5:20000.
What Rust version is test on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by test. Matching protocol is required to join. Let Steam update your game.
What is the uptime on test, and is it online?
test reports offline. The last reading came 36 days 11 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 22 September 2026.
Settings and map
What settings and rules apply on test?
Reading the name gives no gather rate for test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — 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 off.
Which map is live on test?
The game generates a procedural map for test.
How to join
How can you get onto test?
To join: start Rust, press F1 and type client.connect 145.224.74.5:20000. Or press Launch Rust here and Steam opens the game and connects you.