TEST
Offline 188.244.249.145:28015 checked 16d 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 71% 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- 314/325
- 383/425
- 950/1000
- 47/100
- 980/1000
- 774/800
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes 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 16 days 8 hours ago.
Tags
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): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty 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?
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.
Occupancy
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,366, in the top 71% of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 16 days 8 hours ago.
Server
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 188.244.249.145:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by TEST. Matching protocol is required to join. Let Steam update your game.
What is the uptime on TEST, and is it online?
Reading: offline. TEST last answered 16 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 October 2026.
Map and rules
How is TEST configured, and what rules are in force?
No gather rate appears in the name: TEST. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. 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.
Which map is live on TEST?
The game generates a procedural map for TEST.
Connection
What do you do to join TEST?
Press F1 in Rust and enter client.connect 188.244.249.145:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.