test
Offline 91.108.0.163:28015 checked 24d ago
Server instruments
no direct query in 48 hoursPlayers now
1% 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 61% 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 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. 26 days 22 hours ago the current world was made.
Tags
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): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show test?
These Rust Metrics lists carry 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.
Player count
Where does test sit in the rankings?
Ranking for test: #13,861 on seven-day player hours, top 61% of all ranked servers.
What is the population on test?
test is not responding; status offline, last seen 24 days 6 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 91.108.0.163:28015.
What Rust version is test on?
Rust network protocol 2634 and build 166652 on Linux is the build test runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is test, and is it online now?
Check: connection. test is offline at this moment. Last contact was 24 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 4 October 2026.
Settings and map
What rules does test enforce, and what are its settings?
Check: gather rate. The name test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is test on?
Procedural map on test, made by the game's generator.
Join
What do you do to join test?
Check: join. Open Rust, press F1, then enter client.connect 91.108.0.163:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.