DWG RG-S6176Server sheetchecked 7m ago
BeamedPrivate
Online 149.202.64.146:5005 checked 7m ago
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 28% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players 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 UTC18d 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.
Similar servers
Quick answers
Server details
What uptime is recorded for BeamedPrivate, and is it up?
Right now, BeamedPrivate is recorded as online. Counted from its reported uptime, the last restart was about 6 days 3 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.
What does the recorded performance of BeamedPrivate show?
93 server fps on average over the last 48 hours, and never under 22. Counted at its highest: 111,656 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,871 MB. What players feel as lag is low fps together with a climbing entity count.
In which location is BeamedPrivate hosted?
A region is not published by BeamedPrivate. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 149.202.64.146:5005.
What Rust version is recorded for BeamedPrivate?
On Linux, BeamedPrivate runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.
Population
What does the population history show for BeamedPrivate?
Current player count on BeamedPrivate: 0, of 69 slots. Averaged across seven days, the player count is 0, with a peak of 2. Averaged over the last 48 hours, the player count is highest at 20:00 UTC: 2 players.
What rank has been recorded for BeamedPrivate?
Player hours over seven days place BeamedPrivate at #6,176, within the top 28% of ranked servers.
Schedules
What is recorded on BeamedPrivate on wipe day?
An average of 3 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 4.
What wipe schedule has been recorded for BeamedPrivate?
There is no next wipe to predict at BeamedPrivate, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 6 days 4 hours ago the current world was made.
Settings
Which settings does BeamedPrivate run, and what rules?
Gather rate for BeamedPrivate: not stated in the name. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is off.
On which map is BeamedPrivate played?
Seed 85484 and size 4,500 define the procedural map BeamedPrivate generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
Where does BeamedPrivate appear among the Rust Graphs lists and filters?
These Rust Graphs lists include BeamedPrivate: Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
On BeamedPrivate, what is meant by each tag?
The game's server browser reads these tags from BeamedPrivate: gmrust (Game mode): Survival in standard Rust style; mp69 (Max players): 69 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
What is the way to connect to BeamedPrivate?
Enter client.connect 149.202.64.146:5005 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://guavahost.com/.
Server tags
Published as mp69,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp69
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.