Rust Server TrendsSeismic network · station log
Recording Stations11,696 Players36,352 Active2,907 Wipes · 3 h94 48 h

Station XX-7973 · no signal

FRONTIER

Offline 91.179.64.204:28015 checked 3h ago

moddedoxide
Connect
Players now
1/ 10
10% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 1
Rank
#7,973
top 36%
Last wipe
16h ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-7973 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 10 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Wed 17:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75110:0012:0015:0017:0021:0023:00Wiped Wed 28 Oct, 10:32 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
025507510010:0012:0015:0017:0021:0023:00Wiped Wed 28 Oct, 10:32 UTCWIPE

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, measured since 28 Oct. 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
15k10k15k20k20 Sep22 Sep23 Sep25 Sep26 Sep29 Oct

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

usual gap
39.1 daysbetween real wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 28 Oct, 10:32 UTC16h ago – – – – running 0
Sat 19 Sep, 08:52 UTC39d ago M0.0steady 1 – 39.1 days 1

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
ShockRust | Blue | NoLimit no group limit · 154 on average
3/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
32/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
12/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
5/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
1/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on FRONTIER?

The procedural map on FRONTIER is size 5,000 with seed 944313, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on FRONTIER?

The name of FRONTIER gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on FRONTIER?

A reading taken now finds FRONTIER offline; the most recent activity was 3 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1. Averaged over the last 48 hours, the busiest hour was 11:00 UTC at 1 players.

How does FRONTIER rank against other Rust servers?

Over the last seven days, FRONTIER recorded enough player hours to reach #7,973 worldwide, placing it in the top 36% of all ranked servers.

Server facts

How reliably does FRONTIER stay online?

As recorded now, FRONTIER is not reachable, the last contact having been 3 hours ago. Going by the uptime figure it reports, it restarted about 12 minutes ago. 13 of 168 hours in the last 7 full days were up time, 8% of the total. On 16 September 2026 it was recorded for the first time by Rust Server Trends.

Does FRONTIER hold a steady tick rate?

Its average server fps over the last 48 hours was 68, and it never dropped below 48. Buildings, deployables and all the rest of the world's entities brought it to a high of 317,931. It reached a ceiling of 3,922 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is FRONTIER hosted?

Nothing about a region comes from FRONTIER. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 91.179.64.204:28015 is the address it uses.

Which Rust version is FRONTIER running?

On Windows, FRONTIER runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on FRONTIER?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does FRONTIER wipe, and on which days?

Too few wipes of FRONTIER are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 16 hours is how long the current world has been running.

Tags

What do the server tags on FRONTIER mean?

The game's server browser reads the tags FRONTIER publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does FRONTIER appear?

The Rust Server Trends lists that take in FRONTIER are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

How to join

What steps get you onto FRONTIER?

Enter client.connect 91.179.64.204:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.