Rust Data

rustdata.spaceservers192.99.75.83:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 192.99.75.83:28015 checked 7d ago

ASHFALL | LAST STAND

moddedoxide

Connect

srv = rust.server("192.99.75.83:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,409 # top 69%
last wipe 8d 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 69% 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 daysbetween real wipes
on rhythm43%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 20 OctSat 17 OctFri 16 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 3 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 00:28 UTC8d ago 3 NaN running 0
1 Sat 17 Oct, 23:08 UTC10d ago 3 held half 2.1 days 0
2 Fri 16 Oct, 23:08 UTC11d ago 4 NaN 1 days 4
3 Thu 15 Oct, 21:37 UTC13d ago 5 NaN 1.1 days 0
4 Thu 15 Oct, 01:31 UTC13d ago 5 NaN 0.8 days 2
5 Wed 14 Oct, 00:45 UTC14d ago 4 NaN 1 days 0
6 Thu 1 Oct, 18:00 UTC FW27d ago 25 halved by day 6 12.3 days 6
7 Thu 1 Oct, 00:16 UTC27d ago 25 NaN 0.7 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

3000 · seed 0
No map picture published
map
Procedural Map
size
3000
seed
–

Server

srv.info()
address
192.99.75.83:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 00:28 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
YOU WILL DIE. YOUR BASE WILL FALL. 23 hours to build. 1 hours to survive. 24 escalating Horde waves. Daily map wipes. Persistent blueprints and skills. Every defense will be tested. Every mistake will cost you. The world resets. Your progress doesn't. ASHFALL — THE HORDE ALWAYS WINS.

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average74/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average72/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 91 on average58/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average18/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9/1000

Quick answers

From the figures on this page.

Player counts

How does ASHFALL | LAST STAND compare in the rankings?

Player hours over seven days put ASHFALL | LAST STAND at #15,409, in the top 69% of the ranked set.

How many players does ASHFALL | LAST STAND hold at once?

The current row shows ASHFALL | LAST STAND offline; the last response was 7 days 22 hours ago.

Server facts

What is the Rust version on ASHFALL | LAST STAND?

Version Rust network protocol 2634 and build 167781 on Linux is reported by ASHFALL | LAST STAND. Joining needs the same protocol on your game; Steam handles the update.

How reliable is ASHFALL | LAST STAND, and is it online now?

Offline now for ASHFALL | LAST STAND, last seen 7 days 22 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Where does ASHFALL | LAST STAND sit?

No region is published by ASHFALL | LAST STAND. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 192.99.75.83:28015.

Rules, settings, map

Which settings and rules does ASHFALL | LAST STAND run?

No gather rate appears in the name: ASHFALL | LAST STAND. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on ASHFALL | LAST STAND?

Generated by the game at size 3,000, the map on ASHFALL | LAST STAND is procedural.

Wipe schedule

When does ASHFALL | LAST STAND wipe, and on what schedule?

Irregular wipe times on ASHFALL | LAST STAND leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 8 days 22 hours ago, and that is the one in play.

What is wipe day on ASHFALL | LAST STAND like?

The average peak over recent wipes is 3 players. Peak population on the latest wipe came 3 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold ASHFALL | LAST STAND, and which filters?

These Rust Data lists include ASHFALL | LAST STAND: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on ASHFALL | LAST STAND hold?

The game's server browser reads these tags from ASHFALL | LAST STAND: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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

What is the way into ASHFALL | LAST STAND?

The manual route: launch Rust, F1, then client.connect 192.99.75.83:28015. 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 mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 60,085 players 11,768 servers online