Rust Data

rustdata.spaceservers104.143.3.231:28446.ipynb

Run all rust-data · live

‹ All servers

Online 104.143.3.231:28449 checked 9m ago

A Rust Server

moddedoxide

Connect

srv = rust.server("104.143.3.231:28446")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 0 # peak 1
rank #12,398 # top 56%
last wipe 7d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
0246800:0009:0018:0002:0011:0021:00

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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 56% 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.2 daysbetween real wipes
on rhythm29%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 21 OctTue 20 OctMon 19 Oct
01234+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 Wed 21 Oct, 18:16 UTC7d ago 1 NaN running 0
1 Tue 20 Oct, 23:09 UTC8d ago 1 NaN 0.8 days 0
2 Mon 19 Oct, 18:09 UTC9d ago 1 NaN 1.2 days 0
3 Sun 18 Oct, 23:45 UTC9d ago 1 NaN 0.8 days 0
4 Fri 9 Oct, 20:25 UTC19d ago 1+1 queue halved by day 1 9.1 days 0
5 Thu 8 Oct, 17:21 UTC20d ago 1 NaN 1.1 days 0
6 Fri 2 Oct, 11:13 UTC26d ago 0 NaN 6.3 days 0
7 Wed 16 Sep, 22:52 UTC42d ago 1 halved by day 1 15.5 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

2600 · seed 1
Map of A Rust Server
map
Custom Map
size
2600
seed
1

Server

srv.info()
address
104.143.3.231:28449
region
–
max players
–
group limit
20 max
wipe schedule
–
last wipe
21 Oct 2026, 18:16 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
0ShockRust | Blue | NoLimitno group limit · 157 on average61/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average57/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average53/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average17/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9/1000

Quick answers

From the figures on this page.

Population data

How does A Rust Server compare in the rankings?

Rank #12,398 on seven-day player hours for A Rust Server, within the top 56% of all ranked servers.

How full does A Rust Server run?

Point query at this second: A Rust Server returns 0 players. Over the last seven days it averaged 0 players and peaked at 1.

About the server

What does performance look like on A Rust Server?

Server fps over the last 48 hours averages 5; the floor is 5. Entity numbers reached 32,065, and that includes buildings, deployables and the rest. A high of 1,839 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does A Rust Server run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by A Rust Server. Joining needs the same protocol on your game; Steam handles the update.

How reliable is A Rust Server, and is it up?

A Rust Server reports itself online at the current refresh. The uptime it reports puts the last restart about 9 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.

Which location does A Rust Server run from?

For A Rust Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.143.3.231:28449 is its address.

Map and rules

What rules and settings are recorded for A Rust Server?

The name A Rust Server carries no gather rate. Group size tops out at 20 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.

Which map has A Rust Server loaded?

A Rust Server runs a procedural map of size 2,600 with seed 1, 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.

Wipe data

On what schedule does A Rust Server wipe?

A Rust Server 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 7 days 4 hours ago.

On A Rust Server, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Which lists on Rust Data hold A Rust Server, and which filters?

On Rust Data, A Rust Server appears in these lists: 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.

How should you read the server tags on A Rust Server?

The game's server browser reads these tags from A Rust Server: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts20 (Group limit): The team cap is 20; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.

Connecting

What is the way into A Rust Server?

In Rust, F1 opens the console: type client.connect 104.143.3.231:28449. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://discord.com/invite/feMTbPSGZJ.

Server tags · what each one means

srv.tags.decode()

Published as mp0,ptrak,$r?,v2635,gmrust,cs168909,ts20,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp0
Max players Slot count: 0.
ts20
Group limit The team cap is 20.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 55,890 players 11,751 servers online