Working its way up from the back of the class: #16,957 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
47/ 100
D
Slipped a little: down 1,070 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.
No daily history yet.
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
You won't see a region from Devblog 301 LAN, whose region code is us4. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 185.16.213.70:28015 is the address to use.
How reliable is Devblog 301 LAN, and is it up?
You cannot join now: Devblog 301 LAN is offline, last seen 31 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 27 September 2026.
Which Rust version is Devblog 301 LAN running?
Rust network protocol 2602 and build 132924 on Windows is what Devblog 301 LAN runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Devblog 301 LAN wipe its map?
Devblog 301 LAN has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 36 days 10 hours have passed since this world was made.
Player numbers
Where does Devblog 301 LAN place in the wider field of Rust servers?
In the top 71% of all ranked servers, Devblog 301 LAN sits at #16,957 for player hours over the last seven days.
How many players does Devblog 301 LAN usually have?
It has been 31 days 21 hours since Devblog 301 LAN was last seen, and it is offline right now.
Lists and filters
What do Devblog 301 LAN's tags stand for?
You'll see Devblog 301 LAN tagged with gmrust (Game mode): Survival in the standard Rust style; 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): To get in, your game needs to be on the same version: the protocol is 2602; cs132924 (Build): The game build is 132924; ptrak (Networking): RakNet handles it, the game's default network layer; $rus4 (Region code): Region code: us4; ^p (PvE): Players do not fight one another here; the world is the danger in the browser, which picks them up from the server. 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 lists and filters on Rust Server Score show Devblog 301 LAN?
These Rust Server Score lists count Devblog 301 LAN among them: Best community servers, graded and Rust PvE servers, graded. It shows under the following 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 and settings
How is Devblog 301 LAN set up, and what rules does it keep?
You will find no gather rate in the name of Devblog 301 LAN. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is not enabled.
Devblog 301 LAN runs which map?
The game generates a procedural map for Devblog 301 LAN.
Connecting
What is the way to join Devblog 301 LAN?
Enter client.connect 185.16.213.70:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp20,ptrak,$rus4,v2602,^p,gmrust,cs132924,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2602
ProtocolTo get in, your game needs to be on the same version: the protocol is 2602.
cs132924
BuildThe game build is 132924.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rus4
Region codeRegion code: us4.
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).