RUST METRICSFlight deck · live data
Data live Servers11,695 Players53,611 Populated3,212 Fresh wipes 3 h134 Scan5 min
‹ All servers69.250.66.224:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Dev Server

Offline 69.250.66.224:28015 checked 12d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,106top 70%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

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

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k21 Sep27 Sep4 Oct10 Oct17 Oct23 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 18:12 UTC26d ago 1 – running 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Local Dev Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Local Dev Server wipe, and when?

Its rhythm cannot be told from the wipes of Local Dev Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 26 days 15 hours ago the current world was made.

Tags

How should you read the tags on Local Dev Server?

These are the tags Local Dev Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166655 (Build): Build 166655; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Local Dev Server?

Rust Metrics lists featuring Local Dev Server: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Local Dev Server hold among Rust servers?

Player hours over seven days put Local Dev Server at #15,106, in the top 70% of all ranked servers.

What player count does Local Dev Server carry?

Status for Local Dev Server: offline. Last seen 12 days 15 hours ago.

Server

Which location does Local Dev Server run from?

Reading: location. Local Dev Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 69.250.66.224:28015.

What Rust version is Local Dev Server on?

Reading: Local Dev Server, Rust network protocol 2634 and build 166655, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Local Dev Server up, and how often does it stay up?

Check: connection. Local Dev Server is offline at this moment. Last contact was 12 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 21 September 2026.

Map and rules

How is Local Dev Server configured, and what rules are in force?

Reading the name gives no gather rate for Local Dev Server. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

What map is Local Dev Server on?

Procedural map on Local Dev Server, made by the game's generator.

How to join

What do you do to join Local Dev Server?

To join: start Rust, press F1 and type client.connect 69.250.66.224:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166655,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166655
Build Build 166655.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.