Rust Data LabData lab · live
Live readings Servers11,869 Players90,153 Populated3,832 Fresh wipes · 3h374 Sampled every 5 min

Element card · group Modded · atomic number 14,560, its rank

Aperture_Game's testing server

Online 109.247.229.146:28015 checked 7m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 3 0% full Room to join
7-day average0peak 1
Rank · atomic number#14,560top 65%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123416:0001:0010:0019:0004:0013:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

daily · 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.

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap4.5 daysbetween real 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 07:53 UTC2d ago 1 – running 0
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 186
    ShockRust | Blue | NoLimit no group limit · 149 on average 186/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 134
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 134/ 100
  3. 3 Re RETRO RUST #1 … 179
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 179/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 91
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average 91/ 700
  5. 5 Ru RustSpain.com … 284
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 86 on average 284/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 236
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 86 on average 236/ 700

Quick answers

from the figures on this page

Server setup

How is Aperture_Game's testing server configured, and what rules apply?

Nothing in the name of Aperture_Game's testing server gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, raiding, building and gathering: the standard game. Raids and player fights are part of play here. The server browser lists it under Modded, where plugins or settings change the game. Plugins in use: Oxide. Anti-cheat is on: Valve's VAC.

Server facts

What region hosts Aperture_Game's testing server?

Nothing about a region is published by Aperture_Game's testing server. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 109.247.229.146:28015.

On what Rust version does Aperture_Game's testing server operate?

On Linux, Aperture_Game's testing server is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is Aperture_Game's testing server for staying online?

At the moment, Aperture_Game's testing server is online. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. The first sighting by Rust Data Lab was on 19 October 2026.

Wipes and resets

What is the wiping pattern on Aperture_Game's testing server?

The record holds too few of Aperture_Game's testing server's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. 2 days 7 hours ago the current world was made.

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

At their busiest, recent wipes averaged 1 players. Peak numbers on the latest wipe came 1 hours in. Half that peak was held until the next wipe in 0% of recent wipes. In the other cases, half the peak was lost by day 1.

Tags, lists

Which meanings sit behind the tags on Aperture_Game's testing server?

The game's server browser reads the tags Aperture_Game's testing server publishes, which are gmrust (Game mode): Standard Rust survival is the game here; mp3 (Max players): Player slots: 3; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it lists under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does Aperture_Game's testing server come up?

These themed Rust Data Lab lists carry Aperture_Game's testing server: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Player counts

What position does Aperture_Game's testing server hold among Rust servers?

Player hours over the last week put Aperture_Game's testing server at #14,560, inside the top 65% of ranked servers.

What does the current player count on Aperture_Game's testing server tell you?

At the moment Aperture_Game's testing server has 0 of its 3 slots filled. A seven-day sample gives 0 players on average and 1 at the top.

Getting on

What steps get you onto Aperture_Game's testing server?

In Rust, press F1 and enter client.connect 109.247.229.146:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp3
Max players Player slots: 3.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it lists 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.