RS-15954Modded server
Testing
Offline OC 159.196.14.186:28015 checked 11d ago
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 16 October, 02:13 UTC, in 1d 0h. 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.
Player count
What is the typical player count on Testing?
Testing is offline at this moment; the last signal was 11 days 23 hours ago.
How is Testing ranked?
On seven-day player hours, Testing ranks #15,954 overall, in the top 70% of ranked servers and #195 across Oceania.
Server tags and lists
On Top Rust Servers, which lists and filters carry Testing?
These Top Rust Servers lists include Testing: Rust servers in Oceania, Top modded Rust servers and Rust battlefield servers, ranked. 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; Last wipe: In the last 2 weeks.
How should you read the tags on Testing?
The game's server browser reads the tags that Testing publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp44 (Max players): Player slots: 44; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): To join, your game must be on protocol 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set; ^w (Weekly): It wipes weekly; ^i (Battlefield): Kits and high rates drive fast PvP; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, so it is listed as Modded; OC (Oceania): The server browser lists it under Oceania. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Map and rules
What is the map on Testing?
A procedural map, created by the game, is in use on Testing.
What does Testing run for rules and settings?
You will not find a gather rate in the name Testing. Up to 8 players per group, as the game defaults. battlefield is the game mode, kits and high rates for rapid PvP. It is a Modded server, meaning plugins or settings modify the game. Oxide plugins are in use. VAC anti-cheat is active.
About the server
What is the Rust version on Testing?
Rust network protocol 2634 and build 166494 is what Testing runs, on Windows. Joining requires matching protocols, and Steam updates your game automatically.
Where can Testing be found?
Its OC tag is how Testing lists itself in Oceania. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 159.196.14.186:28015.
What is the uptime of Testing?
The server Testing is down at the moment, with its last appearance 11 days 23 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. It was first observed by Top Rust Servers on 2 October 2026.
Wipe schedule
When does Testing wipe?
An estimate of Testing's next wipe comes from weekly: 7 days after its last wipe. The upcoming wipe is set for Friday 16 October at 02:13 UTC. The present world has been live since 12 days 23 hours ago. Its tags carry a wipe schedule set to weekly.
Joining the server
What are the steps to join Testing?
To connect manually, open the console with F1 and type client.connect 159.196.14.186:28015. Or click Launch Rust on this page to open Rust through Steam and connect directly.