Testing server
Offline 95.26.136.180:28015 checked 22d 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 67% 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
- 848/ 100
- 115/ 400
- 113/ 245
- 131/ 100
- 283/ 1000
- 21/ 700
Quick answers
Tags and filters
Where does Testing server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Testing server: 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?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): The build number is 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — that is the tag list Testing server puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What's the location of Testing server?
Testing server does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 95.26.136.180:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 22 days 6 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 25 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Testing server?
On Windows, Testing server runs Rust network protocol 2633 and build 165217. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Testing server wipe?
Testing server's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 24 days 6 hours is how long ago this world came into being.
Rules and settings
What settings are in place on Testing server?
The name of Testing server contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
Population
Is Testing server busy?
The last sighting of Testing server was 22 days 6 hours ago; it is offline right now.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #15,361 by player hours, among the top 67% of all ranked servers.
Join info
What's the way to join Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.136.180:28015. Or click Launch Rust on this page to open the game through Steam and connect.