Testing server
Offline 95.26.141.224:28015 checked 23d 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 60% 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
- 833/ 100
- 112/ 400
- 91/ 245
- 128/ 100
- 245/ 1000
- 18/ 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): This is the standard Rust survival experience; mp1 (Max players): It holds 1 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — 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
Where can you find Testing server?
Testing server does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 95.26.141.224:28015.
What's the uptime like for Testing server?
The server Testing server is not reachable at the moment; the last sighting was 23 days 6 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 24 September 2026 is when Rust Going Deep first saw it.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2633 and build 165217, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
When does Testing server wipe?
Too few wipes are on record for Testing server to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 24 days 7 hours ago.
Settings and map
Which rules and settings is Testing server running?
No gather rate appears in the name of Testing server. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. The server runs Valve's anti-cheat, VAC.
Population
How many players are on Testing server?
Right now Testing server is offline, with its last appearance 23 days 6 hours ago.
Where does Testing server sit in the rankings?
Over the last seven days, Testing server is #13,424 by player hours, among the top 60% of all 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.224:28015.