Testing server
Offline 95.26.147.207:28015 checked 30d 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 bestWipe 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
- 15/ 100
- 4/ 50
- 1/ 50
- 0/ 50
- 2/ 100
- 1/ 50
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. You can find it on the server list by these filters: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o.
How should you read the tags on Testing server?
Testing server's game browser tags read: gmhardcore (Game mode): It's hardcore, with tougher rules; mp1 (Max players): The slot count is 1; ts0 (Group limit): Team play is disabled; v2633 (Protocol): To join, your game has to be on protocol 2633; cs164530 (Build): The build number is 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. 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.147.207:28015.
Is Testing server up, and how often does it stay online?
The server Testing server is not reachable at the moment; the last sighting was 30 days 9 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 17 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Testing server?
Rust network protocol 2633 and build 164530 is what Testing server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
When 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. The world you are on now was created 30 days 10 hours.
Settings and map
What settings are in place on Testing server?
No gather rate appears in the name of Testing server. There is no published group limit. It runs hardcore, Facepunch's most punishing mode. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. The server runs Valve's anti-cheat, VAC.
Which map is active on Testing server?
The map on Testing server is procedural, made by the game.
Population
How many players are on Testing server?
Testing server was last seen 30 days 9 hours ago and is offline as you read this.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #13,262 by player hours, among the top – of all ranked servers.
How to join
What's the way to join Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.147.207:28015. Or click Launch Rust on this page to open the game through Steam and connect.