test
Offline 91.108.0.219:28015 checked 40d 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 bestWipe 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- 237/275
- 146/200
- 28/250
- 15/250
- 32/100
- 42/200
Quick answers
from the figures on this pageWipe timing
When does test wipe?
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. 54 days 21 hours ago the current world was made.
Tag meanings
How should you read the tags on test?
Tags published by test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp75 (Max players): 75 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.
Where does test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry test: 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.
Population
Where does test sit in the rankings?
Player hours over seven days put test at #15,415, in the top – of all ranked servers.
How full does test get?
Status for test: offline. Last seen 40 days 18 hours ago.
Server details
Which location does test run from?
No region comes from test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 91.108.0.219:28015.
What Rust version is test on?
Rust network protocol 2633 and build 164530 on Linux is the build test runs. Matching protocol is required to join. Let Steam update your game.
How reliable is test, and is it online now?
Reading: offline. test last answered 40 days 18 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 17 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. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on test?
Check: map. Procedural, generated by the game, on test.
Connection
How can you get onto test?
Press F1 in Rust and enter client.connect 91.108.0.219:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.