Skip to the page
Network live 11,770 servers online 75,264 players aboard 241 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Aperture_Game's testing server

Online 109.247.229.146:28015 checked 8m ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 6h ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 3 players now 0% full
07-day averagepeak 1
#13,581ranktop 61%
6h agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeakWipe
00.250.50.75123:0008:0017:0003:0012:0021:00Wiped Thu 29 Oct, 16:36 UTCWIPE

Hourly average and peak, UTC.

Server performance

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

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

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.

3.5 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse 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

every wipe as a delivery, newest first
  1. Thu 29 Oct, 16:36 UTC 16:36 UK · 6h ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Tue 27 Oct, 07:53 UTC 07:53 UK · 2d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    2.4 days
    Players before
    0
  3. Thu 22 Oct, 18:44 UTC 19:44 UK · 7d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    4.5 days
    Players before
    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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 150 on average 36 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 121 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average 71 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average 30 / 700
  5. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average 74 / 700
  6. RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average 293 / 310
Help desk

Quick answers

From the figures on this page.

Player count

What is the ranking of Aperture_Game's testing server against other Rust servers?

A seven-day player-hours count places Aperture_Game's testing server at #13,581: the top 61% of every ranked server.

What is the current population on Aperture_Game's testing server?

Checking now: 0 players on 3 slots at Aperture_Game's testing server. The seven-day figures show an average of 0 players and a peak of 1. Over the last 48 hours, the peak hour came at 17:00 UTC with an average of 0 players.

Rules and settings

Which map is active on Aperture_Game's testing server?

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

Which settings and rules apply on Aperture_Game's testing server?

No gather rate appears in the name of Aperture_Game's testing server. The game's default applies: 8 players to a group at most. It runs survival, the usual game: build, gather, raid. Fighting and raiding between players is allowed. The server browser lists it as Modded, because plugins or settings alter the game. Oxide supplies the plugins. The VAC anti-cheat from Valve is enabled.

About the server

In which region is Aperture_Game's testing server based?

You will find no region published by Aperture_Game's testing server. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 109.247.229.146:28015 is its address.

What is the uptime of Aperture_Game's testing server, and is it online?

You can find Aperture_Game's testing server online at present. It was up 167 of 168 hours over the last 7 full days, 99% of the time. 19 October 2026 is when Rust Wipe Tracker first recorded it.

What Rust version is Aperture_Game's testing server using?

The version on Aperture_Game's testing server is Rust network protocol 2635 and build 168909, running on Linux. The same protocol is required to join, and Steam takes care of updating it.

Wipe times

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

1 players is the average peak across its recent wipes. 1 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the other cases it sank under half by day 1.

How often does Aperture_Game's testing server wipe, and at what times?

Aperture_Game's testing server wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 6 hours.

Tags and filters

Where does Aperture_Game's testing server appear across the Rust Wipe Tracker lists and filters?

These Rust Wipe Tracker lists take Aperture_Game's testing server: Modded Rust servers. On the server list, apply Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours and it appears.

What is the meaning of the server tags on Aperture_Game's testing server?

The game's server browser picks up these Aperture_Game's testing server tags: gmrust (Game mode): Standard Rust survival is the game mode here; mp3 (Max players): It holds 3 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

How to join

What steps do you take to join Aperture_Game's testing server?

Enter client.connect 109.247.229.146:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

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 mode here.
mp3
Max players It holds 3 slots.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.

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.