Devblog 301 LAN
Offline 94.139.255.199:28015 checked 22d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
Quick answers
Tags and search
Where does Devblog 301 LAN appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Devblog 301 LAN are: Rust community servers, going deep and Go deep on PvE servers. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
How should you read the tags on Devblog 301 LAN?
Devblog 301 LAN's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp20 (Max players): There are 20 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2602 (Protocol): This server runs game protocol 2602, so your game must match that version to join; cs132924 (Build): The build number is 132924; ptrak (Networking): The network layer is RakNet, Rust's default; $reu1 (Region code): eu1 is this server's region code; ^p (PvE): Other players aren't a threat; the world is. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of Devblog 301 LAN?
There is no region from Devblog 301 LAN, but the region code reads eu1. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 94.139.255.199:28015.
How reliable is Devblog 301 LAN?
Devblog 301 LAN is down at the moment; it was last up 22 days 13 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 24 September 2026 is when Rust Going Deep first saw it.
What Rust version is Devblog 301 LAN on?
The version on Devblog 301 LAN is Rust network protocol 2602 and build 132924, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
When does Devblog 301 LAN wipe?
The wipes recorded for Devblog 301 LAN are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 24 days 18 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to Devblog 301 LAN?
Its name does not state a gather rate for Devblog 301 LAN. 8 players is the group cap, the game's default. It runs pve, no fighting other players. It sits under Community in the server browser: a community server. VAC, Valve's anti-cheat, is disabled.
What's the map on Devblog 301 LAN?
A procedural map, generated by the game, is in play on Devblog 301 LAN.
Population
What's the population like on Devblog 301 LAN?
Devblog 301 LAN was last seen 22 days 13 hours ago and is offline as you read this.
What's Devblog 301 LAN's rank among Rust servers?
For player hours in the last seven days, Devblog 301 LAN ranks #16,363, within the top 71% of ranked servers.
Join info
What's the way to join Devblog 301 LAN?
Open Rust and press F1, then type client.connect 94.139.255.199:28015. Alternatively, click Launch Rust on this page to join via Steam.