Testing server
Offline 95.26.147.40:28015 checked 28d 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
- 1000/ 100
- 234/ 400
- 212/ 245
- 120/ 100
- 498/ 1000
- 43/ 700
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; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on Testing server?
gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): It holds 1 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs164530 (Build): This server runs build 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list Testing server puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
Where can you find Testing server?
Testing server does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 95.26.147.40:28015.
How reliable is Testing server?
Right now Testing server is offline, having last been seen 28 days 11 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 19 September 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2633 and build 164530, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
How often does Testing server wipe?
Too few wipes are on record for Testing server to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 29 days 11 hours ago.
Rules and settings
What settings are in place on Testing server?
The name of Testing server contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Which map is active on Testing server?
Testing server uses a game-generated procedural map.
Player count
How many players are on Testing server?
The last sighting of Testing server was 28 days 11 hours ago; it is offline right now.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,269 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.147.40:28015. Alternatively, click Launch Rust on this page to join via Steam.