Rust StatisticsWorking papers on every public Rust server · 103,852 players now

Aperture_Game's testing server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 8m ago · 109.247.229.146:28015

Abstract

We describe the public Rust server Aperture_Game's testing server, reached at 109.247.229.146:28015. At the last check it held 0 of 3 places, against a seven-day mean of 0 and a peak of 11. It ranks #14,158 of all servers, the top 63%. It last wiped 2h ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/30% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#14,158top 63%
Last wipe2h agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeakWipe
00.250.50.75119:0004:0013:0023:0008:0017:00Wiped Thu 29 Oct, 16:36 UTCWIPE
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 63% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k19 Oct21 Oct23 Oct25 Oct27 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

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

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
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
Tue 27 OctThu 22 Oct
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 29 Oct, 16:362h ago – – running 0
Tue 27 Oct, 07:532d ago 1 halved by day 1 2.4 d 0
Thu 22 Oct, 18:446d ago 1 halved by day 1 4.5 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address109.247.229.146:28015
Region–
Max players3
Group limit8, the default
Wipe schedule–
Last wipe29 Oct 2026, 16:36 UTC
Hostname–
First seen19 Oct 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average120/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average197/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average75/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 89 on average228/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average348/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of Aperture_Game's testing server?

There is no region published for Aperture_Game's testing server. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 109.247.229.146:28015.

A.2How reliable is Aperture_Game's testing server, and is it currently online?

Aperture_Game's testing server is currently online. Its uptime over the last full days (7 days) was 99%, with 167 of 168 hours online. It was first observed on 19 October 2026 by Rust Statistics.

A.3What is the Rust version for Aperture_Game's testing server?

Aperture_Game's testing server is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does Aperture_Game's testing server follow for wipes?

Prediction of the next wipe is impossible for Aperture_Game's testing server, which wipes irregularly. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 2 hours ago.

A.5What happens on Aperture_Game's testing server when wipe day arrives?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 1 hours after the latest wipe. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. If not, the population dropped below half by day 1.

Player count

A.6What position does Aperture_Game's testing server occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Aperture_Game's testing server at #14,158, within the top 63% of ranked servers.

A.7How would you characterise the player activity on Aperture_Game's testing server?

On Aperture_Game's testing server, 0 of the 3 slots are occupied at present. The peak over seven days is 1, against an average of 0. Of the last 48 hours, the peak hour falls at 17:00 UTC, with an average of 0 players.

Tags, lists

A.8What do the tags associated with Aperture_Game's testing server signify?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp3 (Max players): 3 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which Aperture_Game's testing server publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Aperture_Game's testing server be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Aperture_Game's testing server fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Settings and map

A.10What are the settings and rules that govern Aperture_Game's testing server?

Its name carries no gather rate for Aperture_Game's testing server. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.11What is the map for Aperture_Game's testing server?

A procedural map, generated by the game, is what Aperture_Game's testing server runs.

How to join

A.12How do you connect to Aperture_Game's testing server?

Press F1 inside Rust to open the console and enter client.connect 109.247.229.146:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp3Max players. 3 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.