test
Offline 217.142.18.135:20000 checked 8d 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 63% 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- 522/550
- 438/450
- 60/250
- 66/250
- 53/100
- 164/200
Quick answers
from the figures on this pageWipe schedule
How often does test wipe, and when?
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. 26 days 19 hours ago the current world was made.
Lists and filters
How should you read the tags on test?
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): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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.
Occupancy
What position does test hold among Rust servers?
Player hours over seven days put test at #13,867, in the top 63% of all ranked servers.
What is the population on test?
Reading for test: offline at this moment; last seen 8 days 17 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. Check: address. It reads 217.142.18.135:20000.
What Rust version is test on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by test. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on test, and is it online?
test reports offline. The last reading came 8 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 October 2026, recorded by Rust Metrics.
Settings and map
What rules does test enforce, and what are its settings?
No gather rate appears in the name: test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.
Which map is live on test?
The game generates a procedural map for test.
Join
How can you get onto test?
Press F1 in Rust and enter client.connect 217.142.18.135:20000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.