Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO M SRV11,658online PAX48,164playing OCC3,140with players WIPED 3H112
MODModded traffic
Callsign

RFG14433

RFG Troubleshooting

Offline 199.231.185.234:27500 checked 21d ago

vanillamoddedcarbon
Clearance · join
Players now 1/ 40 2% full
7-day average0peak –
Rank#14,433top 65%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

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 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

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 20:21 UTC21d ago 1 – running 0
Fri 2 Oct, 10:02 UTC26d 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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign SHC102no group limit · 149 on average ShockRust | Blue | NoLimit
    Players 108/500
  2. 02MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 134/100
  3. 03MOD
    Callsign RTR811EU · groups of 16+ · weekly · 118 on average RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
    Players 168/225
  4. 04MOD
    Callsign RUS021EU · groups of 16+ · monthly · 93 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 49/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 24/1000
ATIS · this server

Quick answers

From the figures on this page.

Filters

Where does RFG Troubleshooting appear in Rust Tracker lists and filters?

These Rust Tracker lists carry RFG Troubleshooting: Modded servers, tracked live. It comes up under these filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more.

How should you read the tags on RFG Troubleshooting?

Listed for the server browser to read, RFG Troubleshooting publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp40 (Max players): Slots: 40; ts12 (Group limit): Team limit: 12; v2634 (Protocol): Join only if your game is on protocol 2634; cs167058 (Build): This server runs game build 167058; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^z (Modded): The game is changed by plugins or settings; listed under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; all appear 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; same operator, most likely.

Wipe Schedule

What should you expect on RFG Troubleshooting when wipe day lands?

Recent wipes averaged a peak of 1 players. 0 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The fall below half came by day 2 where it did not hold.

On what schedule does RFG Troubleshooting wipe?

Irregular wipe times at RFG Troubleshooting: 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 27 days 15 hours.

Location and Status

Is RFG Troubleshooting up, and how does its uptime hold?

Tracking shows RFG Troubleshooting offline as of now, last seen 21 days 11 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. The first sighting by Rust Tracker was 26 September 2026.

What Rust version is RFG Troubleshooting on?

Rust network protocol 2634 and build 167058 on Linux is what RFG Troubleshooting runs. Steam updates it for you; your game must share the protocol to join.

Which location is RFG Troubleshooting in?

Region: none published by RFG Troubleshooting. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 199.231.185.234:27500.

Player Count

What is the player count on RFG Troubleshooting?

Last seen 21 days 11 hours ago; RFG Troubleshooting is offline at present.

How does RFG Troubleshooting compare in the rankings?

Seven-day player hours put RFG Troubleshooting at #14,433, within the top 65% of all ranked servers.

Settings

Which settings and rules are confirmed on RFG Troubleshooting?

No gather rate appears in RFG Troubleshooting's name. Up to 12 players per group. 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. The plugin count stands at Carbon. Its label is vanilla: facepunch's game unaltered: rates, kits and rules unchanged. On: VAC, Valve's anti-cheat.

Which map is confirmed for RFG Troubleshooting?

A procedural map of size 3,500 runs on RFG Troubleshooting, generated by the game from seed 116945. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Royal Family Gaming FPS+.

Connect

Which steps join RFG Troubleshooting?

Open the console in Rust with F1 after starting the game, then type client.connect 199.231.185.234:27500. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://royalfamilygaming.com.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp40
Max players Slots: 40.
ts12
Group limit Team limit: 12.
v2634
Protocol Join only if your game is on protocol 2634.
cs167058
Build This server runs game build 167058.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Difficulty

^v
Vanilla Facepunch's game unaltered: rates, kits and rules unchanged.

Mods and access

^z
Modded The game is changed by plugins or settings; listed under 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.