Testing server
Offline 95.26.137.120:28015 checked 4d 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 57% 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
- 266/ 400
- 182/ 225
- 129/ 100
- 328/ 1000
- 23/ 700
Quick answers
Tags and listings
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. 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; Last wipe: In the last week.
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): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^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 info
What's the location of Testing server?
Testing server does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 95.26.137.120:28015.
What's the uptime like for Testing server?
Testing server is down at the moment; it was last up 4 days ago. It was up 0% of the time over the last full 3 days, 0 of 72 hours. 14 October 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2634 and build 167781. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Testing server wipe?
Testing server's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 5 days 22 hours is how long ago this world came into being.
Map and rules
What settings are in place on 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. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Player count
Is Testing server busy?
Right now Testing server is offline, with its last appearance 4 days ago. The seven-day average is 1 players, with a peak of 1.
What's Testing server's rank among Rust servers?
Over the last seven days, Testing server is #12,662 by player hours, among the top 57% of all ranked servers.
Join info
What's the way to join Testing server?
Open Rust and press F1, then type client.connect 95.26.137.120:28015. Alternatively, click Launch Rust on this page to join via Steam.