TEST SERVER STAGING
Key statistics
the figures behind the quote- Players now
- 1/ 1 100% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #14,545 top 61%
- Rank · 7d ago
- #10,696 ▼3849 places down
- Last wipe
- 18d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 1 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 25 Sep 2026 no hostname published
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
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 109 on average | 33/245 | ▲+9+39.9% | |
| 2 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 89/100 | ▼−1−1.5% | |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 14/1000 | ▼−1−7.2% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 5/1000 | ▼−3−34.8% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average | 18/700 | ▼−32−64.4% | |
| 6 | SURVIVORS.GG | 2 x Vanilla | Monthlygroups of 30+ · monthly · 72 on average | 26/200 | ▲+10+63.4% |
Quick answers
from the figures on this pageServer Rules
How is TEST SERVER STAGING configured in terms of rules and settings?
The name of TEST SERVER STAGING carries no gather rate. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched off.
Which map is played on TEST SERVER STAGING?
The game generates the procedural map on TEST SERVER STAGING.
Activity
What position does TEST SERVER STAGING hold in the server rankings?
For the last seven days, TEST SERVER STAGING holds rank #14,545 on player hours, in the top 61% of all ranked servers.
What is the population on TEST SERVER STAGING?
At present, TEST SERVER STAGING is offline; the last sighting was 16 days 8 hours ago.
Wipe Cycle
When does TEST SERVER STAGING schedule its wipes?
There are too few wipes on record for TEST SERVER STAGING to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 18 days 5 hours old.
Server Details
Where can TEST SERVER STAGING be found?
For TEST SERVER STAGING, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 176.241.26.3:28015.
What Rust version is TEST SERVER STAGING running?
Rust network protocol 2634 and build 165964 on Windows is what TEST SERVER STAGING runs. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of TEST SERVER STAGING?
No response from TEST SERVER STAGING. It was last seen 16 days 8 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. The earliest Rust Analytics saw it was 25 September 2026.
Tags and Rankings
What is the meaning of the tags on TEST SERVER STAGING?
Published by TEST SERVER STAGING for the game's server browser to read: gmvanilla (Game mode): Survival in its vanilla form; mp1 (Max players): Slot count: 1; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs165964 (Build): Game build: 165964; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does TEST SERVER STAGING show up in Rust Analytics lists and filters?
These Rust Analytics lists include TEST SERVER STAGING: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to Join
What steps do I take to join TEST SERVER STAGING?
Type client.connect 176.241.26.3:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp1,ptrak,$r?,v2634,gmvanilla,cs165964,ts8,^o^z
Game
gmvanilla
mp1
ts8
v2634
cs165964
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.