Testing server
Offline 95.26.138.151:28015 checked 1d 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 46% 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?
These Rust Going Deep lists include Testing server: 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 3 days.
How should you read the tags on Testing server?
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): The protocol is 2634; a different version won't get you in; cs167781 (Build): The build number is 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Testing server puts out for the game's server browser. 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's the location of Testing server?
No region comes from Testing server. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 95.26.138.151:28015.
What's the uptime like for Testing server?
Right now Testing server is offline, having last been seen 24 hours ago. 17 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 167781, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
How often does Testing server wipe?
Testing server's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 31 hours.
Rules and settings
What settings are in place on Testing server?
No gather rate appears in the name of Testing server. The group limit is the game's default of 8 players. It runs survival, 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. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Player count
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 24 hours ago. For the past week, players averaged 1 with a high of 1. At 10:00 UTC in the last 48 hours, the average reached its highest: 1 players.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #10,218 by player hours, among the top 46% of all ranked servers.
Join info
What's the way 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.138.151:28015.