Rust Data

rustdata.spaceservers5.39.17.13:23093.ipynb

Run all rust-data · live

‹ All servers

Offline 5.39.17.13:23092 checked 26d ago

Asid's Serv - SOLO ONLY

Connect

srv = rust.server("5.39.17.13:23093")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,985 # top 70%
last wipe 38d ago # no schedule published
next wipe – # no rhythm it keeps

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, measured since 17 Sep. 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
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.4 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Mon 21 SepSat 19 SepFri 18 Sep
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 Mon 21 Sep, 17:23 UTC38d ago 1 NaN running 0
1 Sat 19 Sep, 20:54 UTC40d ago 1 NaN 1.9 days 0
2 Fri 18 Sep, 11:44 UTC41d ago 1+1 queue NaN 1.4 days 0
3 Thu 17 Sep, 19:54 UTC42d ago 1+1 queue NaN 0.7 days 0
4 Tue 15 Sep, 13:53 UTC44d ago 2 held half 2.3 days 0
5 Tue 15 Sep, 00:09 UTC45d ago 2 NaN 0.6 days 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

1000 · seed 8904910
Map of Asid's Serv - SOLO ONLY
map
Custom Map
size
1000
seed
8904910

Server

srv.info()
address
5.39.17.13:23092
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
21 Sep 2026, 17:48 UTC
hostname
–
first seen
13 Sep 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 · 477 on average46/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 321 on average86/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 284 on average202/250
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 279 on average5/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average254/300
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 258 on average285/300

Quick answers

From the figures on this page.

Population

How does Asid's Serv - SOLO ONLY compare in the rankings?

Rank #15,985 on seven-day player hours for Asid's Serv - SOLO ONLY, within the top 70% of all ranked servers.

How many players does Asid's Serv - SOLO ONLY hold at once?

The current row shows Asid's Serv - SOLO ONLY offline; the last response was 26 days 19 hours ago.

Server data

What Rust version does Asid's Serv - SOLO ONLY run?

Rust network protocol 2633 and build 165217 on Linux is what Asid's Serv - SOLO ONLY runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Asid's Serv - SOLO ONLY, and is it online now?

The latest sample has Asid's Serv - SOLO ONLY offline, with a last sighting 26 days 19 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 13 September 2026.

Which location does Asid's Serv - SOLO ONLY run from?

For Asid's Serv - SOLO ONLY, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 5.39.17.13:23092.

Settings and map

What rules and settings are recorded for Asid's Serv - SOLO ONLY?

No gather rate appears in the name: Asid's Serv - SOLO ONLY. 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. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has Asid's Serv - SOLO ONLY selected?

Size 1,000, seed 8904910: the procedural map on Asid's Serv - SOLO ONLY, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.

Wipes and dates

When does Asid's Serv - SOLO ONLY wipe, and how often?

Asid's Serv - SOLO ONLY wipes on no fixed rhythm, so there is nothing to predict. 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 38 days 10 hours ago.

What is wipe day on Asid's Serv - SOLO ONLY like?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags and filters

Which Rust Data filters and lists contain Asid's Serv - SOLO ONLY?

The Rust Data lists that Asid's Serv - SOLO ONLY fits are: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on Asid's Serv - SOLO ONLY?

The game's server browser reads these tags from Asid's Serv - SOLO ONLY: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to Asid's Serv - SOLO ONLY?

The manual route: launch Rust, F1, then client.connect 5.39.17.13:23092. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs165217
Build Build number: 165217.
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 40,937 players 11,633 servers online