RUST METRICSFlight deck · live data
Data live Servers11,643 Players57,901 Populated3,212 Fresh wipes 3 h146 Scan5 min
‹ All servers89.222.104.137:22619
Online Full Queue Fresh wipe Wipe due No query

[ESP/Ñ] DEV

Online EU 89.222.104.137:22619 checked 8m ago

biweekly wipes moddedcarbonpve
COM 1 · connect

Server instruments

last reading Fri 08:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 22 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 67,243 ×1000

Entities

48 h range 61,603–71,032 · memory 3,286 MB
1239 ET SINCE RESTART 03:09

Uptime

3 h 9 min since its last restart, at the last reading
7-day average0peak 1
Rank#8,462top 38% · #2129 in EU
Last wipe1d agobiweekly schedule
Next wipe6d 9hThu 5 Nov, 19:00 UTC FW
Memory3,286MBat the last reading
REC 1

Players

AveragePeakWipe
0123410:0020:0005:0014:0023:0008:00Wiped Wed 28 Oct, 17:36 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
01020304010:0020:0005:0014:0023:0008:00Wiped Wed 28 Oct, 17:36 UTCWIPE

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 9h. The force wipe · high confidence

usual gap10.8 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak1players, last three wipes
crowd held20%else halves by day 2

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 9hFW
  2. WPT 2Wed 11 Nov, 17:36 UTC12d 8h
  3. WPT 3Wed 25 Nov, 17:36 UTC26d 8h
  4. WPT 4Thu 3 Dec, 19:00 UTC34d 9hFW
  5. WPT 5Wed 9 Dec, 17:36 UTC40d 8h

The first 48 hours of its last wipes

Sat 24 OctMon 12 OctThu 1 Oct
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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 17:36 UTC1d ago – – running 0
Sat 24 Oct, 22:04 UTC5d ago 1 halved by day 1 3.8 days 0
Mon 12 Oct, 15:04 UTC17d ago 1 halved by day 2 12.3 days 0
Thu 1 Oct, 19:09 UTC FW28d ago 1 halved by day 2 10.8 days 0
Tue 29 Sep, 17:22 UTC30d ago 1 held half 2.1 days 0
Wed 16 Sep, 16:55 UTC43d ago 1 halved by day 2 13 days 0

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 should you expect from wipe day on [ESP/Ñ] DEV?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 20% of its recent wipes. By day 2 it fell below half when it didn't.

What wipe timing does [ESP/Ñ] DEV follow?

The prediction follows its tag, because too few of [ESP/Ñ] DEV's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 39 hours ago. The tags carry an every-two-weeks wipe schedule.

Tags

How should you read the tags on [ESP/Ñ] DEV?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts12 (Group limit): Teams are capped at 12; 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): Check: wipe cycle. Every two weeks; ^p (PvE): No fighting between players: the world itself is the hazard; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon; EU (Europe): Its browser listing: Europe from [ESP/Ñ] DEV. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [ESP/Ñ] DEV appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [ESP/Ñ] DEV: EU Rust servers, checked, Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.

Occupancy

What position does [ESP/Ñ] DEV hold among Rust servers?

Ranked by seven-day player hours, [ESP/Ñ] DEV sits at #8,462 and #2,129 in Europe, inside the top 38%.

What is the population on [ESP/Ñ] DEV?

Current headcount on [ESP/Ñ] DEV: 0 players, 40 slots available. Check: players over seven days. Average 0, peak 1.

Operator and location

Where does [ESP/Ñ] DEV sit?

Reading: location. The EU tag puts [ESP/Ñ] DEV in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 89.222.104.137:22619.

What Rust version is [ESP/Ñ] DEV on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [ESP/Ñ] DEV. Matching protocol is required to join. Let Steam update your game.

Is performance on [ESP/Ñ] DEV within range?

Check: fps. Average 30 server fps over the last 48 hours, low of 22. Within range. Reading: 71,032 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,944 MB. Expect lag when fps falls and entities climb.

Is [ESP/Ñ] DEV up, and how often does it stay up?

[ESP/Ñ] DEV reports online. Status: normal. By its reported uptime, the last restart was roughly 3 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 15 September 2026.

Rules and settings

What rules does [ESP/Ñ] DEV enforce, and what are its settings?

No gather rate appears in the name: [ESP/Ñ] DEV. Check: group limit. Up to 12 players. Mode check gives pve; fighting between players is off. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on [ESP/Ñ] DEV?

Size 3,500 and seed 1337: the game generates the procedural map on [ESP/Ñ] DEV from them. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Bots y eventos en todo el mapa.

Connection

How do you connect to [ESP/Ñ] DEV?

Check: join. Open Rust, press F1, then enter client.connect 89.222.104.137:22619. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,^z,^y,^b,EU,^p,gmrust,cs168909,ts12

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players The server holds 40 slots.
ts12
Group limit Teams are capped at 12.
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 Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Plugin framework in use: Carbon.

Region

EU
Europe Its browser listing: 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.