test
Offline 145.224.72.249:20000 checked 30d 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 65% 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageReset cycle
What wipe timing does test follow?
Its rhythm cannot be told from the wipes of test on record: there are too few. 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 it runs now was made 47 days 6 hours ago.
Tag meanings
How should you read the tags on test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from test. 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
Where does test sit in the rankings?
Player hours over seven days put test at #15,577, in the top 65% of all ranked servers.
What is the population on test?
test is not responding; status offline, last seen 30 days 5 hours ago.
Operator and location
What location is test hosted in?
No region comes from test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 145.224.72.249:20000.
What Rust version is test on?
Reading: test, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
Is test up, and how often does it stay up?
Reading: offline. test last answered 30 days 5 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 28 September 2026.
Map and rules
What rules does test enforce, and what are its settings?
Reading the name gives no gather rate for test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. VAC is off. That is Valve's anti-cheat.
What map is test on?
Procedural map on test, made by the game's generator.
Join
What do you do to join test?
To join: start Rust, press F1 and type client.connect 145.224.72.249:20000. Or press Launch Rust here and Steam opens the game and connects you.