Devblog 260 Local
Offline 176.52.78.213:28015 checked 31d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What is the wipe schedule on Devblog 260 Local?
The record of Devblog 260 Local's wipes is not yet long enough to show a rhythm. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 31 days 20 hours ago the server made the world it is on now.
Player counts
How busy is Devblog 260 Local?
Devblog 260 Local went quiet 31 days 20 hours ago and is offline right now.
How does Devblog 260 Local rank against other Rust servers?
Player hours over seven days put Devblog 260 Local at #16,730, in the top 71% of ranked servers.
Settings and rules
Which map does Devblog 260 Local run?
The game generates the procedural map on Devblog 260 Local.
What are the rules and settings on Devblog 260 Local?
The name Devblog 260 Local does not specify a gather rate. Groups can contain up to 8 players, the default in the game. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does Devblog 260 Local run?
Rust network protocol 2633 and build 165217 on Windows is what Devblog 260 Local runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Devblog 260 Local online, and how reliable is it?
Last seen 31 days 20 hours ago, Devblog 260 Local is offline right now. 0 of 168 hours up over the last 7 full days, which is 0%. The first record of it on Rust Heatmap is 26 September 2026.
Where is Devblog 260 Local located?
Nothing about a region comes from Devblog 260 Local. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 176.52.78.213:28015.
Lists and filters
Which Rust Heatmap lists and filters include Devblog 260 Local?
Modded Rust servers, by live population are the Rust Heatmap lists that Devblog 260 Local fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on Devblog 260 Local mean?
The game's server browser reads the tags Devblog 260 Local publishes: gmrust (Game mode): Survival in the standard Rust form; mp50 (Max players): Slot count: 50; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): To join, run the same version: game protocol 2633; cs165217 (Build): This build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join Devblog 260 Local?
Press F1 in Rust to open the console, then enter client.connect 176.52.78.213:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.