RUST METRICSFlight deck · live data
Data live Servers11,597 Players34,396 Populated2,832 Fresh wipes 3 h63 Scan5 min
‹ All servers62.45.100.181:28015
Offline Full Queue Fresh wipe Wipe due No query

Living World checkpoint

Offline 62.45.100.181:28015 checked 23d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

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,962top 71%
Last wipe23d 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
15k10k15k20k4 Oct5 Oct7 Oct8 Oct10 Oct11 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

What wipe timing does Living World checkpoint follow?

Its rhythm cannot be told from the wipes of Living World checkpoint 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. The world in play was created 23 days 13 hours ago.

Tags

How should you read the tags on Living World checkpoint?

These are the tags Living World checkpoint publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Living World checkpoint appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Living World checkpoint: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Player count

Where does Living World checkpoint sit in the rankings?

Player hours over seven days put Living World checkpoint at #15,962, in the top 71% of all ranked servers.

What is the population on Living World checkpoint?

Living World checkpoint is not responding; status offline, last seen 23 days 7 hours ago.

Operator and location

Which location does Living World checkpoint run from?

Reading: location. Living World checkpoint gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 62.45.100.181:28015.

What Rust version is Living World checkpoint on?

Reading: Living World checkpoint, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Living World checkpoint up, and how often does it stay up?

Living World checkpoint reports offline. The last reading came 23 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

What settings and rules apply on Living World checkpoint?

Check: gather rate. The name Living World checkpoint does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

What map is Living World checkpoint on?

The game generates a procedural map for Living World checkpoint.

Connection

How can you get onto Living World checkpoint?

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

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players The server holds 20 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Plugin framework in use: 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.