Rust StatisticsWorking papers on every public Rust server · 34,720 players now

Error

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 37d ago · 91.51.23.67:28015

Abstract

We describe the public Rust server Error, reached at 91.51.23.67:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,282 of all servers, the top 58%. It last wiped 37d 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.
MeasureValueNote
Players now1/5000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,282top 58%
Last wipe37d agono schedule published
Next wipe3–too few wipes 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 memory4. 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 58% 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
15k10k15k20k20 Sep22 Sep23 Sep25 Sep26 Sep28 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

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

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sun 20 Sep, 12:3037d ago 1 – running 1

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 5: The map: Procedural Map.
Table 4: The server's published settings.
Address91.51.23.67:28015
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe20 Sep 2026, 12:30 UTC
Hostname–
First seen20 Sep 2026
MapProcedural 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 busiest community rust servers [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 534 on average253/275
Rustoria.co - EU MainEU · groups of 16+ · weekly · 322 on average20/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 321 on average16/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average167/200
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average62/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average39/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Error?

No region is published by Error. Rust Statistics does not look up the machine's location; it shows where the server says it is. 91.51.23.67:28015 is its address.

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

Right now, Error is offline, and the last time it was seen was 37 days 4 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 20 September 2026 by Rust Statistics.

A.3What is the Rust version for Error?

Rust network protocol 2633 and build 164530 is the version that Error runs, on Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4When are wipes carried out on Error?

There are not yet enough recorded wipes for Error to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 37 days 17 hours have passed since the current world was generated.

A.5What characterises wipe day on Error?

Recent wipes saw an average peak of 1 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6How does Error compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Error at #13,282, within the top 58% of ranked servers.

A.7At what level does Error operate in terms of players?

At this moment Error is offline, having last been seen 37 days 4 hours ago.

Tags and filters

A.8What is the meaning of the tags on Error?

Tags from Error, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp500 (Max players): The slot count is 500; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to connect; cs164530 (Build): This server runs game build 164530; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can Error be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Error: Rust community servers, measured. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.10Which settings and rules are in force on Error?

Its name carries no gather rate for Error. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.11On which map does Error take place?

A procedural map, generated by the game, is what Error runs.

Connection

A.12What steps are required to join Error?

Enter client.connect 91.51.23.67:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

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

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp500Max players. The slot count is 500.
ts8Group limit. The team cap is 8, which is the game default.
v2633Protocol. Your game must run protocol 2633 to connect.
cs164530Build. This server runs game build 164530.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.

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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.