stagingtest

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 27d ago · 167.114.158.11:28220

Abstract

We describe the public Rust server stagingtest, reached at 167.114.158.11:28220. It is offline at the last check, against a seven-day mean of 0¹. It ranks #16,537 of all servers, the top 70%. It last wiped 28d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/100	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#16,537	top 70%
Last wipe	28d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: 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.

4Rank

The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

Address	`167.114.158.11:28220`
Region	–
Max players	100
Group limit	8, the default
Wipe schedule	–
Last wipe	30 Sep 2026, 21:37 UTC
Hostname	–
First seen	30 Sep 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are community tab servers measured [2] and predicted wipe schedule [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rusty Moose \|EU Mondays\|EU · groups of 12+ · weekly · 553 on average	504/575
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average	339/400
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 297 on average	39/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average	35/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average	105/150
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average	126/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of stagingtest?

A region is not published by stagingtest. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 167.114.158.11:28220.

A.2What is the online status and reliability of stagingtest?

Right now, stagingtest is offline, and the last time it was seen was 27 days 9 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. The first record of it by Rust Statistics dates to 30 September 2026.

A.3What version of Rust is run on stagingtest?

stagingtest is running Rust network protocol 2633 and build 165217 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4When are wipes carried out on stagingtest?

The record of stagingtest's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 28 days.

Population

A.5What position does stagingtest occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts stagingtest at #16,537, within the top 70% of ranked servers.

A.6At what level does stagingtest operate in terms of players?

stagingtest is not online now; 27 days 9 hours have passed since it was last seen.

Tags, lists

A.7How should the tags on stagingtest be interpreted?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp100 (Max players): It offers 100 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs165217 (Build): Build 165217 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset, which stagingtest publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can stagingtest be found among the Rust Statistics lists and filters?

These Rust Statistics lists include stagingtest: Rust community servers, measured. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.9What are the settings and rules that govern stagingtest?

Its name carries no gather rate for stagingtest. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Players may raid and fight one another. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

A.10On which map does stagingtest take place?

On stagingtest the terrain is procedural, built by the game itself.

Connection

A.11How do you connect to stagingtest?

Press F1 inside Rust to open the console and enter client.connect 167.114.158.11:28220. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp100,ptrak,$r?,v2633,gmrust,cs165217,ts8.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp100`	Max players. It offers 100 slots.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2633`	Protocol. The game protocol is 2633; your client must match it to join.
`cs165217`	Build. Build 165217 is the one running.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. The region code is unset.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.