test
Offline 91.108.1.121:28015 checked 26d 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 68% 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 timing
How often does test wipe, and when?
The rhythm of test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 26 days 22 hours ago.
Lists and filters
Which tags does test carry, and what do they mean?
These are the tags test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; 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; cs166494 (Build): Game build reading: 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $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. 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?
Ranking for test: #15,771 on seven-day player hours, top 68% of all ranked servers.
How full does test get?
Status for test: offline. Last seen 26 days 18 hours ago.
Server
What location is test hosted in?
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.1.121:28015.
What Rust version is test on?
Version check: Rust network protocol 2634 and build 166494 on Linux, run by test. Matching protocol is required to join. Let Steam update your game.
Is test up, and how often does it stay up?
Check: connection. test is offline at this moment. Last contact was 26 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 1 October 2026, recorded by Rust Metrics.
Map and rules
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. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is test on?
Check: map. Procedural, generated by the game, on test.
Join
How can you get onto test?
To join: start Rust, press F1 and type client.connect 91.108.1.121:28015. Or press Launch Rust here and Steam opens the game and connects you.