Rust Data

rustdata.spaceservers199.231.185.234:27503.ipynb

Run all rust-data · live

‹ All servers

Offline 199.231.185.234:27500 checked 21d ago

RFG Troubleshooting

vanillamoddedcarbon

Connect

srv = rust.server("199.231.185.234:27503")
print(srv.connect_command)

Right now

srv.summary()
players now 1/40 # 2% full
7-day average 0 # peak –
rank #14,433 # top 65%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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

srv.rank.plot(invert=True)  # 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

srv.wipe_schedule()

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 7 Oct, 20:21 UTC21d ago 1 NaN running 0
1 Fri 2 Oct, 10:02 UTC27d ago 0 NaN 5.4 days 0
2 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.

display(srv.map, srv.info())

Map

3500 · seed 116945
Map of RFG Troubleshooting
map
Royal Family Gaming FPS+
size
3500
seed
116945

Server

srv.info()
address
199.231.185.234:27500
region
–
max players
40
group limit
12 max
wipe schedule
–
last wipe
1 Oct 2026, 17:37 UTC
hostname
us3x.rfgam.ing
first seen
26 Sep 2026

Operator · rfgam.ing

rust.servers(operator="rfgam.ing").sort_values("players")

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 149 on average172/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average128/100
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average74/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average21/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average25/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average259/700

Quick answers

From the figures on this page.

Player counts

What position does RFG Troubleshooting take in the server rankings?

Rank #14,433 on seven-day player hours for RFG Troubleshooting, within the top 65% of all ranked servers.

How many players does RFG Troubleshooting hold at once?

Offline now for RFG Troubleshooting, with the last sample 21 days 15 hours ago.

Server data

What Rust version does RFG Troubleshooting run?

The build is Rust network protocol 2634 and build 167058 on Linux, run by RFG Troubleshooting. Steam updates your game for you, but the protocol must match to join.

How reliable is RFG Troubleshooting, and is it up?

RFG Troubleshooting is offline at this refresh; the last response came 21 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 26 September 2026.

Which location does RFG Troubleshooting run from?

No region is published by RFG Troubleshooting. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 199.231.185.234:27500.

Rules, settings, map

What rules and settings are recorded for RFG Troubleshooting?

The name RFG Troubleshooting carries no gather rate. Group size tops out at 12 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.

Which map has RFG Troubleshooting selected?

The game generates the map on RFG Troubleshooting: procedural, size 3,500, seed 116945. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Royal Family Gaming FPS+.

Wipe schedule

On what schedule does RFG Troubleshooting wipe?

RFG Troubleshooting wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 19 hours ago.

What is wipe day on RFG Troubleshooting like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 2.

Tags and filters

Which Rust Data filters and lists contain RFG Troubleshooting?

The Rust Data lists that RFG Troubleshooting fits are: Modded Rust servers. It appears 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.

Which operator runs RFG Troubleshooting?

A rfgam.ing hostname is published by RFG Troubleshooting and by 11 other servers we track, which suggests the same operator runs them.

How should you read the server tags on RFG Troubleshooting?

Read by the game's server browser, the tags RFG Troubleshooting publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts12 (Group limit): The team cap is 12; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to RFG Troubleshooting?

In Rust, F1 opens the console: type client.connect 199.231.185.234:27500. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://royalfamilygaming.com.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players 40 slots in total.
ts12
Group limit The team cap is 12.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167058
Build The server runs build 167058.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Difficulty

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

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^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.

Rust Data 70,052 players 11,806 servers online