Testing server
Offline 95.26.141.240:28015 checked 5d 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 72% 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
- 1001/ 100
- 62/ 400
- 49/ 245
- 130/ 100
- 82/ 1000
- 7/ 700
Quick answers
Tags and filters
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): 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; cs167398 (Build): The build number is 167398; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded. 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.
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. The endpoint is 95.26.141.240:28015.
What's the uptime like for Testing server?
Testing server is down at the moment; it was last up 5 days 22 hours ago. Over the past full 5 days it stayed up for 0 of 120 hours, or 0%. Rust Going Deep has had it on record since 12 October 2026.
What Rust version is Testing server on?
Rust network protocol 2634 and build 167398 is what Testing server runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
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. 7 days 17 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Testing server running?
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. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Population
What's the population like on Testing server?
The last sighting of Testing server was 5 days 22 hours ago; it is offline right now. The seven-day average for players here is 0.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #15,859 by player hours, among the top 72% of all ranked servers.
Getting in
What's the process to join Testing server?
Open Rust and press F1, then type client.connect 95.26.141.240:28015. Alternatively, click Launch Rust on this page to join via Steam.