TEST
Offline 46.138.156.52:28015 checked 9h 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 bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 227/275
- 297/350
- 764/1000
- 50/100
- 877/950
- 727/800
Quick answers
from the figures on this pageReset cycle
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 21 days 8 hours ago the current world was made.
Tags
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; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Game build reading: 167231; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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.
Population
What position does TEST hold among Rust servers?
Ranking for TEST: #15,268 on seven-day player hours, top 68% of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 9 hours ago. Check: player average. 0 over the last seven days.
Server
Where does TEST sit?
Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.138.156.52:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167231, Windows. 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 9 hours ago. Uptime for the last 7 full days: 5 of 168 hours, or 3%. Reading: first seen 18 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. The group cap is 8 players, which is the default in the game. Mode check gives survival; 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. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
Join
How can you get onto TEST?
Press F1 in Rust and enter client.connect 46.138.156.52:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.