Testing server
Offline 95.26.144.228:28015 checked 20d 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 67% 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
- 262/ 400
- 184/ 225
- 126/ 100
- 320/ 1000
- 22/ 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.
How should you read the tags on Testing server?
The server browser shows these tags for Testing server: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): Standard RakNet networking; $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. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
What location is Testing server in?
Testing server does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 95.26.144.228:28015.
How reliable is Testing server?
Testing server is down at the moment; it was last up 20 days 15 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 27 September 2026.
What Rust version is Testing server on?
On Windows, Testing server runs Rust network protocol 2633 and build 165217. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does Testing server follow for wipes?
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. This world has been running since 24 days 16 hours ago.
Rules and settings
What settings and rules have been applied to Testing server?
No gather rate appears in the name of Testing server. The group limit is the game's default of 8 players. 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. The server runs Valve's anti-cheat, VAC.
Player count
How many players are on Testing server?
Testing server was last seen 20 days 15 hours ago and is offline as you read this.
What position does Testing server hold in the server rankings?
Over the last seven days, Testing server is #15,935 by player hours, among the top 67% 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.228:28015. Alternatively, click Launch Rust on this page to join via Steam.