Testing server
Offline 95.26.145.6:28015 checked 32d 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?
The server browser shows these tags for Testing server: gmhardcore (Game mode): It's hardcore, with tougher rules; mp1 (Max players): There are 1 slots on this server; ts0 (Group limit): No teams here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): The build number is 163794; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded category fits: plugins or settings are in play. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What's the location of Testing server?
There is no published region for 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.145.6:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 32 days 10 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 15 September 2026.
What Rust version is Testing server on?
Rust network protocol 2633 and build 163794 is what Testing server runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
When 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 33 days 17 hours.
Rules and settings
What settings are in place on Testing server?
Its name does not state a gather rate for Testing server. There is no published group limit. hardcore is the game mode, The hardest option from Facepunch. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.
Which map is active on Testing server?
Testing server uses a game-generated procedural map.
Player count
Is Testing server busy?
The last sighting of Testing server was 32 days 10 hours ago; it is offline right now.
What position does Testing server hold in the server rankings?
For player hours in the last seven days, Testing server ranks #13,340, within the top – of ranked servers.
Join info
How do you get into Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.145.6:28015. Or click Launch Rust on this page to open the game through Steam and connect.