Testing server
Offline 95.26.146.55:28015 checked 23d 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 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
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
- 834/ 100
- 111/ 400
- 101/ 245
- 130/ 100
- 255/ 1000
- 18/ 700
Quick answers
Tags and listings
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.
How should you read the tags on Testing server?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): It holds 1 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — 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
Where can you find Testing server?
There is no published region for Testing server. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 95.26.146.55:28015.
Is Testing server up, and how often does it stay online?
Right now Testing server is offline, having last been seen 23 days 15 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 24 September 2026.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2633 and build 165217, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Testing server wipe?
The wipes recorded for Testing server are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 24 days 6 hours.
Rules and settings
What settings are in place on Testing server?
Its name does not state a gather rate for Testing server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. The server runs Valve's anti-cheat, VAC.
Player count
What's the population like on Testing server?
Right now Testing server is offline, with its last appearance 23 days 15 hours ago.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #13,322 by player hours, among the top 61% of all ranked servers.
How to join
How do you get into Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.146.55:28015. Or click Launch Rust on this page to open the game through Steam and connect.