Rust Server TrendsSeismic network · station log
Recording Stations11,894 Players99,159 Active3,939 Wipes · 3 h396 48 h

Station XX-16905 · no signal

Ямало-Ненецкий

Offline 79.140.252.222:28015 checked 30d ago

moddedoxide
Connect
Players now
0/ 41
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,905
top 71%
Last wipe
30d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-16905 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 41 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep28 Sep30 Sep2 Oct4 Oct6 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
0.4 daysbetween real wipes
on rhythm
67%of its recent wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

Tue 29 SepMon 28 SepMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 05:05 UTC30d ago M0.0steady 0 – – running 0
Mon 28 Sep, 12:10 UTC31d ago M0.0steady 1 – 0.7 days 1
Mon 28 Sep, 01:44 UTC31d ago M0.0rising 1 – 0.4 days 0
Sun 27 Sep, 15:17 UTC32d ago M0.0steady 1 – 0.4 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
133/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
185/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
94/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 88 on average
231/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average
348/ 350
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
29/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Ямало-Ненецкий?

The procedural map on Ямало-Ненецкий is size 3,500 with seed 1234, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Ямало-Ненецкий?

The name of Ямало-Ненецкий gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on Ямало-Ненецкий right now?

Ямало-Ненецкий is not responding at this moment and is offline, last seen 30 days 11 hours ago.

How does Ямало-Ненецкий rank against other Rust servers?

Over the last seven days, Ямало-Ненецкий recorded enough player hours to reach #16,905 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does Ямало-Ненецкий stay online?

Ямало-Ненецкий is down at the moment; the last recorded contact was 30 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 26 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Ямало-Ненецкий run from?

The name of Ямало-Ненецкий points to Europe, even though it publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 79.140.252.222:28015.

Which Rust version is Ямало-Ненецкий running?

Ямало-Ненецкий is running Rust network protocol 2633 and build 164530 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on Ямало-Ненецкий?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.

How often does Ямало-Ненецкий wipe, and on which days?

There is no next wipe to predict at Ямало-Ненецкий, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 30 days 11 hours.

Server tags

What do the server tags on Ямало-Ненецкий mean?

These are the tags Ямало-Ненецкий publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp41 (Max players): Slots: 41; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): It runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Ямало-Ненецкий appear?

The Rust Server Trends lists that take in Ямало-Ненецкий are: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto Ямало-Ненецкий?

You can connect by pressing F1 in Rust and typing client.connect 79.140.252.222:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp41,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp41
Max players Slots: 41.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs164530
Build It runs game build 164530.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.