Devblog 260 Local
Offline 176.52.78.213:28015 checked 32d ago
Vital stats
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include Devblog 260 Local?
These are the Rust Pop Watch lists that include Devblog 260 Local: Modded Rust servers, live. These filters bring it up on the server 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 picks up these tags from Devblog 260 Local: gmrust (Game mode): Plain vanilla Rust survival, nothing bolted on; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the default limit of 8 players per team; v2633 (Protocol): You need the same game version to get in: protocol 2633; cs165217 (Build): It's on game build 165217; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): Region code left blank; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You'll find players now, queue length and world creation time in the tags, printed at the top of this page.
Population
How does Devblog 260 Local rank against other Rust servers?
The last seven days of player hours place Devblog 260 Local at #16,730, in the top 71% of all ranked servers.
How many players are on Devblog 260 Local right now?
Devblog 260 Local went quiet 32 days 8 hours ago and is offline at the moment.
About the server
Is Devblog 260 Local online, and how reliable is it?
The server Devblog 260 Local is not online now; 32 days 8 hours have passed since it was last seen. It was up 0% of the time over the last 7 full days, 0 of 168 hours in total. It came to Rust Pop Watch's attention on 26 September 2026.
Where is Devblog 260 Local located?
No region is published by Devblog 260 Local. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. Connect at 176.52.78.213:28015.
Which Rust version is Devblog 260 Local on?
On Windows, Devblog 260 Local runs Rust network protocol 2633 and build 165217. Steam updates your game so it matches the protocol needed to join.
The wipe schedule
What is the wipe schedule on Devblog 260 Local?
Devblog 260 Local's rhythm stays hidden while so few of its wipes are on record. On Thursday 5 November at 19:00 UTC the force wipe arrives, and every Rust server wipes with it at monthly intervals. The world it is running now dates from 32 days 8 hours.
Rules and settings
Which map does Devblog 260 Local run?
Devblog 260 Local uses a procedural map, which the game generates.
What are the rules and settings on Devblog 260 Local?
Nothing in the name tells you the gather rate on Devblog 260 Local. Eight players per group: that is the game's default. It runs survival, gather, build and raid, as standard. Players can raid and fight one another. Plugins or settings alter the game, and the browser lists it as Modded. Oxide plugins are running on it. The VAC anti-cheat from Valve is on.
Join up
How do I join Devblog 260 Local?
The console method: start Rust, press F1, and type client.connect 176.52.78.213:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.