Station XX-13751 · no signal
Local Dev Server
Offline 46.138.18.129:28015 checked 14d ago
- Players now
- 1/ 5
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,751
- top 64%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 5 slots
- Motion · 24 h
- M –not enough readings
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 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 2.1 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 19:49 UTC24d ago | M0.0■steady | 1 | – | – | running | 1 |
| Thu 1 Oct, 18:20 UTC FW27d ago | M0.0■steady | 1 | held half | 2.1 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Local Dev Server?
The map on Local Dev Server is procedural, produced by the game.
Which settings and rules apply on Local Dev Server?
The name of Local Dev Server gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is off: VAC, from Valve.
Live population
How many players are recorded on Local Dev Server right now?
No players are recorded on Local Dev Server at this moment; it is offline, and the last sighting was 14 days 20 hours ago.
How does Local Dev Server rank against other Rust servers?
Over the last seven days, Local Dev Server recorded enough player hours to reach #13,751 worldwide, placing it in the top 64% of all ranked servers.
Operator and location
How reliably does Local Dev Server stay online?
As recorded now, Local Dev Server is not reachable, the last contact having been 14 days 20 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 17 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Local Dev Server hosted?
A region is not published by Local Dev Server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 46.138.18.129:28015 is the address it uses.
What build of Rust does Local Dev Server use?
Rust network protocol 2634 and build 167781 on Windows is what Local Dev Server runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Local Dev Server?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
How often does Local Dev Server wipe, and on which days?
Too few wipes of Local Dev Server are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 24 days 23 hours is how long the current world has been running.
Lists and tags
What do the server tags on Local Dev Server mean?
The game's server browser reads the tags Local Dev Server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): Slots: 5; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Local Dev Server appear?
You will find Local Dev Server on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to Local Dev Server?
Enter client.connect 46.138.18.129:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.