Devblog 260 Local

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 32d ago · 176.52.78.213:28015

Abstract

We describe the public Rust server Devblog 260 Local, reached at 176.52.78.213:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #16,730 of all servers, the top 71%. It last wiped 32d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/50	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#16,730	top 71%
Last wipe	32d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: 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.

4Rank

The server stands in the top 71% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

Address	`176.52.78.213:28015`
Region	–
Max players	50
Group limit	8, the default
Wipe schedule	–
Last wipe	26 Sep 2026, 13:42 UTC
Hostname	–
First seen	26 Sep 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and predicted wipe schedule [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 157 on average	205/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	121/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average	183/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average	126/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 87 on average	19/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Devblog 260 Local?

No region is published by Devblog 260 Local. Rust Statistics does not look up the machine's location; it shows where the server says it is. 176.52.78.213:28015 is its address.

A.2What is the online status and reliability of Devblog 260 Local?

Devblog 260 Local is currently offline, with the last sighting 32 days 4 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first observed on 26 September 2026 by Rust Statistics.

A.3What version of Rust is run on Devblog 260 Local?

Rust network protocol 2633 and build 165217 is the version that Devblog 260 Local runs, on Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4When are wipes carried out on Devblog 260 Local?

The record of Devblog 260 Local's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 32 days 4 hours.

Player count

A.5How does Devblog 260 Local compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Devblog 260 Local at #16,730, within the top 71% of ranked servers.

A.6At what level does Devblog 260 Local operate in terms of players?

At this moment Devblog 260 Local is offline, having last been seen 32 days 4 hours ago.

Tags and filters

A.7What is the meaning of the tags on Devblog 260 Local?

gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): The slot count is 50; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs165217 (Build): The game build is 165217; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Devblog 260 Local publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can Devblog 260 Local be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Devblog 260 Local fits. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.9What are the settings and rules that govern Devblog 260 Local?

Its name carries no gather rate for Devblog 260 Local. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is active: that is Valve's anti-cheat.

A.10On which map does Devblog 260 Local take place?

A procedural map, generated by the game, is what Devblog 260 Local runs.

Connection

A.11What is the process for joining Devblog 260 Local?

Press F1 inside Rust to open the console and enter client.connect 176.52.78.213:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp50`	Max players. The slot count is 50.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2633`	Protocol. The game protocol is 2633; your client must match it to join.
`cs165217`	Build. The game build is 165217.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. No region code is set.
Mods and access
`^o`	Oxide. Plugins are handled by Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify the game.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.