TEST
Offline 46.32.67.68:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
100% 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- 247/275
- 20/250
- 17/250
- 163/200
- 64/200
- 37/100
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. The world in play was created 41 days 6 hours ago.
Tag meanings
Which tags does TEST carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from TEST. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TEST: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #14,201, in the top – of all ranked servers.
What player count does TEST carry?
Status for TEST: offline. Last seen 41 days 6 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 46.32.67.68:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 163794 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 41 days 6 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.
Settings and map
What rules does TEST enforce, and what are its settings?
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: standard play of gathering, building and raiding. 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.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
How to join
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 46.32.67.68:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.