Station XX-16966 · no signal
Solo Frontier | SOLO | ╨в╨Х╨б╨в
Offline 95.182.106.96:28015 checked 30d ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,966
- top 71%
- Last wipe
- 35d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.3 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 28 Sep, 17:04 UTC30d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 28 Sep, 10:31 UTC30d ago | M0.0■steady | 0 | – | 0.3 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Solo Frontier | SOLO | ╨в╨Х╨б╨в?
A procedural map runs on Solo Frontier | SOLO | ╨в╨Х╨б╨в, generated by the game.
Which settings and rules apply on Solo Frontier | SOLO | ╨в╨Х╨б╨в?
You will find no gather rate in the name of Solo Frontier | SOLO | ╨в╨Х╨б╨в. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. 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
What is the current population on Solo Frontier | SOLO | ╨в╨Х╨б╨в?
Solo Frontier | SOLO | ╨в╨Х╨б╨в is not responding at this moment and is offline, last seen 30 days 2 hours ago.
How does Solo Frontier | SOLO | ╨в╨Х╨б╨в rank against other Rust servers?
On player hours for the past week, Solo Frontier | SOLO | ╨в╨Х╨б╨в sits at #16,966, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does Solo Frontier | SOLO | ╨в╨Х╨б╨в stay online?
No contact with Solo Frontier | SOLO | ╨в╨Х╨б╨в right now, and the last recorded contact was 30 days 2 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 28 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Solo Frontier | SOLO | ╨в╨Х╨б╨в run from?
No region tag comes from Solo Frontier | SOLO | ╨в╨Х╨б╨в, though the name points to Europe. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 95.182.106.96:28015 is the address it uses.
What build of Rust does Solo Frontier | SOLO | ╨в╨Х╨б╨в use?
Rust network protocol 2633 and build 165217 on Windows is what Solo Frontier | SOLO | ╨в╨Х╨б╨в runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Solo Frontier | SOLO | ╨в╨Х╨б╨в?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Solo Frontier | SOLO | ╨в╨Х╨б╨в run its wipes?
On record so far are too few of Solo Frontier | SOLO | ╨в╨Х╨б╨в's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 35 days 15 hours.
Server tags
What do the server tags on Solo Frontier | SOLO | ╨в╨Х╨б╨в mean?
These are the tags Solo Frontier | SOLO | ╨в╨Х╨б╨в publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The server has 20 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): It runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 | SOLO | ╨в╨Х╨б╨в appear?
The Rust Server Trends lists that take in Solo Frontier | SOLO | ╨в╨Х╨б╨в are: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
What steps get you onto Solo Frontier | SOLO | ╨в╨Х╨б╨в?
You can connect by pressing F1 in Rust and typing client.connect 95.182.106.96:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
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.