Testing server
Offline 95.26.145.58: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 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
- 12/ 100
- 110/ 400
- 70/ 225
- 134/ 100
- 115/ 1000
- 6/ 700
Quick answers
Tags and search
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?
The server browser shows these tags for Testing server: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): The slot count is 1; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): This server runs build 165217; 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. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
About the server
What location is Testing server in?
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. The endpoint is 95.26.145.58:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 22 days 20 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 25 September 2026.
What Rust version is Testing server on?
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 details
How often 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. The world you are on now was created 24 days 13 hours.
Settings and map
What settings and rules have been applied to 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. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Player count
What's the population like on Testing server?
Testing server was last seen 22 days 20 hours ago and is offline as you read this.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,835 by player hours, among the top 61% of all ranked servers.
Join info
What's the process to join Testing server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 95.26.145.58:28015.