Testing server
Offline 95.26.144.122: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
- 10/ 100
- 4/ 50
- 3/ 50
- 0/ 50
- 3/ 100
- 1/ 50
Quick answers
Tags and filters
Where does Testing server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Testing server: Modded Rust servers. Its entry appears under the 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): The slot count is 1; ts0 (Group limit): Team play is disabled; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163794 (Build): This server runs build 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is Testing server in?
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. You can reach it at 95.26.144.122:28015.
What's the uptime like for Testing server?
Testing server is down at the moment; it was last up 32 days 14 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 15 September 2026.
What is the Rust version for Testing server?
Rust network protocol 2633 and build 163794 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
What schedule does Testing server follow for wipes?
Testing server's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 33 days 15 hours is how long ago this world came into being.
Rules and settings
What settings are in place on Testing server?
The name of Testing server contains no gather rate. The group limit is not published. hardcore is the game mode, The mode Facepunch made hardest. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Which map is active on Testing server?
The map on Testing server is procedural, made by the game.
Population
What's the population like on Testing server?
Testing server was last seen 32 days 14 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,258 by player hours, among the top – 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.144.122:28015. Alternatively, click Launch Rust on this page to join via Steam.