TEST
Offline 176.193.156.72:28015 checked 36d 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 57% 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- 536/525
- 408/450
- 54/250
- 51/250
- 58/100
- 167/200
Quick answers
from the figures on this pageWipe timing
How often does TEST wipe, and when?
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 38 days 17 hours ago.
Tag meanings
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TEST?
These Rust Metrics lists carry 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
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #13,187, in the top 57% of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 36 days 15 hours ago.
Server
Which location does TEST run from?
No region comes from TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 176.193.156.72:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
TEST reports offline. The last reading came 36 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 September 2026.
Rules and settings
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
Join
What do you do to join TEST?
Check: join. Open Rust, press F1, then enter client.connect 176.193.156.72:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.