Testing server
Offline 95.26.145.148:28015 checked 9d 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
- 31/ 400
- 42/ 245
- 132/ 100
- 77/ 1000
- 11/ 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. Its entry appears under the filters 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?
Testing server's game browser tags read: 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; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167231 (Build): It's on build 167231; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
Where can you find Testing server?
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.145.148:28015.
How reliable is Testing server?
Testing server is down at the moment; it was last up 9 days 16 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 8 October 2026.
What is the Rust version for Testing server?
On Windows, Testing server runs Rust network protocol 2634 and build 167231. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does Testing server follow for wipes?
The wipes recorded for Testing server are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 10 days 9 hours ago.
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. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Player count
Is Testing server busy?
Testing server was last seen 9 days 16 hours ago and is offline as you read this.
What's Testing server's rank among Rust servers?
For player hours in the last seven days, Testing server ranks #13,685, within the top 62% of 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.145.148:28015.