Rust HeatmapInfrared · players
IR live Players32,393 Servers11,620 Warm2,767 Fresh wipes · 3h69 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–40° · slots

RFG Troubleshooting

Offline 199.231.185.234:27500 checked 21d ago

vanillamoddedcarbon
Sp1 · players now 1/ 40
2% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#14,433
rank
top 65%
27d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 21d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

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

Li4Rank

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.

Bx1Wipe 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 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
0%
crowd held
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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 UTC31d 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 152 on average
41 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
124 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 117 on average
0 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 93 on average
16 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 88 on average
2 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
3 / 1000

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on RFG Troubleshooting?

At their busiest, its recent wipes averaged 1 players. The crowd on the latest wipe reached its peak 0 hours in. Above half the peak until the next wipe: that held in 0% of its recent wipes. By day 2 it was below half in the wipes that did not hold.

What is the wipe schedule on RFG Troubleshooting?

No next wipe can be predicted: RFG Troubleshooting wipes when it chooses, at irregular times. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world it runs now dates from 27 days 11 hours ago.

Population

How busy is RFG Troubleshooting?

RFG Troubleshooting went quiet 21 days 7 hours ago and is offline right now.

How does RFG Troubleshooting rank against other Rust servers?

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

Rules and settings

Which map does RFG Troubleshooting run?

The map on RFG Troubleshooting is procedural, size 3,500 with seed 116945, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map. You play on a map named Royal Family Gaming FPS+.

What are the rules and settings on RFG Troubleshooting?

No gather rate appears in the name RFG Troubleshooting. The group limit is 12 players. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. The server browser lists it as Modded: plugins or settings change the game. Carbon plugins are in use. Its own label is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. Anti-cheat: Valve's VAC is on.

Location and uptime

Which version of Rust does RFG Troubleshooting run?

Rust network protocol 2634 and build 167058 on Linux is what RFG Troubleshooting runs. Your game must run the same protocol to join, and Steam takes care of updating it.

Is RFG Troubleshooting online, and how reliable is it?

RFG Troubleshooting is down just now; the last sighting was 21 days 7 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. It first appears in Rust Heatmap records on 26 September 2026.

Where is RFG Troubleshooting located?

No region is published by RFG Troubleshooting. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 199.231.185.234:27500.

Tags

Which Rust Heatmap lists and filters include RFG Troubleshooting?

The Rust Heatmap lists that RFG Troubleshooting fits are: Modded Rust servers, by live population. You will find it 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.

What do the server tags on RFG Troubleshooting mean?

The game's server browser reads the tags RFG Troubleshooting publishes: gmrust (Game mode): Survival in the standard Rust form; mp40 (Max players): Slot count: 40; ts12 (Group limit): A team holds no more than 12; v2634 (Protocol): Your game must match protocol 2634 to get in; cs167058 (Build): This build is 167058; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): Plugins run through Carbon. The top of this page also shows the tags for players now, the queue and when the world was made.

Who runs RFG Troubleshooting?

11 other servers we track publish a rfgam.ing hostname too, so one operator most likely runs them all with RFG Troubleshooting.

How to join

How do I join RFG Troubleshooting?

Enter client.connect 199.231.185.234:27500 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you. https://royalfamilygaming.com is where its website is.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust form.
mp40
Max players Slot count: 40.
ts12
Group limit A team holds no more than 12.
v2634
Protocol Your game must match protocol 2634 to get in.
cs167058
Build This build is 167058.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Difficulty

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

Mods and access

^z
Modded The game is changed by settings or plugins, so it sits under Modded.
^y
Carbon Plugins run through 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.