test
Offline 91.108.0.111:28015 checked 9d 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 bestTop 69% 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 pageReset cycle
How often does test wipe, and when?
To tell the rhythm of test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 26 days 23 hours ago.
Tags
How should you read the tags on test?
These are the tags test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp75 (Max players): The server holds 75 slots; ts8 (Group limit): Default limit in force: 8 per team; 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): No region code is 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
What position does test hold among Rust servers?
Ranking for test: #15,285 on seven-day player hours, top 69% of all ranked servers.
What player count does test carry?
Status for test: offline. Last seen 9 days 17 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. The endpoint you need is 91.108.0.111:28015.
What Rust version is test on?
Rust network protocol 2634 and build 167781 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 9 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 October 2026.
Rules and settings
What rules does test enforce, and what are its settings?
Reading the name gives no gather rate for test. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. 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?
The game generates a procedural map for test.
How to join
What do you do to join test?
Check: join. Open Rust, press F1, then enter client.connect 91.108.0.111:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.