Testing server
Offline 95.26.142.164:28015 checked 9d 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 66% 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
- 836/ 100
- 110/ 400
- 105/ 245
- 123/ 100
- 263/ 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. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What's the meaning of 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): The protocol is 2634; a different version won't get you in; cs167231 (Build): This server runs build 167231; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^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. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
About the server
What's the location of Testing server?
No region comes from Testing server. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 95.26.142.164:28015.
How reliable is Testing server?
Right now Testing server is offline, having last been seen 9 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 8 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Testing server?
Rust network protocol 2634 and build 167231 is what Testing server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
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. This world has been running since 9 days 6 hours ago.
Map and rules
What settings are in place on Testing server?
No gather rate appears in the name of Testing server. The group limit is the game's default of 8 players. survival is the game mode, 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. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Player stats
What's the population like on Testing server?
The last sighting of Testing server was 9 days 6 hours ago; it is offline right now.
What's Testing server's rank among Rust servers?
For player hours in the last seven days, Testing server ranks #14,527, within the top 66% of ranked servers.
Join info
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.142.164:28015.