Rust Server TrendsSeismic network · station log
Recording Stations11,535 Players86,112 Active4,004 Wipes · 3 h131 48 h

Station XX-16685 · no signal

Frontier_Map_Validation

Offline 79.139.216.13:28025 checked 22d ago

moddedcarbon
Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,685
top 70%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16685 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 1 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Oct31 Oct2 Nov3 Nov5 Nov6 Nov

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

Expected events

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.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –
Fri 30 Oct, 07:20 UTC22d ago M0.0steady 0 – – – 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
133/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
298/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
187/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
119/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
11/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on Frontier_Map_Validation?

The name of Frontier_Map_Validation gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on Frontier_Map_Validation right now?

A reading taken now finds Frontier_Map_Validation offline; the most recent activity was 22 days 5 hours ago.

How does Frontier_Map_Validation rank against other Rust servers?

Over the last seven days, Frontier_Map_Validation recorded enough player hours to reach #16,685 worldwide, placing it in the top 70% of all ranked servers.

Server facts

How reliably does Frontier_Map_Validation stay online?

Frontier_Map_Validation is down at the moment; the last recorded contact was 22 days 5 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 30 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Frontier_Map_Validation hosted?

A region is not published by Frontier_Map_Validation. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 79.139.216.13:28025.

What build of Rust does Frontier_Map_Validation use?

Frontier_Map_Validation is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on Frontier_Map_Validation?

The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does Frontier_Map_Validation wipe, and on which days?

The rhythm of Frontier_Map_Validation cannot yet be told: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 22 days 5 hours.

Lists and tags

What do the server tags on Frontier_Map_Validation mean?

These are the tags Frontier_Map_Validation publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Frontier_Map_Validation appear?

These Rust Server Trends lists include Frontier_Map_Validation: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How to join

What steps get you onto Frontier_Map_Validation?

To join, enter client.connect 79.139.216.13:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.