RUST METRICSFlight deck · live data
Data live Servers11,711 Players51,860 Populated3,326 Fresh wipes 3 h136 Scan5 min
‹ All servers168.119.64.99:50000
Online Full Queue Fresh wipe Wipe due No query

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

Online 168.119.64.99:50000 checked 9m ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

last reading Tue 23:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 238 SERVER FPS

Server fps

48 h low 75 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 6,711 ×1000

Entities

48 h range 5,506–6,831 · memory 2,036 MB
1239 ET SINCE RESTART 11:04

Uptime

11 h 4 min since its last restart, at the last reading
7-day average0peak 1
Rank#12,600top 57%
Last wipe6d agono schedule published
Next wipe–too few wipes seen yet
Memory2,036MBat the last reading
REC 1

Players
AveragePeak
0123401:0010:0019:0005:0014:0023:00

Hourly average and peak, UTC.

REC 2

Server performance
010020030040001:0010:0019:0005:0014:0023: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

PLAN

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 gap19.2 daysbetween real wipes
wipe-day peak0players, 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.

LOG

Wipes

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

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 follow?

To tell the rhythm of Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 6 days 7 hours ago.

Tags

How should you read the tags on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

These are the tags Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): Slots: 40; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2?

These Rust Metrics lists carry Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2: Modded Rust servers, checked live and Aim training servers, live readings. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Player count

What position does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 hold among Rust servers?

Ranking for Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2: #12,600 on seven-day player hours, top 57% of all ranked servers.

How full does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 get?

Current headcount on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2: 0 players, 40 slots available. Check: players over seven days. Average 0, peak 1.

Server details

Where does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 sit?

No region tag on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 168.119.64.99:50000.

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

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. Matching protocol is required to join. Let Steam update your game.

Is performance on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 within range?

Over the last 48 hours the average was 229 server fps; the floor was 75. Check: entities. The peak was 6,831, counting buildings, deployables and the rest of the world. Memory peak: 2,771 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2, and is it online?

Reading: online. Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 answers right now. By its reported uptime, the last restart was roughly 11 hours ago. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What rules does Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 enforce, and what are its settings?

No gather rate appears in the name: Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

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

Size 6,000 and seed 1337: the game generates the procedural map on Beans AimTrain Targets/Tracking/Facechecks/Recoil/bow/ak/UKN #2 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

Connection

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

To join: start Rust, press F1 and type client.connect 168.119.64.99:50000. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players Slots: 40.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.