Testing server
Offline 95.26.144.163: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
- 229/ 400
- 174/ 225
- 132/ 100
- 274/ 1000
- 21/ 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. 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?
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): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded category fits: plugins or settings are in play — 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. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 95.26.144.163:28015.
Is Testing server up, and how often does it stay online?
The server Testing server is not reachable at the moment; the last sighting was 21 days 15 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 26 September 2026.
What is the Rust version for Testing server?
On Windows, Testing server runs Rust network protocol 2633 and build 165217. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
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. 24 days 16 hours is how long ago this world came into being.
Rules and settings
What settings are in place on Testing server?
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. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.
Population
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 21 days 15 hours ago.
What's Testing server's rank among Rust servers?
For player hours in the last seven days, Testing server ranks #14,326, within the top 61% of ranked servers.
Getting in
How do you get into 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.144.163:28015.