Testing server
Offline 95.26.146.49:28015 checked 8d 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
- 833/ 100
- 112/ 400
- 91/ 245
- 125/ 100
- 246/ 1000
- 18/ 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; 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): There are 1 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167398 (Build): It's on build 167398; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of 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. The endpoint is 95.26.146.49:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 8 days 7 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 9 October 2026.
What is the Rust version for Testing server?
The version on Testing server is Rust network protocol 2634 and build 167398, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
How often 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. 9 days 3 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to Testing server?
The name of Testing server contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. 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 8 days 7 hours ago; it is offline right now.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,553 by player hours, among the top 61% of all ranked servers.
Getting in
What's the way to join Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.146.49:28015. Or click Launch Rust on this page to open the game through Steam and connect.