Rust Data

rustdata.spaceservers201.10.76.6:28015.ipynb

Run all rust-data · live

‹ All servers

Offline 201.10.76.6:28015 checked 21d ago

Devblog 65 Legacy Server

Connect

srv = rust.server("201.10.76.6:28015")
print(srv.connect_command)

Right now

srv.summary()
players now 1/30 # 3% full
7-day average 0 # peak –
rank #13,767 # top 61%
last wipe 21d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k5 Oct7 Oct8 Oct10 Oct11 Oct13 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
201.10.76.6:28015
region
–
max players
30
group limit
not published
wipe schedule
–
last wipe
6 Oct 2026, 11:16 UTC
hostname
–
first seen
5 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 536 on average444/475
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average244/225
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 318 on average26/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 317 on average30/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 276 on average140/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average49/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Devblog 65 Legacy Server rank?

Over the last seven days Devblog 65 Legacy Server sits at #13,767 on player hours, in the top 61% of ranked servers.

How many players does Devblog 65 Legacy Server hold at once?

Offline now for Devblog 65 Legacy Server, with the last sample 21 days 19 hours ago.

Server data

Which Rust version is Devblog 65 Legacy Server on?

The build is Rust network protocol 2013 on Windows, run by Devblog 65 Legacy Server. Steam updates your game for you, but the protocol must match to join.

Is Devblog 65 Legacy Server up, and what does its uptime show?

Devblog 65 Legacy Server is offline at this refresh; the last response came 21 days 19 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 5 October 2026.

Which location does Devblog 65 Legacy Server run from?

For Devblog 65 Legacy Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 201.10.76.6:28015 is its address.

Rules, settings, map

Which settings and rules does Devblog 65 Legacy Server run?

The name Devblog 65 Legacy Server carries no gather rate. Group limits do not appear in its data. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. The server browser lists it under Community. The VAC field reads off.

Which map has Devblog 65 Legacy Server selected?

The game generates its map: procedural, on Devblog 65 Legacy Server.

Wipes and dates

When does Devblog 65 Legacy Server wipe, and how often?

A rhythm cannot be read from the wipes of Devblog 65 Legacy Server on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 21 days 21 hours ago, and that is the one in play.

Tags and filters

Which Rust Data filters and lists contain Devblog 65 Legacy Server?

These Rust Data lists include Devblog 65 Legacy Server: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all.

How should you read the server tags on Devblog 65 Legacy Server?

Read by the game's server browser, the tags Devblog 65 Legacy Server publishes are: mp30 (Max players): Slot count: 30; v2013 (Protocol): The server speaks protocol 2013, so match your game version; h5cf11350 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin; stok (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into Devblog 65 Legacy Server?

In Rust, F1 opens the console: type client.connect 201.10.76.6:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp30,v2013,h5cf11350,stok

Game

mp30
Max players Slot count: 30.
v2013
Protocol The server speaks protocol 2013, so match your game version.

Other

h5cf11350
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.
stok
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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.

Rust Data 46,789 players 11,635 servers online