Testing server
Offline 95.26.140.51:28015 checked 8d 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 62% 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
- 1001/ 100
- 84/ 400
- 45/ 245
- 127/ 100
- 118/ 1000
- 11/ 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. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on Testing server?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167231 (Build): The build number is 167231; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through 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. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of Testing server?
There is no published region for Testing server. 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.140.51:28015.
What's the uptime like for Testing server?
The server Testing server is not reachable at the moment; the last sighting was 8 days 17 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 9 October 2026.
What is the Rust version for Testing server?
On Windows, Testing server runs Rust network protocol 2634 and build 167231. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
When 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. 9 days 5 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Testing server running?
The name of Testing server contains no gather rate. 8 players is the group cap, the game's default. It runs survival, 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. The server runs Valve's anti-cheat, VAC.
Player count
What's the population like on Testing server?
Testing server was last seen 8 days 17 hours ago and is offline as you read this.
What's Testing server's rank among Rust servers?
Over the last seven days, Testing server is #13,637 by player hours, among the top 62% of all ranked servers.
How to join
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.51:28015.