TEST
Offline 95.170.182.48:28015 checked 40d 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 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- 246/300
- 15/250
- 33/250
- 120/200
- 46/200
- 51/100
Quick answers
from the figures on this pageReset cycle
When does TEST wipe?
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. 40 days 10 hours ago the current world was made.
Lists and filters
Which tags does TEST carry, and what do they mean?
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): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does TEST sit in the rankings?
Ranking for TEST: #13,285 on seven-day player hours, top – of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 40 days 9 hours ago.
Server
Which location does TEST run from?
No region comes from TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 95.170.182.48:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 40 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 17 September 2026.
Rules and settings
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Join
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 95.170.182.48:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.