test
Offline 217.142.18.79: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 59% 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- 288/325
- 377/425
- 930/1000
- 49/100
- 971/1000
- 774/800
Quick answers
from the figures on this pageWipe schedule
What wipe timing does test follow?
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. The world in play was created 27 days 1 hours ago.
Lists and filters
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; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
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.
Player count
Where does test sit in the rankings?
Player hours over seven days put test at #13,159, in the top 59% of all ranked servers.
What player count does test carry?
Reading for test: offline at this moment; last seen 8 days 1 hours ago.
Operator and location
What location is test hosted in?
No region tag on test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 217.142.18.79:20000.
What Rust version is test on?
Reading: test, Rust network protocol 2634 and build 167781, Windows. 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 8 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 21 October 2026, recorded by Rust Metrics.
Map and rules
How is test configured, and what rules are in force?
Check: gather rate. The name test does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. 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.79:20000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.