RS-13778Modded server
Testing server
Offline 95.26.139.0:28015 checked 9d 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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
How many players are usually on Testing server?
Currently, Testing server is offline; the last sighting was 9 days 1 hours ago.
Where does Testing server sit in the rankings?
On player hours across seven days, Testing server is #13,778, inside the top 61% of all ranked servers.
Server tags and lists
Where does Testing server show up in Top Rust Servers lists and filters?
These Top Rust Servers lists count Testing server among their servers: Top modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on Testing server?
The game's server browser reads the tags that Testing server publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp1 (Max players): It has 1 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must be on protocol 2634; cs166652 (Build): Running game build 166652; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): It appears in Modded, as plugins or settings modify the game. 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 settings and rules does Testing server use?
You will not find a gather rate in the name Testing server. Up to 8 players per group, as the game defaults. survival is the game mode, gather, build and raid in the standard game. Player versus player combat and raiding are enabled. It is a Modded server, meaning plugins or settings modify the game. Oxide plugins are loaded. The server runs with VAC on.
Server info
What version is Testing server running?
Testing server uses Rust network protocol 2634 and build 166652 with Windows as its system. Joining requires matching protocols, and Steam updates your game automatically.
Where can Testing server be found?
No region is published by Testing server. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. It answers at 95.26.139.0:28015.
Is Testing server currently online?
Testing server is offline now; the last time it was seen was 9 days 1 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. The first time Top Rust Servers saw it was on 5 October 2026.
Wipe schedule
When does Testing server wipe?
Not enough wipe data exists yet to identify the rhythm of Testing server. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 9 days 4 hours ago.
How to join
What are the steps to join Testing server?
Use the console: open Rust, press F1, and type client.connect 95.26.139.0:28015. Or simply click Launch Rust here; it opens the game through Steam and connects you.