Offline 199.231.185.234:27500 checked 21d ago
RFG Troubleshooting
Connect
srv = rust.server("199.231.185.234:27503")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_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())
Operator · rfgam.ing
rust.servers(operator="rfgam.ing").sort_values("players")
12 servers publish a rfgam.ing hostname; the busiest are listed.
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 74/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 21/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 25/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 259/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.