Test
Offline 46.138.155.176:28015 checked 3d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avg7-day peakServer 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 39% 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- 324/375
- 217/250
- 35/250
- 31/250
- 57/100
- 73/200
Quick answers
from the figures on this pageReset cycle
How often does Test wipe, and when?
To tell the rhythm of Test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 21 days 1 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; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.
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.
Occupancy
What position does Test hold among Rust servers?
Ranking for Test: #8,742 on seven-day player hours, top 39% of all ranked servers.
What player count does Test carry?
Test is not responding; status offline, last seen 3 days 23 hours ago. Check: players over seven days. Average 0, peak 1.
Server details
What location is Test hosted in?
Reading: location. Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 46.138.155.176:28015.
What Rust version is Test on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Test. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Test reports offline. The last reading came 3 days 23 hours ago. Uptime for the last 7 full days: 17 of 168 hours, or 10%. The first sighting on Rust Metrics was 15 October 2026.
Map and rules
How is Test configured, and what rules are in force?
Check: gather rate. The name Test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
What map is Test on?
The game generates a procedural map for Test.
Join
What do you do to join Test?
Press F1 in Rust and enter client.connect 46.138.155.176:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.