Rust Server TrendsSeismic network · station log
Recording Stations11,703 Players41,069 Active3,025 Wipes · 3 h98 48 h

Station EU-16363 · no signal

Devblog 301 LAN

Offline 94.139.255.199:28015 checked 33d ago

pve
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,363
top 71%
Last wipe
35d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station EU-16363 · 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 20 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. 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
15k10k15k20k24 Sep26 Sep27 Sep29 Sep30 Sep2 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
ABYSS | PvE | US | Vanilla | Noob Friendly NA · groups of 8+ · monthly · 54 on average
80/ 200
[EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EU · groups of 8+ · monthly · 33 on average
13/ 200
[US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding NA · groups of 8+ · monthly · 31 on average
39/ 200
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 EA · groups of 30+ · monthly · 22 on average
10/ 200
[PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly groups of 8+ · monthly · 21 on average
29/ 150
[EU/GER] Rust Norddeutschland PVE EU · groups of 8+ · biweekly · 16 on average
1/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Devblog 301 LAN?

A procedural map runs on Devblog 301 LAN, generated by the game.

Which settings and rules apply on Devblog 301 LAN?

You will find no gather rate in the name of Devblog 301 LAN. At the game's default, groups can have up to 8 players. It plays in pve mode, no player-versus-player fighting. It is a community server, and the browser lists it under Community. Anti-cheat is off: VAC, from Valve.

Population

How many players are recorded on Devblog 301 LAN right now?

A reading taken now finds Devblog 301 LAN offline; the most recent activity was 33 days 11 hours ago.

How does Devblog 301 LAN rank against other Rust servers?

On player hours for the past week, Devblog 301 LAN sits at #16,363, which puts it inside the top 71% of every ranked server.

Server facts

How reliably does Devblog 301 LAN stay online?

As recorded now, Devblog 301 LAN is not reachable, the last contact having been 33 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 24 September 2026 is when Rust Server Trends first recorded it.

Which region does Devblog 301 LAN run from?

No region comes from Devblog 301 LAN, though its region code is eu1. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 94.139.255.199:28015 is the address it uses.

Which Rust version is Devblog 301 LAN running?

On Windows, Devblog 301 LAN runs Rust network protocol 2602 and build 132924. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does Devblog 301 LAN run its wipes?

Too few wipes of Devblog 301 LAN are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 35 days 16 hours is how long the current world has been running.

Lists and tags

What do the server tags on Devblog 301 LAN mean?

Tags published by Devblog 301 LAN and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): The server has 20 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2602 (Protocol): Your game needs to be on protocol 2602 to join; cs132924 (Build): The game build is 132924; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $reu1 (Region code): You'll see it listed with the region code eu1; ^p (PvE): The danger comes from the world, not from other players. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Devblog 301 LAN appear?

The Rust Server Trends lists that take in Devblog 301 LAN are: Rust community servers without the side modes and Rust PvE servers. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Connecting

What steps get you onto Devblog 301 LAN?

You can connect by pressing F1 in Rust and typing client.connect 94.139.255.199: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 mp20,ptrak,$reu1,v2602,^p,gmrust,cs132924,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players The server has 20 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2602
Protocol Your game needs to be on protocol 2602 to join.
cs132924
Build The game build is 132924.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$reu1
Region code You'll see it listed with the region code eu1.

Gameplay

^p
PvE The danger comes from the world, not from other players.

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.