Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO S SRV11,617online PAX33,246playing OCC2,800with players WIPED 3H72
MODModded traffic
Callsign

BMD6338=

BeamedPrivate

Online 149.202.64.146:5005 checked 9m ago

moddedoxide
Clearance · join
Players now 0/ 69 0% full
7-day average0peak 2
Rank#6,338top 28%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeak
00.511.5207:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Server performance

05010015020007:0016:0001:0010:0020:0005: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Flight plan

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.

usual gap1.9 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 4

The first 48 hours of its last wipes

Thu 22 OctTue 13 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 21:03 UTC6d ago 1 – running 0
Tue 13 Oct, 17:16 UTC15d ago 4 halved by day 4 9.2 days 1
Mon 12 Oct, 17:27 UTC16d ago 3 – 1 days 0
Sun 11 Oct, 00:36 UTC18d ago 3 – 1.7 days 2
Sat 10 Oct, 01:38 UTC19d ago 2 – 1 days 1
Wed 7 Oct, 22:33 UTC21d ago 2 held half 2.1 days 0
Fri 2 Oct, 23:19 UTC26d ago 1 held half 5 days 1
Thu 1 Oct, 22:52 UTC FW27d ago 1 – 1 days 0
Thu 17 Sep, 18:05 UTC41d ago 2 held half 14.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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign SHC102no group limit · 151 on average ShockRust | Blue | NoLimit
    Players 54/500
  2. 02MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 130/100
  3. 03MOD
    Callsign RTR811EU · groups of 16+ · weekly · 117 on average RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
    Players 72/225
  4. 04MOD
    Callsign RUS021EU · groups of 16+ · monthly · 93 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 22/700
  5. 05MOD
    Callsign RST016EU · groups of 12+ · weekly · 88 on average RustSpain.com | EU Main
    Players 3/200
  6. 06MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 6/1000
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does BeamedPrivate appear in Rust Tracker lists and filters?

These Rust Tracker lists carry BeamedPrivate: Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which tags does BeamedPrivate carry, and what do they mean?

Listed for the server browser to read, BeamedPrivate publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp69 (Max players): Slots: 69; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

What should you expect on BeamedPrivate when wipe day lands?

At their busiest, recent wipes averaged 3 players. 0 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. By day 4 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for BeamedPrivate?

Irregular wipe times at BeamedPrivate: there is no next wipe to predict. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 6 days 9 hours.

Server Details

Is BeamedPrivate up, and how does its uptime hold?

BeamedPrivate is up and online at this moment. About 6 days 8 hours ago it restarted last, based on reported uptime. 99% uptime over the last 7 full days, with 167 of 168 hours up. First contact for Rust Tracker: 13 September 2026.

Which Rust version is confirmed on BeamedPrivate?

Rust network protocol 2635 and build 168909 is the build on BeamedPrivate; the platform is Linux. To join, your game must be on the same protocol; Steam handles the update.

Is BeamedPrivate holding performance?

For the last 48 hours it averaged 94 server fps; the floor was 22. Maximum entities carried: 111,656, from buildings and deployables to everything else. Peak memory use: 4,871 MB. Lag, as players experience it, comes from low fps and a rising entity count.

What location is BeamedPrivate hosted in?

Region: none published by BeamedPrivate. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 149.202.64.146:5005.

Player Count

How many players are on BeamedPrivate right now?

Slots 69; players on board 0: that is BeamedPrivate now. Seven-day average 0 players; peak 2. Peak traffic in the last 48 hours came at 20:00 UTC, averaging 2 players.

Where does BeamedPrivate sit in the server rankings?

Seven-day player hours put BeamedPrivate at #6,338, within the top 28% of all ranked servers.

Settings

Which settings and rules are confirmed on BeamedPrivate?

No gather rate appears in BeamedPrivate's name. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. Off: VAC, Valve's anti-cheat.

Which map is confirmed for BeamedPrivate?

Generated by the game from seed 85484, the procedural map on BeamedPrivate measures 4,500. Size and seed match, so the map is the same: view it on RustMaps from this page.

How to Join

How do you get onto BeamedPrivate?

To connect: start Rust, press F1, enter client.connect 149.202.64.146:5005 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://guavahost.com/.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp69
Max players Slots: 69.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is 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.