Testing server
Offline 95.26.142.151: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 48% 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
- 20/ 100
- 172/ 400
- 107/ 225
- 130/ 100
- 151/ 1000
- 6/ 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?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $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 — 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 details
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. You can reach it at 95.26.142.151:28015.
How reliable is Testing server?
Right now Testing server is offline, having last been seen 4 days 17 hours ago. Over the past full 4 days it stayed up for 0 of 96 hours, or 0%. 13 October 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 2634 and build 167781. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
What schedule does Testing server follow for wipes?
Too few wipes are on record for Testing server to show 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 5 days 19 hours ago.
Settings and map
What settings are in place on Testing server?
No gather rate appears in the name of Testing server. 8 players is the group cap, the game's default. It runs survival, 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.
Player stats
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 4 days 17 hours ago. For the past week, players averaged 1 with a high of 1.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #10,685 by player hours, among the top 48% of all ranked servers.
How to join
How do you get into Testing server?
Open Rust and press F1, then type client.connect 95.26.142.151:28015. Alternatively, click Launch Rust on this page to join via Steam.