TEST
Offline 91.108.1.190:28015 checked 23d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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- 258/250
- 200/225
- 18/250
- 23/250
- 22/100
- 94/200
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
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 23 days 13 hours ago.
Tag meanings
How should you read the tags on TEST?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from TEST. 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?
Rust Metrics lists featuring TEST: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #13,772, in the top 61% of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 23 days 10 hours ago.
Server
Where does TEST sit?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 91.108.1.190:28015.
What Rust version is TEST on?
Rust network protocol 2634 and build 166652 on Windows is the build TEST runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on TEST, and is it online?
Reading: offline. TEST last answered 23 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 5 October 2026.
Map and rules
How is TEST configured, and what rules are in force?
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; gather, build and raid, as the game normally runs. 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.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 91.108.1.190:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.