RUST METRICSFlight deck · live data
Data live Servers11,620 Players35,915 Populated2,914 Fresh wipes 3 h77 Scan5 min
‹ All servers68.3.12.103:28015
Online Full Queue Fresh wipe Wipe due No query

Rust map validation

Online 68.3.12.103:28015 checked 9m ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,419top 69%
Last wipe14h agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeakWipe
0123416:0019:0021:0000:0002:0005:00Wiped Tue 27 Oct, 16:14 UTCWIPE

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 Oct28 Oct

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 16:18 UTC14h ago – – 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

Wipe timing

When does Rust map validation wipe?

To tell the rhythm of Rust map validation, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 14 hours ago.

Tag meanings

How should you read the tags on Rust map validation?

These are the tags Rust map validation publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Your game must run protocol 2632 to get in; cs161125 (Build): Build 161125; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Rust map validation appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust map validation: 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; Last wipe: In the last 24 hours.

Player count

Where does Rust map validation sit in the rankings?

Ranking for Rust map validation: #15,419 on seven-day player hours, top 69% of all ranked servers.

How full does Rust map validation get?

0 of 1 slots are filled on Rust map validation right now. A seven-day average of 0 players is the reading.

Server details

Where does Rust map validation sit?

Reading: location. Rust map validation gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 68.3.12.103:28015.

What Rust version is Rust map validation on?

Version check: Rust network protocol 2632 and build 161125 on Windows, run by Rust map validation. To get in, your game needs the same protocol; Steam applies the update.

Is Rust map validation up, and how often does it stay up?

Reading: online. Rust map validation answers right now. Reading: first seen 27 October 2026, recorded by Rust Metrics.

Settings and map

How is Rust map validation configured, and what rules are in force?

Reading the name gives no gather rate for Rust map validation. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Join

What do you do to join Rust map validation?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2632,gmrust,cs161125,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2632
Protocol Your game must run protocol 2632 to get in.
cs161125
Build Build 161125.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.