Testing server
Offline 95.26.139.171:28015 checked 21d 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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 78/ 400
- 66/ 245
- 126/ 100
- 174/ 1000
- 17/ 700
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. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Testing server?
The server browser shows these tags for Testing server: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): It's on build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What's the location of 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.139.171:28015.
How reliable is Testing server?
Right now Testing server is offline, having last been seen 21 days 17 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 26 September 2026.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2633 and build 165217. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does Testing server follow for wipes?
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 24 days 8 hours ago.
Map and rules
What settings are in place on Testing server?
Its name does not state a gather rate for Testing server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Player count
How many players are on Testing server?
The last sighting of Testing server was 21 days 17 hours ago; it is offline right now.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #14,198 by player hours, among the top 61% of all ranked servers.
Join info
What's the way to join Testing server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 95.26.139.171:28015.