Testing
Offline OC 159.196.14.186:28015 checked 26d 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, top 86% in OC. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 02:13 UTC, in 17h. Weekly: 7 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 Testing?
These are the Rust Pop Watch lists that include Testing: Oceania Rust servers, live, Modded Rust servers, live and The battlefield crowd, counted. These filters bring it up on the server list: Region: Oceania; Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
What do the server tags on Testing mean?
These are the tags Testing publishes for the browser: gmrust (Game mode): Plain vanilla Rust survival, nothing bolted on; mp44 (Max players): There are 44 slots; ts8 (Group limit): This uses the default limit of 8 players per team; v2634 (Protocol): To join, your game must be on the same protocol version: 2634; cs166494 (Build): It's on game build 166494; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): Region code left blank; ^w (Weekly): Every week brings a wipe; ^i (Battlefield): High rates and kits for fast PvP; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; OC (Oceania): Its place in the server browser is under Oceania. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
The players
How does Testing rank against other Rust servers?
Testing takes #15,954 on seven-day player hours, a top 70% spot overall and #195 across Oceania.
How many players are on Testing right now?
Testing went quiet 26 days 6 hours ago and is offline at the moment.
About the server
Is Testing online, and how reliable is it?
The server Testing is not online now; 26 days 6 hours have passed since it was last seen. Out of 168 hours in the last 7 full days, it was online for 0, a 0% uptime. It came to Rust Pop Watch's attention on 2 October 2026.
Where is Testing located?
In Oceania, Testing lists itself with its OC tag. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 159.196.14.186:28015.
Which Rust version is Testing on?
On Windows, Testing runs Rust network protocol 2634 and build 166494. To join, your game must be on the same protocol; Steam handles the update.
The wipe schedule
What is the wipe schedule on Testing?
An estimate from weekly: 7 days after its last wipe gives Testing's next wipe. Friday 30 October at 02:13 UTC is the date its next wipe is due. 27 days 6 hours is when the present world was made. Its tags carry a wipe schedule that runs weekly.
Rules and settings
Which map does Testing run?
A procedural map is what Testing runs, generated by the game.
What are the rules and settings on Testing?
The name of Testing says nothing about gather rate. The group limit is 8 players, the game's default. It runs battlefield, kits and high rates drive fast PvP. It is a Modded listing: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is switched on.
Getting in
How do I join Testing?
The console method: start Rust, press F1, and type client.connect 159.196.14.186:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.