Test
Online 66.51.99.64:28035 checked 10m ago
Measurements
Players
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
Top 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 9h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:57 UTC FW26d ago | 1 | – | running | 0 |
| Thu 1 Oct, 04:17 UTC27d ago | 1 | – | 0.6 days | 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.
Quick answers
Population
How does Test rank against other Rust servers?
Over the past week it ranks #14,563 for player hours, which puts Test in the top 66% of all ranked servers.
How busy is Test?
The count reads 0 players on Test, which has 50 slots. Seven days of counting give an average of 0 players and a peak of 1.
Lists and tags
What do the server tags on Test mean?
These are the tags Test publishes, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^m (Monthly): This server wipes once a month, at the same time as Facepunch's force wipe; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Test?
These Rust Population lists include Test: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Wipe schedule
What does wipe day look like on Test?
Averaged over recent wipes, 1 players were counted at the busiest point. Peak came 1 hours into the latest wipe.
What is the wipe schedule on Test?
Test wipes with the force wipe and at no other time, once a month. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, when all Rust servers wipe. 26 days 15 hours ago the current world was made. In its tags a monthly wipe schedule is published.
Map and rules
Which map does Test run?
The map on Test is procedural, made by the game at size 5,000 from seed 1337. You can look at it on RustMaps from this page: size and seed determine the map. The name on the map is Custom Map.
What are the rules and settings on Test?
The name tells you nothing about gather rates: Test states none. No limit is set beyond the standard 8 players per group. survival is what it runs, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. Oxide plugins are in use here. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does Test run?
The setup is Rust network protocol 2635 and build 168909 on Linux for Test. Your game needs the same protocol to join; Steam takes care of updating it.
Does Test run smoothly?
It ran at 5 server fps on average over the last 48 hours, and never went below 5. Up to 125,051 entities were present, counting buildings, deployables and everything else. Up to 6,483 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.
Is Test online, and how reliable is it?
Test is up and running at the moment. About 5 days 10 hours ago, it restarted, according to its uptime. Over the last 7 full days, 168 of 168 hours were online, or 100%. On 13 September 2026, Rust Population saw it for the first time.
Where is Test located?
No region is published by Test. Rust Population does not look up where the machine stands; it shows where the server says it is. 66.51.99.64:28035 is where it lives.
How to join
How do I join Test?
Either enter client.connect 66.51.99.64:28035 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.