Skip to the coverage
Live Rust server stats, updated every five minutes.
Rust Live Stats
Live
94,909 players on Rust servers right now 11,835 servers online 3,850 with players on 528 fresh wipes in the last three hours RFG Troubleshooting: 1 players (offline) Updated every five minutes

Live coverage · Rust server

RFG Troubleshooting

Offline RFG Troubleshooting is not on the server list right now. The figures below are from when it was last seen, 21d ago.

Key points

  • 1 of 40 players are on at the last check, 2% full.
  • Over the last seven days it averages 0 players.
  • It ranks #14,433, the top 65% of all ranked servers.
  • The current map has been up 28d 3h, since Thursday 1 October, 17:37 UTC.
Join
vanillamoddedcarbon

Live coverage

newest first · every post is a reading of this server

Last seen: 1 of 40 players

1/ 40players now 2% full
07-day averagepeak –
#14,433ranktop 65%
28d agolast wipeno schedule published
–next wipeno rhythm it keeps

Players on RFG Troubleshooting

Players

No hourly history yet.

Hourly average and peak, UTC.

How the server is running

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 #14,433 today

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.

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.

5.3 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse 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

Wipe peaks at 1 player

Peak
1
Crowd
–
Lasted
running
Players before
0

Wipe peaks at 0 players

Peak
0
Crowd
–
Lasted
5.4 days
Players before
0

Wipe peaks at 1 player

Peak
1
Crowd
halved by day 2
Lasted
5.1 days
Players before
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

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 151 on average
78 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
135 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 118 on average
131 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 96 on average
42 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 91 on average
135 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 85 on average
347 / 350

Quick answers

from the figures on this page

Wipe schedule

What happens on wipe day at RFG Troubleshooting?

The average peak across its recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the other cases it dropped under half by day 2.

When does RFG Troubleshooting wipe?

No next wipe can be predicted for RFG Troubleshooting, which wipes at irregular times. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 28 days 3 hours have passed since this world was generated.

Tags and filters

Who is in charge of RFG Troubleshooting?

A rfgam.ing hostname is published by RFG Troubleshooting and by 11 other servers we track, so they most likely share an operator.

Where does RFG Troubleshooting appear in Rust Live Stats lists and filters?

On Rust Live Stats, RFG Troubleshooting is listed under Modded Rust servers live now. Under the filters Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more it appears on the server list.

How should you read the tags on RFG Troubleshooting?

The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are available; ts12 (Group limit): Team cap: 12; v2634 (Protocol): You need protocol 2634 on your game to get in; cs167058 (Build): Build: 167058; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^v (Vanilla): No changed rates, kits or rules — this is the game as Facepunch ships it; ^z (Modded): Plugins or settings changes put this under Modded; ^y (Carbon): It uses the plugin framework Carbon, which RFG Troubleshooting publishes. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.

Player counts

What is the current population on RFG Troubleshooting?

RFG Troubleshooting reads offline at the moment; the last sighting was 21 days 23 hours ago.

What position does RFG Troubleshooting hold among Rust servers?

Player hours over seven days put RFG Troubleshooting at #14,433, in the top 65% of all ranked servers.

Map and rules

Which settings and rules are in force on RFG Troubleshooting?

Nothing in the name of RFG Troubleshooting states a gather rate. A group can reach 12 players at most. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Plugins run here: Carbon. Vanilla is its own label: no changed rates, kits or rules — this is the game as Facepunch ships it. VAC is enabled: Valve's anti-cheat.

Can you tell me the map for RFG Troubleshooting?

A procedural map of 3,500 with seed 116945, generated by the game, runs on RFG Troubleshooting. RustMaps shows it from this page, since equal size and seed give an equal map. For the map name it lists Royal Family Gaming FPS+.

Server facts

Where does RFG Troubleshooting sit geographically?

Nothing on RFG Troubleshooting states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 199.231.185.234:27500.

What version of Rust is running on RFG Troubleshooting?

RFG Troubleshooting operates on Linux with Rust network protocol 2634 and build 167058. To join, your game must use the same protocol; Steam handles the update for you.

How reliable is RFG Troubleshooting, and is it online at the moment?

RFG Troubleshooting is currently offline, with its last appearance 21 days 23 hours ago. It was online for 0 of 168 hours in the last 7 full days, or 0% of the time. On 26 September 2026, Rust Live Stats saw it for the first time.

How to join

How do you get onto RFG Troubleshooting?

Enter client.connect 199.231.185.234:27500 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you. The server's website: https://royalfamilygaming.com.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players 40 slots are available.
ts12
Group limit Team cap: 12.
v2634
Protocol You need protocol 2634 on your game to get in.
cs167058
Build Build: 167058.
ptrak
Networking RakNet is the network layer — the game's standard one.
$r?
Region code The server sets no region code.

Difficulty

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

Mods and access

^z
Modded Plugins or settings changes put this under Modded.
^y
Carbon It uses the 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.