test
Offline 81.9.127.119:28015 checked 42d 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- 24/500
- 125/100
- 33/225
- 15/700
- 3/200
- 1/1000
Quick answers
from the figures on this pageWipe timing
How often does test wipe, and when?
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. 49 days 17 hours ago the current world was made.
Tag meanings
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; mp15 (Max players): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163493 (Build): Build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?
On Rust Metrics, test sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does test hold among Rust servers?
Player hours over seven days put test at #15,497, in the top – of all ranked servers.
What player count does test carry?
Reading for test: offline at this moment; last seen 42 days 11 hours ago.
Operator and location
What location is test hosted in?
No region comes from test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 81.9.127.119:28015.
What Rust version is test on?
Version check: Rust network protocol 2633 and build 163493 on Windows, run by test. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on test, and is it online?
test reports offline. The last reading came 42 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on test?
Check: gather rate. The name test does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is test on?
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 81.9.127.119:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.