Test
Offline 37.45.16.138:28015 checked 1d 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 69% 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- 304/350
- 21/250
- 38/250
- 138/200
- 52/200
- 46/100
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 39 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): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Game build reading: 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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?
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; Last wipe: In the last 3 days.
Population
What position does Test hold among Rust servers?
Ranking for Test: #15,414 on seven-day player hours, top 69% of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 38 hours ago. A seven-day average of 0 players is the reading.
Server
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. Check: address. It reads 37.45.16.138:28015.
What Rust version is Test on?
Rust network protocol 2634 and build 167584 on Windows is the build Test runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 38 hours ago. Uptime for the last 1 full day: 0 of 24 hours, or 0%. Reading: first seen 26 October 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. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Join
How do you connect to Test?
Press F1 in Rust and enter client.connect 37.45.16.138:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.