Testing server
Offline 95.26.142.163:28015 checked 17d 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
- 0/ 100
- 85/ 400
- 51/ 245
- 123/ 100
- 88/ 1000
- 5/ 700
Quick answers
Tags and search
Where does Testing server appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Testing server are: 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?
gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): It's on build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^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 details
What's the location of 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. To connect, use 95.26.142.163:28015.
How reliable is Testing server?
The server Testing server is not reachable at the moment; the last sighting was 17 days 16 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 30 September 2026.
What Rust version is Testing server on?
The version on Testing server is Rust network protocol 2633 and build 165217, on Windows. The protocol must match to join; Steam will update your game.
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. 17 days 16 hours is how long ago this world came into being.
Map and rules
Which rules and settings is Testing server running?
The name of Testing server contains no gather rate. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Population
What's the population like on Testing server?
The last sighting of Testing server was 17 days 16 hours ago; it is offline right now.
What's Testing server's rank among Rust servers?
Over the last seven days, Testing server is #14,436 by player hours, among the top 60% of all ranked servers.
Join info
What's the process to join Testing server?
Open Rust and press F1, then type client.connect 95.26.142.163:28015. Alternatively, click Launch Rust on this page to join via Steam.