Rust Data

rustdata.spaceservers95.46.137.9:28217.ipynb

Run all rust-data · live

‹ All servers

Offline 95.46.137.9:28215 checked 18d ago

Solo Frontier | Amber 3500 Review

Connect

srv = rust.server("95.46.137.9:28217")
print(srv.connect_command)

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 0 # peak –
rank #13,624 # top 62%
last wipe 18d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak1players, 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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 10 Oct, 14:19 UTC18d ago 1 NaN running 0

# Peak: the most players in the first 48 hours. 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.

display(srv.map, srv.info())

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
95.46.137.9:28215
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
10 Oct 2026, 14:19 UTC
hostname
–
first seen
10 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 516 on average453/475
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average364/375
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average43/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average31/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average52/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 243 on average151/200

Quick answers

From the figures on this page.

Population

How does Solo Frontier | Amber 3500 Review compare in the rankings?

Over the last seven days Solo Frontier | Amber 3500 Review sits at #13,624 on player hours, in the top 62% of ranked servers.

How many players does Solo Frontier | Amber 3500 Review hold at once?

Offline now for Solo Frontier | Amber 3500 Review, with the last sample 18 days 20 hours ago.

About the server

Which Rust version is Solo Frontier | Amber 3500 Review on?

The build is Rust network protocol 2634 and build 166494 on Windows, run by Solo Frontier | Amber 3500 Review. Steam updates your game for you, but the protocol must match to join.

Is Solo Frontier | Amber 3500 Review up, and what does its uptime show?

Solo Frontier | Amber 3500 Review is offline at this refresh; the last response came 18 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 10 October 2026.

Which location does Solo Frontier | Amber 3500 Review run from?

There is no region published for Solo Frontier | Amber 3500 Review. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 95.46.137.9:28215 is its address.

Rules, settings, map

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

You will not find a gather rate in the string Solo Frontier | Amber 3500 Review. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Wipe data

On what schedule does Solo Frontier | Amber 3500 Review wipe?

Too few wipes are on record for Solo Frontier | Amber 3500 Review to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 18 days 20 hours ago.

On Solo Frontier | Amber 3500 Review, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.

Tags, lists

Which lists on Rust Data hold Solo Frontier | Amber 3500 Review, and which filters?

On Rust Data, Solo Frontier | Amber 3500 Review appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Solo Frontier | Amber 3500 Review hold?

These tags are published by Solo Frontier | Amber 3500 Review and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join Solo Frontier | Amber 3500 Review?

In Rust, F1 opens the console: type client.connect 95.46.137.9:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp1
Max players The server lists 1 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166494
Build Recorded game build: 166494.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

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.

Rust Data 61,093 players 11,722 servers online