Working its way up from the back of the class: #13,146 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
34/ 100
F
Lost ground: down 4,290 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeakWipe
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 59% 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
Which region is Devblog 65 Legacy Server based in?
No region is published for Devblog 65 Legacy Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 201.10.76.60:28015.
How dependable is Devblog 65 Legacy Server, and is it online at the moment?
The server is down: Devblog 65 Legacy Server is offline now, with the last sighting 21 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 5 October 2026.
Which Rust version is Devblog 65 Legacy Server running?
You will find Devblog 65 Legacy Server on Rust network protocol 2013, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Devblog 65 Legacy Server wipe its map?
Devblog 65 Legacy 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. 21 days 21 hours have passed since this world was made.
Population
Where does Devblog 65 Legacy Server place in the wider field of Rust servers?
In the top 59% of all ranked servers, Devblog 65 Legacy Server sits at #13,146 for player hours over the last seven days.
How many players does Devblog 65 Legacy Server usually have?
The last sighting of Devblog 65 Legacy Server was 21 days 20 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on Devblog 65 Legacy Server?
You'll see Devblog 65 Legacy Server tagged with mp30 (Max players): Its slot count is 30; v2013 (Protocol): Join only if your game runs protocol 2013; h241a841b (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 in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Devblog 65 Legacy Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Devblog 65 Legacy Server: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all.
Rules and settings
What settings and rules apply on Devblog 65 Legacy Server?
You will find no gather rate in the name of Devblog 65 Legacy Server. No group limit is published. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Devblog 65 Legacy Server uses?
Devblog 65 Legacy Server runs a procedural map, which the game generates.
Connecting
What is the way to join Devblog 65 Legacy Server?
To connect, start Rust, press F1, and type client.connect 201.10.76.60:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,v2013,h241a841b,stok
Game
mp30
Max playersIts slot count is 30.
v2013
ProtocolJoin only if your game runs protocol 2013.
Other
h241a841b
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. Even marks across the subjects, from F to F.