Rust Server TrendsSeismic network · station log
Recording Stations11,770 Players75,264 Active3,495 Wipes · 3 h240 48 h

Station XX-14433 · no signal

RFG Troubleshooting

Offline 199.231.185.234:27500 checked 22d ago

vanillamoddedcarbon
Connect
Players now
1/ 40
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,433
top 65%
Last wipe
28d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-14433 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 40 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 7 Oct, 20:21 UTC22d ago M0.0rising 1 – running 0
Fri 2 Oct, 10:02 UTC27d ago M0.0steady 0 – 5.4 days 0
Sun 27 Sep, 06:36 UTC32d ago M0.0rising 1 halved by day 2 5.1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 150 on average
36/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average
71/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
30/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 92 on average
74/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
293/ 310
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RFG Troubleshooting?

Generated by the game, the map on RFG Troubleshooting is procedural, size 3,500 with seed 116945. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Royal Family Gaming FPS+.

Which settings and rules apply on RFG Troubleshooting?

The name of RFG Troubleshooting gives no gather rate. 12 players is the most a group can hold. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Carbon. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on RFG Troubleshooting?

No players are recorded on RFG Troubleshooting at this moment; it is offline, and the last sighting was 22 days ago.

How does RFG Troubleshooting rank against other Rust servers?

The last seven days of player hours place RFG Troubleshooting at #14,433, in the top 65% of all ranked servers.

Server facts

How reliably does RFG Troubleshooting stay online?

No contact with RFG Troubleshooting right now, and the last recorded contact was 22 days ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 26 September 2026.

Which region does RFG Troubleshooting run from?

Nothing about a region comes from RFG Troubleshooting. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 199.231.185.234:27500 is the address it uses.

Which Rust version is RFG Troubleshooting running?

RFG Troubleshooting is running Rust network protocol 2634 and build 167058 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on RFG Troubleshooting?

The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 2 in the wipes where it didn't hold.

On what timetable does RFG Troubleshooting run its wipes?

There is no next wipe to predict at RFG Troubleshooting, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 28 days 5 hours.

Tags

What do the server tags on RFG Troubleshooting mean?

Tags published by RFG Troubleshooting and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are available; ts12 (Group limit): Each team can hold up to 12; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167058 (Build): Game build: 167058; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does RFG Troubleshooting appear?

You will find RFG Troubleshooting on the following Rust Server Trends lists: Modded Rust servers, tracked live. 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.

Which person or group runs RFG Troubleshooting?

One operator most likely runs these: RFG Troubleshooting and 11 other servers we track, all publishing a rfgam.ing hostname.

How to join

What steps get you onto RFG Troubleshooting?

Enter client.connect 199.231.185.234:27500 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://royalfamilygaming.com.

Instrument codes

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 Each team can hold up to 12.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167058
Build Game build: 167058.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been 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 plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.