TEST
Offline 185.176.113.147:28015 checked 42d 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 bestWipe 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- 226/250
- 196/225
- 20/250
- 17/250
- 20/100
- 100/200
Quick answers
from the figures on this pageWipe schedule
How often does TEST wipe, and when?
To tell the rhythm of TEST, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 42 days 10 hours ago the current world was made.
Lists and filters
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; cs164541 (Build): The server runs game build 164541; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TEST?
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.
Player count
Where does TEST sit in the rankings?
Ranking for TEST: #14,509 on seven-day player hours, top – of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 42 days 10 hours ago.
Operator and location
Where does TEST sit?
No region tag on TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.176.113.147:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 164541 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 42 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TEST?
Check: gather rate. The name TEST does not state one. 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. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
Join
What do you do to join TEST?
To join: start Rust, press F1 and type client.connect 185.176.113.147:28015. Or press Launch Rust here and Steam opens the game and connects you.