RUST METRICSFlight deck · live data
Data live Servers11,639 Players47,599 Populated3,178 Fresh wipes 3 h100 Scan5 min
‹ All servers84.65.217.165:28015
Offline Full Queue Fresh wipe Wipe due No query

RustDev local test

Offline 84.65.217.165:28015 checked 10d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 1 /4

Players now

25% 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#12,972top 59%
Last wipe17d 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
15k10k15k20k10 Oct13 Oct16 Oct18 Oct21 Oct24 Oct

Top 59% 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 schedule

How often does RustDev local test wipe, and when?

The rhythm of RustDev local test'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 17 days 19 hours ago.

Lists and filters

How should you read the tags on RustDev local test?

These are the tags RustDev local test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RustDev local test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustDev local test: 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

What position does RustDev local test hold among Rust servers?

Player hours over seven days put RustDev local test at #12,972, in the top 59% of all ranked servers.

What player count does RustDev local test carry?

RustDev local test is not responding; status offline, last seen 10 days 17 hours ago.

Operator and location

Where does RustDev local test sit?

No region comes from RustDev local test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 84.65.217.165:28015.

What Rust version is RustDev local test on?

Rust network protocol 2634 and build 167398 on Windows is the build RustDev local test runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on RustDev local test, and is it online?

Check: connection. RustDev local test is offline at this moment. Last contact was 10 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on RustDev local test?

Check: gather rate. The name RustDev local test does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Anti-cheat reading: VAC off, Valve's system.

Which map is live on RustDev local test?

The game generates a procedural map for RustDev local test.

Connection

How can you get onto RustDev local test?

Press F1 in Rust and enter client.connect 84.65.217.165:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players The server holds 4 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^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.