test
Offline 95.160.182.126: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- 169/250
- 121/200
- 17/250
- 15/250
- 18/100
- 29/200
Quick answers
from the figures on this pageWipe schedule
When does test wipe?
The rhythm of test's wipes cannot be told yet: too few 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. The world in play was created 55 days 8 hours ago.
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; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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.
Occupancy
What position does test hold among Rust servers?
Ranking for test: #14,437 on seven-day player hours, top – of all ranked servers.
What player count does test carry?
Status for test: offline. Last seen 42 days 14 hours ago.
Server details
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. The endpoint you need is 95.160.182.126: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 42 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.
Settings and map
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. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.
Which map is live on test?
Procedural map on test, made by the game's generator.
Join
How do you connect to test?
Press F1 in Rust and enter client.connect 95.160.182.126:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.