Testing server
Offline 95.26.139.239:28015 checked 21d 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
daily · 1 is bestTop 69% 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
newest first| 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
- 0/ 100
- 72/ 400
- 51/ 245
- 120/ 100
- 90/ 1000
- 6/ 700
Quick answers
Tags and filters
Where does Testing server appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Testing server are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on Testing server?
The server browser shows these tags for Testing server: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What location is Testing server in?
No region comes from Testing server. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 95.26.139.239:28015.
What's the uptime like for Testing server?
Testing server is down at the moment; it was last up 21 days 14 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 26 September 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2633 and build 165217, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does Testing server follow for wipes?
Too few wipes are on record for Testing server to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 24 days 12 hours is how long ago this world came into being.
Settings and map
What settings are in place on Testing server?
Its name does not state a gather rate for Testing server. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Population
Is Testing server busy?
Right now Testing server is offline, with its last appearance 21 days 14 hours ago.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #16,058 by player hours, among the top 69% of all ranked servers.
How to join
What's the way to join Testing server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 95.26.139.239:28015.