Skip to the page
RUST ANALYTICS
LIVE42,791PLY11,477SRV
QUOTE 91.51.23.67:28015 Offline checked 23d ago

Error

Players · last
1/ 500
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
1/ 500
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#13,282
top 58%
Rank · 7d ago
#7,264
6018 places down
Last wipe
23d ago
no schedule published
Next wipe
–
too few wipes 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
20 Sep 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

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

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 best
RankRank in region
15k10k15k20k20 Sep22 Sep23 Sep25 Sep26 Sep28 Sep

Top 58% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

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.

wipe-day peak
1
players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 12:30 UTC23d 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. 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 405 on average318/350−43−11.9%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 354 on average186/200−27−12.5%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 335 on average185/200+21+12.9%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 332 on average192/200−24−11.3%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average33/250−7−17.2%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 280 on average180/225−2−1.1%

Quick answers

from the figures on this page

Server Rules

How is Error configured in terms of rules and settings?

No gather rate appears in the name of Error. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.

Which map is played on Error?

A procedural map runs on Error, created by the game.

Player Count

Where does Error sit in the rankings?

For the last seven days, Error holds rank #13,282 on player hours, in the top 58% of all ranked servers.

How many players does Error have?

Right now, Error is offline; the last sighting was 23 days 7 hours ago.

Wipe Cycle

What can you expect on wipe day for Error?

An average of 1 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak.

When does Error schedule its wipes?

There are too few wipes on record for Error to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 23 days 20 hours ago the current world was created.

Server Overview

What is the location of Error?

No region is published by Error. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 91.51.23.67:28015.

Error runs which version of Rust?

The build is Rust network protocol 2633 and build 164530 on Windows, running on Error. Your game needs the same protocol to get in; Steam takes care of the update.

What is the uptime and reliability of Error?

Offline at this moment: Error. Last seen 23 days 7 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. First sighting by Rust Analytics: 20 September 2026.

Server Tags

What is the meaning of the tags on Error?

These tags are published by Error and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp500 (Max players): It holds 500 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): To join, your game needs protocol 2633; cs164530 (Build): It runs build 164530; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent. The tags also carry its current players, queue and world creation time; this page shows them at the top.

On Rust Analytics, which lists and filters feature Error?

On Rust Analytics, Error matches these lists: Rust community servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to Join

What is the process to join Error?

Type client.connect 91.51.23.67: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 means

Published as mp500,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Rust's standard survival mode.
mp500
Max players It holds 500 slots.
ts8
Group limit At the game default, teams hold up to 8.
v2633
Protocol To join, your game needs protocol 2633.
cs164530
Build It runs build 164530.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code The region code is absent.

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.