TEST
Offline 176.116.166.101:28015 checked 45d 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- 562/625
- 429/450
- 166/250
- 53/100
- 194/250
- 329/225
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. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 54 days 1 hours ago.
Lists and filters
How should you read the tags on TEST?
Tags published by TEST, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): The server runs game build 163207; 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.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: 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
What position does TEST hold among Rust servers?
Ranking for TEST: #15,040 on seven-day player hours, top – of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 45 days 1 hours ago.
Server details
Which location does TEST run from?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.116.166.101:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163207, 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 45 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TEST?
Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: 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. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
The game generates a procedural map for TEST.
How to join
How can you get onto TEST?
Press F1 in Rust and enter client.connect 176.116.166.101:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.