test
Offline 5.175.178.27:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
12% 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- 288/300
- 21/250
- 14/250
- 176/200
- 88/200
- 22/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. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 45 days 10 hours ago the current world was made.
Tags
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; mp8 (Max players): Slots: 8; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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?
Rust Metrics lists featuring 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
What position does test hold among Rust servers?
Player hours over seven days put test at #13,043, in the top – of all ranked servers.
What is the population on test?
Reading for test: offline at this moment; last seen 44 days 12 hours ago.
Operator and location
Where does test sit?
No region comes from test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 5.175.178.27:28015.
What Rust version is test on?
Rust network protocol 2633 and build 163794 on Windows is the build test runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on test, and is it online?
Reading: offline. test last answered 44 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
What settings and rules apply on test?
Check: gather rate. The name test does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
Which map is live on test?
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 5.175.178.27:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.