RUST METRICSFlight deck · live data
Data live Servers11,787 Players83,125 Populated3,861 Fresh wipes 3 h158 Scan5 min
‹ All servers91.122.158.45:26015
Offline Full Queue Fresh wipe Wipe due No query

#3

Offline EU 91.122.158.45:26015 checked 1d ago

biweekly wipes pve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,437top 69% · #2583 in EU
Last wipe1d agobiweekly schedule
Next wipe8d 3hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

AveragePeakWipe
0123408:0009:0010:0011:00Wiped Tue 27 Oct, 08:16 UTCWIPE

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Oct28 Oct

Top 69% of all ranked servers, top 88% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 8d 3h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does #3 follow?

An estimate from the force wipe gives #3's next wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 31 hours ago. The tags carry an every-two-weeks wipe schedule.

Lists and filters

How should you read the tags on #3?

These are the tags #3 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): It wipes once a fortnight; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; EU (Europe): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show #3?

Rust Metrics lists featuring #3: EU Rust servers, checked, Rust community servers: live readings and Rust PvE servers. Reading: server list filters. It comes up under Region: Europe; Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.

Occupancy

What position does #3 hold among Rust servers?

Top 69% of all ranked servers: #3 takes #15,437 on seven-day player hours and #2,583 in Europe.

What player count does #3 carry?

Reading for #3: offline at this moment; last seen 27 hours ago. Seven-day reading: 0 players on average.

Server details

Where does #3 sit?

Its EU tag places #3 in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 91.122.158.45:26015.

What Rust version is #3 on?

Rust network protocol 2635 and build 168909 on Windows is the build #3 runs. Matching protocol is required to join. Let Steam update your game.

How reliable is #3, and is it online now?

#3 reports offline. The last reading came 27 hours ago. Check: first contact. Rust Metrics logged it on 27 October 2026.

Rules and settings

What settings and rules apply on #3?

Reading the name gives no gather rate for #3. The group cap is 8 players, which is the default in the game. Mode check gives pve; fighting between players is off. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on #3?

The game generates a procedural map for #3.

Connection

How do you connect to #3?

Press F1 in Rust and enter client.connect 91.122.158.45:26015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^b,EU,^p,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Region

EU
Europe The server browser files it under Europe.

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.