Testing server
Offline 95.26.140.86: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
- 17/ 100
- 234/ 400
- 178/ 225
- 134/ 100
- 278/ 1000
- 22/ 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. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read 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): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; 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 — that is the tag list Testing server puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is Testing server in?
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. The endpoint is 95.26.140.86:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 21 days 3 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 27 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 165217. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
How often does Testing server wipe?
Too few wipes are on record for Testing server to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 24 days 16 hours is how long ago this world came into being.
Rules and settings
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. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Player stats
What's the population like on Testing server?
Right now Testing server is offline, with its last appearance 21 days 3 hours ago.
What's Testing server's rank among Rust servers?
For player hours in the last seven days, Testing server ranks #14,490, within the top 61% of ranked servers.
Getting in
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.140.86:28015.