RUST METRICSFlight deck · live data
Data live Servers11,789 Players78,653 Populated3,571 Fresh wipes 3 h243 Scan5 min
‹ All servers114.177.122.3:28215
Offline Full Queue Fresh wipe Wipe due No query

Daedalus Local Verification

Offline 114.177.122.3:28215 checked 31d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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#16,966top 71%
Last wipe33d agono schedule published
Next wipe–no wipe 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

How often does Daedalus Local Verification wipe, and when?

The rhythm of Daedalus Local Verification's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 33 days 13 hours ago.

Tags

How should you read the tags on Daedalus Local Verification?

These are the tags Daedalus Local Verification publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Daedalus Local Verification appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Daedalus Local Verification: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

Where does Daedalus Local Verification sit in the rankings?

Ranking for Daedalus Local Verification: #16,966 on seven-day player hours, top 71% of all ranked servers.

How full does Daedalus Local Verification get?

Status for Daedalus Local Verification: offline. Last seen 31 days 4 hours ago.

Operator and location

What location is Daedalus Local Verification hosted in?

Reading: location. Daedalus Local Verification gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 114.177.122.3:28215.

What Rust version is Daedalus Local Verification on?

Rust network protocol 2633 and build 165217 on Windows is the build Daedalus Local Verification runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Daedalus Local Verification, and is it online now?

Daedalus Local Verification reports offline. The last reading came 31 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 28 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Daedalus Local Verification?

No gather rate appears in the name: Daedalus Local Verification. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

What map is Daedalus Local Verification on?

The game generates a procedural map for Daedalus Local Verification.

Connection

What do you do to join Daedalus Local Verification?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players Slots: 2.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.