Rust Server TrendsSeismic network · station log
Recording Stations11,595 Players34,229 Active2,837 Wipes · 3 h65 48 h

Station XX-12628 · recording

Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2

Online 168.119.64.99:50000 checked 8m ago

moddedoxide
Connect
Players now
0/ 40
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#12,628
top 57%
Last wipe
6d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-12628 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 40 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123405:0014:0023:0009:0018:0003:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040005:0014:0023:0009:0018:0003:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Expected events

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 gap
19.2 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Wed 21 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 21 Oct, 17:03 UTC6d ago M0.0steady 0 – running 0
Fri 2 Oct, 12:38 UTC25d ago M0.0steady 0 – 19.2 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
・RUST KILL・XXX|KILL $ CASH|FARM|SHOP|TP|HOME|KITS|PVPVEX10X groups of 10+ · weekly · 5 on average
3/ 100
MINICOPTER / HELICOPTER TRAINING groups of 8+ · 5 on average
3/ 100
PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVP NA · groups of 8+ · 5 on average
5/ 10
[EU] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 EU · no group limit · 4 on average
1/ 100
[US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 NA · no group limit · 2 on average
2/ 100
NA | Apex Aim Arena | 1v1 Facecheck FFA Targets NA · groups of 8+ · 4 on average
0/ 16
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

The procedural map on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 is size 6,000 with seed 1337, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page. The name of its map is Custom Map.

Which settings and rules apply on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

You will find no gather rate in the name of Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

At this moment, Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 records 0 players across 40 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 rank against other Rust servers?

Over the last seven days, Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 recorded enough player hours to reach #12,628 worldwide, placing it in the top 57% of all ranked servers.

Operator and location

How reliably does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 stay online?

Right now, you can reach Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. Its reported uptime points to a restart about 15 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 hold a steady tick rate?

Across the last 48 hours it averaged 229 server fps, with a floor of 75. Buildings, deployables and all the rest of the world's entities brought it to a high of 6,842. Its highest memory use was 2,771 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 hosted?

Nothing about a region comes from Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 168.119.64.99:50000.

Which Rust version is Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 running?

On Linux, Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

0 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.

How often does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 wipe, and on which days?

On record so far are too few of Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 6 days 11 hours is how long the current world has been running.

Tags

What do the server tags on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 mean?

Tags published by Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp40 (Max players): The server has 40 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 appear?

You will find Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust aim training servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Connecting

How do you connect to Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

You can connect by pressing F1 in Rust and typing client.connect 168.119.64.99:50000 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp40
Max players The server has 40 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

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.