Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h58 48 h

Station XX-12999 · no signal

Solo Frontier TEST - acceptance

Offline 95.182.104.45:28115 checked 14d ago

teams off moddedcarbon
Connect
Players now
1/ 20
5% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,999
top 60%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-12999 · 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
1of 20 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
15k10k15k20k13 Oct15 Oct16 Oct18 Oct19 Oct21 Oct

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 157 on average
205/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Solo Frontier TEST - acceptance?

A procedural map runs on Solo Frontier TEST - acceptance, generated by the game.

Which settings and rules apply on Solo Frontier TEST - acceptance?

You will find no gather rate in the name of Solo Frontier TEST - acceptance. No group limit is published. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on Solo Frontier TEST - acceptance right now?

A reading taken now finds Solo Frontier TEST - acceptance offline; the most recent activity was 14 days 10 hours ago.

How does Solo Frontier TEST - acceptance rank against other Rust servers?

Over the last seven days, Solo Frontier TEST - acceptance recorded enough player hours to reach #12,999 worldwide, placing it in the top 60% of all ranked servers.

Server facts

How reliably does Solo Frontier TEST - acceptance stay online?

No contact with Solo Frontier TEST - acceptance right now, and the last recorded contact was 14 days 10 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.

Where in the world is Solo Frontier TEST - acceptance hosted?

No region is published by Solo Frontier TEST - acceptance. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 95.182.104.45:28115.

Which Rust version is Solo Frontier TEST - acceptance running?

On Windows, Solo Frontier TEST - acceptance runs Rust network protocol 2634 and build 166494. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

On what timetable does Solo Frontier TEST - acceptance run its wipes?

Too few wipes of Solo Frontier TEST - acceptance are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days.

Server tags

What do the server tags on Solo Frontier TEST - acceptance mean?

These are the tags Solo Frontier TEST - acceptance publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): Slots: 20; ts0 (Group limit): You can't form teams here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Solo Frontier TEST - acceptance appear?

You will find Solo Frontier TEST - acceptance on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y.

Connecting

How do you connect to Solo Frontier TEST - acceptance?

Enter client.connect 95.182.104.45:28115 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 mp20,ptrak,$r?,v2634,gmrust,cs166494,ts0,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players Slots: 20.
ts0
Group limit You can't form teams here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166494
Build Game build: 166494.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs 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.