Testing server
Offline 95.26.141.92:28015 checked 10d 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 62% 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
- 285/ 400
- 181/ 225
- 123/ 100
- 393/ 1000
- 38/ 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. 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.
What's the meaning of the tags on Testing server?
Testing server's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167058 (Build): It's on build 167058; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^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.
Server info
What location is Testing server in?
No region comes from 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.141.92:28015.
What's the uptime like for Testing server?
The server Testing server is not reachable at the moment; the last sighting was 10 days 20 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 7 October 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2634 and build 167058, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does Testing server follow for wipes?
Too few wipes are on record for Testing server to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 10 days 21 hours ago.
Settings and map
What settings and rules have been applied to Testing server?
No gather rate appears in the name of Testing server. Up to 8 players per group, which is the 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 is on: Valve's anti-cheat is active.
Player count
What's the population like on Testing server?
The last sighting of Testing server was 10 days 20 hours ago; it is offline right now.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,697 by player hours, among the top 62% of all ranked servers.
Getting in
What's the way to join Testing server?
Open Rust and press F1, then type client.connect 95.26.141.92:28015. Alternatively, click Launch Rust on this page to join via Steam.