Testing server
Offline 95.26.141.163:28015 checked 28d 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
- 1000/ 100
- 168/ 400
- 127/ 245
- 132/ 100
- 369/ 1000
- 28/ 700
Quick answers
Tags and search
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.
What's the meaning of 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): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): The build number is 164530; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^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. 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 location is Testing server in?
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. The endpoint is 95.26.141.163:28015.
How reliable is Testing server?
Testing server is down at the moment; it was last up 28 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 19 September 2026.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2633 and build 164530. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
When does Testing server wipe?
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. The world you are on now was created 29 days 13 hours.
Map and rules
What settings are in place on Testing server?
No gather rate appears in the name of Testing server. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. 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.
Which map is active on Testing server?
A procedural map, generated by the game, is in play on Testing server.
Player stats
Is Testing server busy?
Right now Testing server is offline, with its last appearance 28 days 6 hours ago.
What position does Testing server hold in the server rankings?
For player hours in the last seven days, Testing server ranks #13,266, within the top – of ranked servers.
How to join
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.141.163:28015.