Testing server
Offline 95.26.140.54:28015 checked 27d 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 bestWipe 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
- 944/ 100
- 171/ 400
- 130/ 245
- 125/ 100
- 384/ 1000
- 25/ 700
Quick answers
Tags and search
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. The server list shows it under 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): This is the standard Rust survival experience; 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; cs164530 (Build): It's on build 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. 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
Where can you find Testing server?
Testing server does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 95.26.140.54:28015.
What's the uptime like for Testing server?
Testing server is down at the moment; it was last up 27 days 13 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 20 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for Testing server?
On Windows, Testing server runs Rust network protocol 2633 and build 164530. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
How often does Testing server wipe?
Too few wipes are on record for Testing server to show 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 27 days 14 hours.
Settings and map
What settings are in place on Testing server?
The name of Testing server contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, 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.
Population
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 27 days 13 hours ago.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #13,295 by player hours, among the top – of all ranked servers.
Join info
What's the process 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.54:28015.