Working its way up from the back of the class: #16,363 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 579 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
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 best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The region code for Devblog 301 LAN is eu1, but no region is published. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 94.139.255.199:28015.
How reliable is Devblog 301 LAN, and is it up?
At this moment, Devblog 301 LAN is offline; the last time it was seen was 33 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 24 September 2026.
On what Rust version does Devblog 301 LAN sit?
The server Devblog 301 LAN is on Rust network protocol 2602 and build 132924 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Devblog 301 LAN wipe, and how often?
There are too few wipes on record for Devblog 301 LAN to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 35 days 21 hours have passed since this world was made.
Player numbers
What position does Devblog 301 LAN hold in the rankings?
In the top 71% of all ranked servers, Devblog 301 LAN sits at #16,363 for player hours over the last seven days.
How many players does Devblog 301 LAN usually have?
It has been 33 days 16 hours since Devblog 301 LAN was last seen, and it is offline right now.
Tags and filters
What do Devblog 301 LAN's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2602 (Protocol): The game protocol is 2602, so your game must match that version to join; cs132924 (Build): The game build is 132924; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $reu1 (Region code): eu1 is the region code this server uses; ^p (PvE): Players do not fight one another here; the world is the danger are the tags Devblog 301 LAN publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Devblog 301 LAN?
Rust Server Score lists that include Devblog 301 LAN: Best community servers, graded and Rust PvE servers, graded. These filters bring it up 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.
Server rules
Which rules does Devblog 301 LAN enforce, and what are its settings?
Nothing in the name of Devblog 301 LAN states a gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map Devblog 301 LAN uses?
The game generates a procedural map for Devblog 301 LAN.
Getting in
What is the way to join Devblog 301 LAN?
To connect, start Rust, press F1, and type client.connect 94.139.255.199:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$reu1,v2602,^p,gmrust,cs132924,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2602
ProtocolThe game protocol is 2602, so your game must match that version to join.
cs132924
BuildThe game build is 132924.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$reu1
Region codeeu1 is the region code this server uses.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).