RUST METRICSFlight deck · live data
Data live Servers11,714 Players56,753 Populated3,283 Fresh wipes 3 h169 Scan5 min
‹ All servers187.170.251.198:28015
Offline Full Queue Fresh wipe Wipe due No query

Defcon_Server

Offline 187.170.251.198:28015 checked 24d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% 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#14,431top 64%
Last wipe25d 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
15k10k15k20k27 Sep30 Sep3 Oct6 Oct9 Oct12 Oct

Top 64% 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.

usual gap5.5 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 3 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 13:52 UTC25d ago 1 – running 0
Mon 28 Sep, 01:19 UTC31d ago 1 – 5.5 days 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

Wipe schedule

What happens on Defcon_Server when wipe day comes?

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

How often does Defcon_Server wipe, and when?

Its rhythm cannot be told from the wipes of Defcon_Server on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 25 days 20 hours ago the current world was made.

Tags

Which tags does Defcon_Server carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Defcon_Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Defcon_Server?

These Rust Metrics lists carry Defcon_Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Defcon_Server hold among Rust servers?

Player hours over seven days put Defcon_Server at #14,431, in the top 64% of all ranked servers.

How full does Defcon_Server get?

Status for Defcon_Server: offline. Last seen 24 days 8 hours ago.

Server details

What location is Defcon_Server hosted in?

No region tag on Defcon_Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 187.170.251.198:28015.

What Rust version is Defcon_Server on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by Defcon_Server. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Defcon_Server, and is it online now?

Reading: offline. Defcon_Server last answered 24 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 27 September 2026, recorded by Rust Metrics.

Map and rules

How is Defcon_Server configured, and what rules are in force?

No gather rate appears in the name: Defcon_Server. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. VAC is off. That is Valve's anti-cheat.

Which map is live on Defcon_Server?

The game generates a procedural map for Defcon_Server.

Connection

How can you get onto Defcon_Server?

Check: join. Open Rust, press F1, then enter client.connect 187.170.251.198:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2634,gmvanilla,cs166652,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp3
Max players The server holds 3 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.