test
Offline 9.246.41.75:20000 checked 34d 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- 679/750
- 476/500
- 40/250
- 59/250
- 159/200
- 210/250
Quick answers
from the figures on this pageReset cycle
When does test wipe?
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 in play was created 47 days 1 hours ago.
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: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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?
These Rust Metrics lists carry test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does test hold among Rust servers?
Ranking for test: #14,163 on seven-day player hours, top 65% of all ranked servers.
How full does test get?
Status for test: offline. Last seen 34 days 18 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. The endpoint you need is 9.246.41.75:20000.
What Rust version is test on?
Reading: test, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is test, and is it online now?
test reports offline. The last reading came 34 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 23 September 2026.
Settings and map
How is test configured, and what rules are in force?
No gather rate appears in the name: test. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. 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 off.
Which map is live on test?
Procedural map on test, made by the game's generator.
How to join
How do you connect to test?
Check: join. Open Rust, press F1, then enter client.connect 9.246.41.75:20000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.