Testing server
Offline 95.26.139.217:28015 checked 24d 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 71% 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
- 12/ 100
- 114/ 400
- 72/ 225
- 127/ 100
- 116/ 1000
- 6/ 700
Quick answers
Tags and listings
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.
How should you read the tags on Testing server?
gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): It holds 1 players; ts8 (Group limit): The default team size of 8 applies here; 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): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list Testing server puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
Where can you find Testing server?
No region comes from Testing server. 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.139.217:28015.
Is Testing server up, and how often does it stay online?
The server Testing server is not reachable at the moment; the last sighting was 24 days 12 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 23 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 schedule
When does Testing server wipe?
The wipes recorded for Testing server are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 24 days 13 hours ago.
Rules and settings
Which rules and settings is Testing server running?
No gather rate appears in the name of Testing server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.
Population
Is Testing server busy?
The last sighting of Testing server was 24 days 12 hours ago; it is offline right now.
What's Testing server's rank among Rust servers?
Over the last seven days, Testing server is #15,459 by player hours, among the top 71% 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.139.217:28015. Or click Launch Rust on this page to open the game through Steam and connect.