Testing server
Offline 95.26.144.121:28015 checked 4d 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 52% 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
- 994/ 100
- 193/ 400
- 171/ 245
- 124/ 100
- 451/ 1000
- 25/ 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 week.
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): It holds 1 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167584 (Build): This server runs build 167584; ptrak (Networking): RakNet, the network layer Rust uses by 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.
About the server
Where can you find Testing server?
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.121:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 4 days 14 hours ago. In the last full 3 days, 0 of 72 hours were online, 0% uptime. Rust Going Deep has had it on record since 13 October 2026.
What is the Rust version for Testing server?
Rust network protocol 2634 and build 167584 is what Testing server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Testing server wipe?
The wipes recorded for Testing server are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 5 days 10 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to Testing server?
The name of Testing server contains no gather rate. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Player stats
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 4 days 14 hours ago. For the past week, players averaged 1 with a high of 1.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #11,498 by player hours, among the top 52% of all ranked servers.
Getting in
What's the way to join Testing server?
Open Rust and press F1, then type client.connect 95.26.144.121:28015. Alternatively, click Launch Rust on this page to join via Steam.