RS-16537Community server
stagingtest
Offline 167.114.158.11:28220 checked 13d 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
Top 70% 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
| 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.
Quick answers
From the figures on this page.
Population
What is the typical player count on stagingtest?
stagingtest is offline at this moment; the last signal was 13 days 14 hours ago.
How is stagingtest ranked?
Ranked #16,537 on seven-day player hours, stagingtest is in the top 70% of all ranked servers.
Server tags and lists
On Top Rust Servers, which lists and filters carry stagingtest?
These Top Rust Servers lists include stagingtest: Best Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is the meaning of the tags on stagingtest?
The game's server browser reads the tags that stagingtest publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp100 (Max players): Player slots: 100; ts8 (Group limit): The team limit is 8, which is the game default; v2633 (Protocol): To join, your game must be on protocol 2633; cs165217 (Build): Running game build 165217; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): The region code is left blank. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.
Rules, settings, and map
Which map is running on stagingtest?
A procedural map, created by the game, is in use on stagingtest.
Which settings and rules apply on stagingtest?
The name stagingtest does not state a gather rate. The group limit is the game's default of 8 players. It runs survival, standard survival: gathering, building and raiding. Combat and raiding between players are allowed. It appears under Community in the server browser and is a community server. VAC, Valve's anti-cheat, is enabled.
About the server
What is the Rust version on stagingtest?
On Linux, stagingtest operates Rust network protocol 2633 and build 165217. Your game needs the same protocol to connect; Steam takes care of updating it.
Where can stagingtest be found?
A region is not published by stagingtest. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 167.114.158.11:28220.
What is the uptime of stagingtest?
Currently offline is stagingtest, last seen 13 days 14 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. The first time Top Rust Servers saw it was on 30 September 2026.
Wipe details
When does stagingtest wipe?
Not enough wipe data exists yet to identify the rhythm of stagingtest. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. Its world was last replaced 14 days 5 hours ago.
How to join
What are the steps to join stagingtest?
To connect, start Rust, hit F1, and enter client.connect 167.114.158.11:28220. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.