Testing server
Offline 95.26.139.157:28015 checked 31d 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
- 1/ 50
- 2/ 50
- 0/ 50
- 2/ 100
- 1/ 50
Quick answers
Tags and search
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; 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): The mode is hardcore, which is harsher; mp1 (Max players): There are 1 slots on this server; ts0 (Group limit): You can't form teams; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163794 (Build): It's on build 163794; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^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 details
Where can you find Testing server?
There is no published region for Testing server. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 95.26.139.157:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 31 days 13 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 16 September 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2633 and build 163794. The protocol must match to join; Steam will update your game.
Wipe details
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. This world has been running since 33 days 17 hours ago.
Settings and map
What settings are in place on Testing server?
The name of Testing server contains no gather rate. There is no published group limit. It runs hardcore, The mode Facepunch made hardest. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
What's the map on Testing server?
Testing server uses a game-generated procedural map.
Player count
What's the population like on Testing server?
Testing server was last seen 31 days 13 hours ago and is offline as you read this.
Where does Testing server sit in the rankings?
For player hours in the last seven days, Testing server ranks #13,341, within the top – of ranked servers.
Getting in
What's the way to join Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.139.157:28015. Or click Launch Rust on this page to open the game through Steam and connect.