A166/ 200 players
PvE#16,363
Devblog 301 LAN
Offline 94.139.255.199:28015 checked 19d ago
pve
players now0of 20 slots
7-day average0peak –
rank#16,363top 71%
last wipe · restocked21d agono schedule published
next wipe · restock–no wipe seen yet
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 bestRankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A236/ 200 players
A341/ 200 players
B112/ 300 players
B213/ 200 players
B315/ 100 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
How should you read the tags on Devblog 301 LAN?
The server browser reads these tags that Devblog 301 LAN publishes: gmrust (Game mode): Rust survival, the standard way; mp20 (Max players): Room for 20; ts8 (Group limit): The default cap is 8 per team; v2602 (Protocol): Protocol 2602: your game must match to get in; cs132924 (Build): Game build: 132924; ptrak (Networking): The game's usual network layer, RakNet, is used; $reu1 (Region code): Region code on file: eu1; ^p (PvE): No player-on-player fighting: the danger comes from the world. Tags also carry its current players, its queue and when the world was made, all up top on this page.
Where does Devblog 301 LAN appear in the lists and filters on Rust Vending Machine?
These Rust Vending Machine lists include Devblog 301 LAN: Community Rust servers in stock and PvE Rust servers in stock. It shows under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Rules & map
What map is in play on Devblog 301 LAN?
Generated by the game, the map on Devblog 301 LAN is procedural.
Which settings and rules apply on Devblog 301 LAN?
The name of Devblog 301 LAN gives no gather rate. 8 players is the default group size, and that is the cap here. pve is the game mode, no player-versus-player fighting. The server browser puts it under Community: it is a community server. VAC, Valve's anti-cheat, is disabled.
Server details
Where can you find Devblog 301 LAN?
No region is shown for Devblog 301 LAN, and the region code reads eu1. Rust Vending Machine reports the location a server claims, not where the machine actually sits. You can reach it at 94.139.255.199:28015.
How reliable is Devblog 301 LAN, and is it online now?
No stock at present: Devblog 301 LAN is offline, last seen 19 days 6 hours ago. Over 7 full days, the shelves were stocked for 0 of 168 hours (0%). The first sighting of it on Rust Vending Machine was 24 September 2026.
What Rust version does Devblog 301 LAN run?
On Windows, Devblog 301 LAN is running Rust network protocol 2602 and build 132924. The protocol has to line up on your side to join, and Steam does the updating.
Player count
What is Devblog 301 LAN's rank among Rust servers?
Over the last seven days Devblog 301 LAN ranks #16,363 on player hours, among the top 71% of all ranked servers.
How many players are on Devblog 301 LAN right now?
At the moment Devblog 301 LAN is offline, with a last sighting 19 days 6 hours ago.
Wipe details
On what schedule does Devblog 301 LAN wipe?
The wipes of Devblog 301 LAN on record are too few to show its rhythm. The next force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. It has been running its current world since 21 days 11 hours ago.
Getting in
What is the way to join Devblog 301 LAN?
In the Rust console (F1), type client.connect 94.139.255.199:28015. You can also press Launch Rust on this page, which opens Steam and connects.
Server tags
what each one meansPublished as mp20,ptrak,$reu1,v2602,^p,gmrust,cs132924,ts8
Game
gmrust
Game mode Rust survival, the standard way.
mp20
Max players Room for 20.
ts8
Group limit The default cap is 8 per team.
v2602
Protocol Protocol 2602: your game must match to get in.
cs132924
Build Game build: 132924.
ptrak
Networking The game's usual network layer, RakNet, is used.
$reu1
Region code Region code on file: eu1.
Gameplay
^p
PvE No player-on-player fighting: the danger comes from the world.
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.