test
Offline 91.108.0.247:28015 checked 7d ago
Server instruments
no direct query in 48 hoursPlayers now
1% full 7-day avg7-day peakServer 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- 199/250
- 176/200
- 14/250
- 16/250
- 18/100
- 100/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does test follow?
The rhythm of test's wipes cannot be told yet: too few 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 27 days 10 hours ago.
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): Slots: 75; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; 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. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does test appear in Rust Metrics lists and filters?
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?
Player hours over seven days put test at #13,094, in the top 59% of all ranked servers.
What is the population on test?
test is not responding; status offline, last seen 7 days 1 hours ago. Check: players over seven days. Average 1, peak 1.
Server details
Where does test sit?
Reading: location. test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 91.108.0.247:28015.
What Rust version is test on?
Rust network protocol 2634 and build 167781 on Linux is the build test runs. Check: protocol. To join, your game must match; Steam handles the update.
Is test up, and how often does it stay up?
Reading: offline. test last answered 7 days 1 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. The first sighting on Rust Metrics was 22 October 2026.
Rules and settings
How is test configured, and what rules are in force?
Reading the name gives no gather rate for test. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is test on?
Procedural map on test, made by the game's generator.
Join
How do you connect to test?
Press F1 in Rust and enter client.connect 91.108.0.247:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.