Testing server
Offline 95.26.139.0:28015 checked 12d 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
- 17/ 100
- 259/ 400
- 181/ 225
- 129/ 100
- 312/ 1000
- 23/ 700
Quick answers
Tags and search
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. The server list shows it under 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 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; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166652 (Build): It's on build 166652; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is Testing server in?
Testing server does not put out a region. 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.0:28015.
What's the uptime like for Testing server?
The server Testing server is not reachable at the moment; the last sighting was 12 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 5 October 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
Rust network protocol 2634 and build 166652 is what Testing server runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
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. This world has been running since 12 days 9 hours ago.
Map and rules
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. survival is the game mode, 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. VAC, Valve's anti-cheat, is enabled.
Population
How many players are on Testing server?
Testing server was last seen 12 days 6 hours ago and is offline as you read this.
What's Testing server's rank among Rust servers?
For player hours in the last seven days, Testing server ranks #13,778, within the top 61% of ranked servers.
How to join
What's the way to join Testing server?
Open Rust and press F1, then type client.connect 95.26.139.0:28015. Alternatively, click Launch Rust on this page to join via Steam.