StatusLive Servers online11,703 Players49,472 Populated2,998 Wiped · 3 h104 Interval5 min Date30 OCT 2026

DWG RG-S14433Server sheetchecked 22d ago

RFG Troubleshooting

Offline 199.231.185.234:27500 checked 22d ago

vanillamoddedcarbon
Connect
Players now 1/ 40 2% full
7-day average0peak –
Rank#14,433top 65%
Last wipe28d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on RFG Troubleshooting
Fig. 2

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

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep30 Sep3 Oct7 Oct10 Oct14 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 gap5.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Wed 7 OctFri 2 OctSun 27 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 20:21 UTC22d ago 1 – running 0
Fri 2 Oct, 10:02 UTC27d ago 0 – 5.4 days 0
Sun 27 Sep, 06:36 UTC32d ago 1 halved by day 2 5.1 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 151 on average
15 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
132 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average
34 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average
2 / 700
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average
6 / 700
06
RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average
127 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for RFG Troubleshooting, and is it up?

The current state of RFG Troubleshooting is offline, with the last sighting 22 days 4 hours ago. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 26 September 2026 is when Rust Graphs first saw it.

In which location is RFG Troubleshooting hosted?

There is no region published by RFG Troubleshooting. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 199.231.185.234:27500.

On which Rust version is RFG Troubleshooting running?

On Linux, RFG Troubleshooting runs Rust network protocol 2634 and build 167058. To join, your game must be on the same protocol; Steam handles the update.

Population

How many players are plotted on RFG Troubleshooting?

No response from RFG Troubleshooting; the server was last seen 22 days 4 hours ago.

In the rankings, which position does RFG Troubleshooting hold?

Within the top 65% of all ranked servers: RFG Troubleshooting at #14,433 for player hours, seven days recorded.

Schedules

What is recorded on RFG Troubleshooting on wipe day?

An average of 1 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. By day 2 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for RFG Troubleshooting?

No next wipe can be predicted for RFG Troubleshooting: its wipes fall 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. 28 days 8 hours ago the current world was made.

Rules and settings

What settings and rules apply on RFG Troubleshooting?

The name of RFG Troubleshooting records no gather rate. The group limit is 12 players. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Carbon. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat: VAC, from Valve, is on.

What is the map for RFG Troubleshooting?

RFG Troubleshooting runs a procedural map of size 3,500 with seed 116945, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Royal Family Gaming FPS+.

Filters

Where does RFG Troubleshooting appear among the Rust Graphs lists and filters?

These Rust Graphs lists include RFG Troubleshooting: Modded Rust servers. It is returned by these filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more.

On RFG Troubleshooting, what is meant by each tag?

Tags published by RFG Troubleshooting, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): Slots: 40; ts12 (Group limit): Team size is capped at 12; v2634 (Protocol): Your game must match protocol 2634 to join; cs167058 (Build): The game build is 167058; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Plugin framework: Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Which operator runs RFG Troubleshooting?

A rfgam.ing hostname is published by RFG Troubleshooting, as it is by 11 other servers we track; the same operator most likely runs them.

Connect

How is RFG Troubleshooting joined?

In Rust, press F1 and type client.connect 199.231.185.234:27500 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://royalfamilygaming.com is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,^z,^y,^v,gmrust,cs167058,ts12

Game

gmrust
Game mode Standard survival, as Rust plays.
mp40
Max players Slots: 40.
ts12
Group limit Team size is capped at 12.
v2634
Protocol Your game must match protocol 2634 to join.
cs167058
Build The game build is 167058.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon Plugin framework: Carbon.

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.

KeyTag string decoded