Station XX-15957 · no signal
SOLO FRONTIER | BR OUTPOST 3500 | TEST
Offline 95.182.105.168:28115 checked 23d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,957
- top 70%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 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 70% 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.
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Wed 28 Oct, 11:27 UTC24d ago | M0.0▲rising | 1 | – | – | 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 pageMap and rules
Which settings and rules apply on SOLO FRONTIER | BR OUTPOST 3500 | TEST?
The name of SOLO FRONTIER | BR OUTPOST 3500 | TEST gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on SOLO FRONTIER | BR OUTPOST 3500 | TEST right now?
A reading taken now finds SOLO FRONTIER | BR OUTPOST 3500 | TEST offline; the most recent activity was 23 days 22 hours ago.
How does SOLO FRONTIER | BR OUTPOST 3500 | TEST rank against other Rust servers?
The last seven days of player hours place SOLO FRONTIER | BR OUTPOST 3500 | TEST at #15,957, in the top 70% of all ranked servers.
Server details
How reliably does SOLO FRONTIER | BR OUTPOST 3500 | TEST stay online?
SOLO FRONTIER | BR OUTPOST 3500 | TEST is down at the moment; the last recorded contact was 23 days 22 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 28 October 2026 is when Rust Server Trends first recorded it.
Where in the world is SOLO FRONTIER | BR OUTPOST 3500 | TEST hosted?
The name of SOLO FRONTIER | BR OUTPOST 3500 | TEST points to South America, even though it publishes no region tag. 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.105.168:28115.
What build of Rust does SOLO FRONTIER | BR OUTPOST 3500 | TEST use?
On Windows, SOLO FRONTIER | BR OUTPOST 3500 | TEST runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on SOLO FRONTIER | BR OUTPOST 3500 | TEST?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does SOLO FRONTIER | BR OUTPOST 3500 | TEST wipe, and on which days?
Too few wipes of SOLO FRONTIER | BR OUTPOST 3500 | TEST are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. It has run its current world for 24 days.
Server tags
What do the server tags on SOLO FRONTIER | BR OUTPOST 3500 | TEST mean?
These are the tags SOLO FRONTIER | BR OUTPOST 3500 | TEST publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): The server has 5 slots; 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): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server. 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 | BR OUTPOST 3500 | TEST appear?
These Rust Server Trends lists include SOLO FRONTIER | BR OUTPOST 3500 | TEST: Rust community servers without the side modes. On the server list, the filters it matches are: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
What steps get you onto SOLO FRONTIER | BR OUTPOST 3500 | TEST?
To join, enter client.connect 95.182.105.168: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.
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.