Working its way up from the back of the class: #16,590 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 759 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
Rust Devblog Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 139.100.245.66:28015.
How dependable is Rust Devblog Server, and is it online at the moment?
You cannot join now: Rust Devblog Server is offline, last seen 33 days 4 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 25 September 2026.
On what Rust version does Rust Devblog Server sit?
You will find Rust Devblog Server on Rust network protocol 2362, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Rust Devblog Server wipe its map?
Rust Devblog Server has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 36 days 14 hours.
Player count
Where does Rust Devblog Server place in the wider field of Rust servers?
In the top 71% of all ranked servers, Rust Devblog Server sits at #16,590 for player hours over the last seven days.
Is Rust Devblog Server a busy server?
It has been 33 days 4 hours since Rust Devblog Server was last seen, and it is offline right now.
Tags
What do Rust Devblog Server's tags stand for?
The game's browser takes its cue from the tags Rust Devblog Server has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; v2362 (Protocol): To get in, your game needs to be on the same version: the protocol is 2362; ptrak (Networking): This is RakNet: the network layer Rust normally uses; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon; hil2cpp (Custom tag): The owner or a plugin created this tag, so it is not standard Rust; stok (Custom tag): The owner or a plugin created this tag, so it is not standard Rust. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Rust Devblog Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust Devblog Server among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y.
Map and rules
What settings and rules apply on Rust Devblog Server?
The name of Rust Devblog Server gives no gather rate. No group limit is published. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. The server does not run VAC, Valve's anti-cheat.
Rust Devblog Server runs which map?
A procedural map, generated by the game, is what Rust Devblog Server runs.
Getting in
How do you get onto Rust Devblog Server?
To connect, start Rust, press F1, and type client.connect 139.100.245.66:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,v2362,hil2cpp,stok,gmrust,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
v2362
ProtocolTo get in, your game needs to be on the same version: the protocol is 2362.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
Other
hil2cpp
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
stok
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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).