TEST SERVER STAGING
Offline 176.241.26.3: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 61% 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
- 125/ 100
- 246/ 1000
- 18/ 700
Quick answers
Tags and search
Where does TEST SERVER STAGING appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TEST SERVER STAGING: 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 TEST SERVER STAGING?
The server browser shows these tags for TEST SERVER STAGING: gmvanilla (Game mode): It's vanilla survival; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs165964 (Build): The build number is 165964; 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. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server details
Where can you find TEST SERVER STAGING?
TEST SERVER STAGING does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 176.241.26.3:28015.
How reliable is TEST SERVER STAGING?
Right now TEST SERVER STAGING is offline, having last been seen 20 days 8 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 25 September 2026.
What Rust version is TEST SERVER STAGING on?
On Windows, TEST SERVER STAGING runs Rust network protocol 2634 and build 165964. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does TEST SERVER STAGING wipe?
The wipes recorded for TEST SERVER STAGING are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 22 days 4 hours.
Map and rules
What settings and rules have been applied to TEST SERVER STAGING?
No gather rate appears in the name of TEST SERVER STAGING. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is off: Valve's anti-cheat is not active.
What's the map on TEST SERVER STAGING?
TEST SERVER STAGING uses a game-generated procedural map.
Population
What's the population like on TEST SERVER STAGING?
TEST SERVER STAGING was last seen 20 days 8 hours ago and is offline as you read this.
Where does TEST SERVER STAGING sit in the rankings?
Over the last seven days, TEST SERVER STAGING is #14,545 by player hours, among the top 61% of all ranked servers.
Join info
What's the process to join TEST SERVER STAGING?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 176.241.26.3:28015.