TEST
Offline 188.163.53.218:28015 checked 14d 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 62% 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- 201/250
- 281/300
- 763/800
- 44/100
- 854/900
- 669/725
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. 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 20 days 8 hours ago.
Tag meanings
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; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none 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?
Rust Metrics lists featuring 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
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #13,419, in the top 62% of all ranked servers.
How full does TEST get?
Reading for TEST: offline at this moment; last seen 14 days 3 hours ago.
Operator and location
Which location does TEST run from?
No region tag on TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 188.163.53.218:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167398, Windows. 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 14 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 12 October 2026.
Settings and map
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. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
The game generates a procedural map for TEST.
How to join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 188.163.53.218:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.