Rust Data

rustdata.spaceservers109.247.229.146:28017.ipynb

Run all rust-data · live

‹ All servers

Online 109.247.229.146:28015 checked 13m ago

Aperture_Game's testing server

moddedoxide

Connect

srv = rust.server("109.247.229.146:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/3 # 0% full
7-day average 0 # peak 1
rank #14,552 # top 65%
last wipe 1h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75118:0003:0012:0022:0007:0016:00

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
15k10k15k20k19 Oct21 Oct23 Oct25 Oct27 Oct29 Oct

Top 65% 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 gap3.5 daysbetween real wipes
on rhythm0%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

Tue 27 OctThu 22 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 16:36 UTC1h ago NaN NaN running 0
1 Tue 27 Oct, 07:53 UTC2d ago 1 halved by day 1 2.4 days 0
2 Thu 22 Oct, 18:44 UTC6d ago 1 halved by day 1 4.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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
109.247.229.146:28015
region
–
max players
3
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 16:36 UTC
hostname
–
first seen
19 Oct 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 · 151 on average144/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average131/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average196/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average90/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average226/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average348/350

Quick answers

From the figures on this page.

Player counts

How does Aperture_Game's testing server compare in the rankings?

Over the last seven days Aperture_Game's testing server sits at #14,552 on player hours, in the top 65% of ranked servers.

How full does Aperture_Game's testing server run?

The sample now reads 0 players for Aperture_Game's testing server, out of 3 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 16:00 UTC, mean 0 players.

About the server

What is the Rust version on Aperture_Game's testing server?

Version Rust network protocol 2635 and build 168909 on Linux is reported by Aperture_Game's testing server. The protocol has to match before you can join, and Steam does the updating.

Is Aperture_Game's testing server up, and what does its uptime show?

Online is the state at the latest refresh for Aperture_Game's testing server. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 19 October 2026.

Where does Aperture_Game's testing server sit?

No region is published by Aperture_Game's testing server. Rust Data does not look up where the machine stands; it shows where a server says it is. 109.247.229.146:28015 is its address.

Rules, settings, map

Which settings and rules does Aperture_Game's testing server run?

You will not find a gather rate in the string Aperture_Game's testing server. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

What is the map on Aperture_Game's testing server?

Aperture_Game's testing server runs a procedural map, which the game generates.

Wipe schedule

When does Aperture_Game's testing server wipe, and on what schedule?

No next wipe can be predicted for Aperture_Game's testing server, which wipes at irregular times. 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 1 hours ago, and that is the one in play.

On Aperture_Game's testing server, what happens on wipe day?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.

Lists and tags

Where does Aperture_Game's testing server appear among Rust Data lists and filters?

On Rust Data, Aperture_Game's testing 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 24 hours.

How should you read the server tags on Aperture_Game's testing server?

The game's server browser reads these tags from Aperture_Game's testing server: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to Aperture_Game's testing server?

Enter client.connect 109.247.229.146:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp3
Max players The server lists 3 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 102,621 players 11,897 servers online