[TEST STAND] private - do not join
Online 46.174.50.219:28215 checked 11m ago
Server instruments
last reading Thu 04:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 59 · below 20 is lag, below 10 is badEntities
48 h range 2,126–2,168 · memory 3,239 MBUptime
6 days 9 hours since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 47% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 13h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 13hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 13hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 25 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:04 UTC FW27d ago | 2 | – | running | 0 |
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- 303/300
- 92/400
- 8/400
- 17/250
- 5/400
- 10/50
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on [TEST STAND] private - do not join?
At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 25 hours in.
What wipe timing does [TEST STAND] private - do not join follow?
With the force wipe, once a month, [TEST STAND] private - do not join wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 27 days 11 hours ago.
Tag meanings
How should you read the tags on [TEST STAND] private - do not join?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): Slots: 150; ts12 (Group limit): Teams are capped at 12; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^e (Minigames): Minigames run here: arenas, Bedwars, parkour and more; ^d (Combat training): Practise aim and PvP here; the loot comes to you; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here from [TEST STAND] private - do not join. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show [TEST STAND] private - do not join?
Rust Metrics lists featuring [TEST STAND] private - do not join: Modded Rust servers, checked live and Aim training servers, live readings. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Minigames ^e, Combat training ^d, Modded ^z and Carbon ^y; Group limit: 5 or more.
Player count
What position does [TEST STAND] private - do not join hold among Rust servers?
Player hours over seven days put [TEST STAND] private - do not join at #10,514, in the top 47% of all ranked servers.
How full does [TEST STAND] private - do not join get?
Current headcount on [TEST STAND] private - do not join: 0 players, 150 slots available. Check: players over seven days. Average 0, peak 1.
Operator and location
Which location does [TEST STAND] private - do not join run from?
No region comes from [TEST STAND] private - do not join. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 46.174.50.219:28215.
What Rust version is [TEST STAND] private - do not join on?
Rust network protocol 2635 and build 168909 on Linux is the build [TEST STAND] private - do not join runs. Matching protocol is required to join. Let Steam update your game.
How does [TEST STAND] private - do not join perform?
Reading: 60 server fps on average across the last 48 hours. It never dropped below 59. Peak entity count: 2,168. Buildings, deployables and all else included. Check: memory. Peak use was 3,239 MB. Expect lag when fps falls and entities climb.
Is [TEST STAND] private - do not join up, and how often does it stay up?
Reading: online. [TEST STAND] private - do not join answers right now. Check: restart. The uptime it reports puts the last restart about 6 days 9 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Map and rules
How is [TEST STAND] private - do not join configured, and what rules are in force?
No gather rate appears in the name: [TEST STAND] private - do not join. Group size, maximum: 12 players. Mode check gives minigames & battle royale; battle royale, parkour, Bedwars and arenas. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. VAC is off. That is Valve's anti-cheat.
What map is [TEST STAND] private - do not join on?
Size 6,000 and seed 1337: the game generates the procedural map on [TEST STAND] private - do not join from them. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name discord.gg/r2aim.
Connection
What do you do to join [TEST STAND] private - do not join?
To join: start Rust, press F1 and type client.connect 46.174.50.219:28215. Or press Launch Rust here and Steam opens the game and connects you.