Rust Server TrendsSeismic network · station log
Recording Stations11,608 Players34,356 Active2,818 Wipes · 3 h71 48 h

Station XX-13624 · no signal

Solo Frontier | Amber 3500 Review

Offline 95.46.137.9:28215 checked 18d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,624
top 62%
Last wipe
18d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13624 · 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 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
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

Top 62% 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
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
Sat 10 Oct, 14:19 UTC18d ago M0.0rising 1 – running 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 537 on average
196/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
182/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
16/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 281 on average
15/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
16/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 248 on average
90/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on Solo Frontier | Amber 3500 Review?

The name of Solo Frontier | Amber 3500 Review gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Solo Frontier | Amber 3500 Review right now?

No players are recorded on Solo Frontier | Amber 3500 Review at this moment; it is offline, and the last sighting was 18 days 15 hours ago.

How does Solo Frontier | Amber 3500 Review rank against other Rust servers?

On player hours for the past week, Solo Frontier | Amber 3500 Review sits at #13,624, which puts it inside the top 62% of every ranked server.

Server details

How reliably does Solo Frontier | Amber 3500 Review stay online?

As recorded now, Solo Frontier | Amber 3500 Review is not reachable, the last contact having been 18 days 15 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 10 October 2026.

Where in the world is Solo Frontier | Amber 3500 Review hosted?

No region is published by Solo Frontier | Amber 3500 Review. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 95.46.137.9:28215.

What build of Rust does Solo Frontier | Amber 3500 Review use?

On Windows, Solo Frontier | Amber 3500 Review runs Rust network protocol 2634 and build 166494. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Solo Frontier | Amber 3500 Review?

On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.

How often does Solo Frontier | Amber 3500 Review wipe, and on which days?

On record so far are too few of Solo Frontier | Amber 3500 Review's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 18 days 16 hours is how long the current world has been running.

Server tags

What do the server tags on Solo Frontier | Amber 3500 Review mean?

The game's server browser reads the tags Solo Frontier | Amber 3500 Review publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166494 (Build): It runs game build 166494; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code. 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 Solo Frontier | Amber 3500 Review appear?

These Rust Server Trends lists include Solo Frontier | Amber 3500 Review: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to Solo Frontier | Amber 3500 Review?

To join, enter client.connect 95.46.137.9:28215 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?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players The server has 1 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166494
Build It runs game build 166494.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

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.