Station XX-14552 · recording
Aperture_Game's testing server
Online 109.247.229.146:28015 checked 11m ago
- Players now
- 1/ 3
- 33% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #14,552
- top 65%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 3 slots
- Motion · 24 h
- M0.0■steady+0 players
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 3.5 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 29 Oct, 16:36 UTC34m ago | – | – | – | – | running | 0 |
| Tue 27 Oct, 07:53 UTC2d ago | M0.0▲rising | 1 | halved by day 1 | 2.4 days | 0 | |
| Thu 22 Oct, 18:44 UTC6d ago | M0.0▲rising | 1 | halved by day 1 | 4.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Aperture_Game's testing server?
Aperture_Game's testing server uses a procedural map, which the game generates.
Which settings and rules apply on Aperture_Game's testing server?
The name of Aperture_Game's testing server gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Aperture_Game's testing server right now?
At this moment, Aperture_Game's testing server records 1 players across 3 slots. The seven-day average is 0 players, with a peak of 1.
How does Aperture_Game's testing server rank against other Rust servers?
On player hours for the past week, Aperture_Game's testing server sits at #14,552, which puts it inside the top 65% of every ranked server.
Server details
How reliably does Aperture_Game's testing server stay online?
Right now, you can reach Aperture_Game's testing server. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. Its earliest appearance in the records of Rust Server Trends dates to 19 October 2026.
Where in the world is Aperture_Game's testing server hosted?
Nothing about a region comes from Aperture_Game's testing server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 109.247.229.146:28015 is the address it uses.
What build of Rust does Aperture_Game's testing server use?
On Linux, Aperture_Game's testing server runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Aperture_Game's testing server?
1 players, on average, was the busiest crowd at its recent wipes. 1 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
How often does Aperture_Game's testing server wipe, and on which days?
There is no next wipe to predict at Aperture_Game's testing server, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 2 days 9 hours.
Server tags
What do the server tags on Aperture_Game's testing server mean?
Tags published by Aperture_Game's testing server and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp3 (Max players): The server has 3 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Aperture_Game's testing server appear?
The Rust Server Trends lists that take in Aperture_Game's testing server are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How to join
What steps get you onto Aperture_Game's testing server?
To join, enter client.connect 109.247.229.146:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.