Rust Server TrendsSeismic network · station log
Recording Stations11,694 Players35,972 Active2,914 Wipes · 3 h94 48 h

Station XX-15394 · no signal

Solo Frontier TEST - acceptance

Offline 95.182.106.67:28115 checked 15d ago

teams off moddedcarbon
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,394
top 71%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15394 · 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 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
15k10k15k20k12 Oct14 Oct15 Oct17 Oct18 Oct20 Oct

Top 71% 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 · 154 on average
15/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
31/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
14/ 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

Server rules

Which map is running on Solo Frontier TEST - acceptance?

The map on Solo Frontier TEST - acceptance is procedural, produced 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. It gives no group limit in its listing. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Population

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

Solo Frontier TEST - acceptance is not responding at this moment and is offline, last seen 15 days 18 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 #15,394 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does Solo Frontier TEST - acceptance stay online?

As recorded now, Solo Frontier TEST - acceptance is not reachable, the last contact having been 15 days 18 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 12 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Solo Frontier TEST - acceptance run from?

A region is not published by Solo Frontier TEST - acceptance. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 95.182.106.67:28115.

What build of Rust does Solo Frontier TEST - acceptance use?

Solo Frontier TEST - acceptance is running Rust network protocol 2634 and build 166494 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

How often does Solo Frontier TEST - acceptance wipe, and on which days?

Too few wipes of Solo Frontier TEST - acceptance are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 27 days 8 hours.

Tags

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

The game's server browser reads the tags Solo Frontier TEST - acceptance publishes: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; ts0 (Group limit): Teams are disabled; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166494 (Build): The game build is 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running 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?

The Rust Server Trends lists that take in Solo Frontier TEST - acceptance are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y.

Connecting

How do you connect to Solo Frontier TEST - acceptance?

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

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players 20 slots are available.
ts0
Group limit Teams are disabled.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166494
Build The game build is 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 Plugins or settings alter the game, so it's listed 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.