Devblog 260 Local
Offline 176.52.78.213:28015 checked 21d ago
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
daily · 1 is bestTop 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
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
the same kind of game, then region, group limit, rate and wipes
- 997/ 100
- 201/ 400
- 200/ 245
- 123/ 100
- 463/ 1000
- 33/ 700
Quick answers
Tags and listings
Where does Devblog 260 Local appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Devblog 260 Local are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Devblog 260 Local?
gmrust (Game mode): This is the standard Rust survival experience; mp50 (Max players): The slot count is 50; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Devblog 260 Local puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Where can you find Devblog 260 Local?
No region comes from Devblog 260 Local. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 176.52.78.213:28015.
What's the uptime like for Devblog 260 Local?
The server Devblog 260 Local is not reachable at the moment; the last sighting was 21 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 26 September 2026.
What is the Rust version for Devblog 260 Local?
The version on Devblog 260 Local is Rust network protocol 2633 and build 165217, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does Devblog 260 Local follow for wipes?
Devblog 260 Local's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 21 days 7 hours.
Map and rules
What settings are in place on Devblog 260 Local?
Its name does not state a gather rate for Devblog 260 Local. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Which map is active on Devblog 260 Local?
A procedural map, generated by the game, is in play on Devblog 260 Local.
Player stats
How many players are on Devblog 260 Local?
The last sighting of Devblog 260 Local was 21 days 6 hours ago; it is offline right now.
Where does Devblog 260 Local sit in the rankings?
For player hours in the last seven days, Devblog 260 Local ranks #16,730, within the top 71% of ranked servers.
Getting in
What's the way to join Devblog 260 Local?
To join, open Rust, hit F1, and enter client.connect 176.52.78.213:28015. Or click Launch Rust on this page to open the game through Steam and connect.