Test
Offline 31.162.18.183:28015 checked 8d ago
Vital stats
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Monday 2 November, 18:37 UTC, in 5d 8h. Biweekly: 14 days after its last wipe
Wipes
| 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.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include Test?
These Rust Pop Watch lists include Test: Modded Rust servers, live and Rust PvE servers, ranked by who's hot. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
What do the server tags on Test mean?
For the server browser, Test lists these tags: gmvanilla (Game mode): Survival in vanilla form; mp200 (Max players): It has 200 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game must be on the same protocol version: 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^b (Biweekly): It wipes on a two-week cycle; ^p (PvE): Here the world is the threat, and players don't fight each other; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. Current players, queue and world age are in the tags too, displayed at the top of this page.
Player counts
How does Test rank against other Rust servers?
Player hours over the last week rank Test at #15,322, within the top 70% of ranked servers.
How many players are on Test right now?
Test went quiet 8 days 15 hours ago and is offline at the moment.
Server details
Is Test online, and how reliable is it?
Down at the moment: Test was last seen 8 days 15 hours ago. The last 7 full days saw uptime of 0%, with 0 out of 168 hours online. The first time Rust Pop Watch saw it was 19 October 2026.
Where is Test located?
There is no region from Test. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 31.162.18.183:28015.
Which Rust version is Test on?
On Windows, Test runs Rust network protocol 2634 and build 167781. To join, your game must be on the same protocol; Steam handles the update.
The wipe schedule
What is the wipe schedule on Test?
An estimate from biweekly: 14 days after its last wipe gives Test's next wipe. The next wipe is pencilled in for Monday 2 November at 18:37 UTC. The world it is running now dates from 8 days 15 hours. The tags list a fortnightly wipe schedule.
Map and rules
Which map does Test run?
Test uses a procedural map, which the game generates.
What are the rules and settings on Test?
No gather rate appears in the name of Test. Eight players per group: that is the game's default. It runs pve, no fighting other players. Plugins or settings alter the game, and the browser lists it as Modded. Oxide plugins power it. The VAC anti-cheat from Valve is on.
Join up
How do I join Test?
The console method: start Rust, press F1, and type client.connect 31.162.18.183:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.