Testing server
Offline 95.26.139.46:28015 checked 15d 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
- 6/ 100
- 86/ 400
- 52/ 245
- 126/ 100
- 139/ 1000
- 14/ 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. The server list shows it under 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): There are 1 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166586 (Build): It's on build 166586; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through 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
What location is Testing server in?
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.46:28015.
How reliable is Testing server?
Testing server is down at the moment; it was last up 15 days 3 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 2 October 2026.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2634 and build 166586. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
When does Testing server wipe?
The wipes recorded for Testing server are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 15 days 11 hours.
Rules and settings
What settings and rules have been applied to Testing server?
The name of Testing server contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, 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. Oxide plugins are running here. The server runs Valve's anti-cheat, VAC.
Population
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 15 days 3 hours ago.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,842 by player hours, among the top 61% of all ranked servers.
Join info
What's the way to join Testing server?
To join, open Rust, hit F1, and enter client.connect 95.26.139.46:28015. Or click Launch Rust on this page to open the game through Steam and connect.