Test
Offline 109.252.87.15:28015 checked 38d 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- 581/675
- 366/525
- 46/250
- 44/250
- 127/200
- 144/300
Quick answers
from the figures on this pageWipe timing
How often does Test wipe, and when?
To tell the rhythm of Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 53 days 4 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): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2617 (Protocol): Protocol 2617: join only on the same game version; cs140244 (Build): Build 140244; ptrak (Networking): Network layer: RakNet, the standard for the game; $reu2 (Region code): eu2 is the region code on record. 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?
These Rust Metrics lists carry 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.
Occupancy
Where does Test sit in the rankings?
Ranking for Test: #15,508 on seven-day player hours, top – of all ranked servers.
How full does Test get?
Test is not responding; status offline, last seen 38 days 13 hours ago.
Operator and location
Which location does Test run from?
Reading: location. Test gives no region, with region code eu2. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 109.252.87.15:28015.
What Rust version is Test on?
Rust network protocol 2617 and build 140244 on Windows is the build Test runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is Test, and is it online now?
Reading: offline. Test last answered 38 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 September 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
No gather rate appears in the name: 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. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.
What map is Test on?
Procedural map on Test, made by the game's generator.
How to join
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 109.252.87.15:28015. Or press Launch Rust here and Steam opens the game and connects you.