RFG Troubleshooting
Offline 199.231.185.234:27500 checked 21d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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
every wipe as a delivery, newest first-
Wed 7 Oct, 20:21 UTC 21:21 UK · 21d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Fri 2 Oct, 10:02 UTC 11:02 UK · 27d agoWipe delivered
- Peak
- 0
- Crowd
- –
- Lasted
- 5.4 days
- Players before
- 0
-
Sun 27 Sep, 06:36 UTC 07:36 UK · 32d agoWipe delivered
- 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 127 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 126 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 195 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 74 / 700
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 222 / 700
- RustSpain.com | EU Main 348 / 350
Quick answers
From the figures on this page.
Player activity
Where does RFG Troubleshooting place among Rust servers?
A seven-day player-hours count places RFG Troubleshooting at #14,433: the top 65% of every ranked server.
Is RFG Troubleshooting busy at the moment?
The last sighting of RFG Troubleshooting was 21 days 20 hours ago; it is offline right now.
Server rules
What is the current map on RFG Troubleshooting?
Size 3,500 and seed 116945 define the procedural map RFG Troubleshooting runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page. Its name for the map: Royal Family Gaming FPS+.
What settings and rules should you know for RFG Troubleshooting?
No gather rate appears in the name of RFG Troubleshooting. The group limit is 12 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players is allowed. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Carbon. The vanilla label is one it applies to itself: no altered rates, kits or rules: the game as shipped by Facepunch. VAC, Valve's anti-cheat, is switched on.
Operator and location
What is the location of RFG Troubleshooting?
No region is published by RFG Troubleshooting. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. You will find it at 199.231.185.234:27500.
What is the uptime of RFG Troubleshooting, and is it online?
The current status for RFG Troubleshooting is offline, last seen 21 days 20 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. 26 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is RFG Troubleshooting using?
The version on RFG Troubleshooting is Rust network protocol 2634 and build 167058, running on Linux. The same protocol is required to join, and Steam takes care of updating it.
Wipe schedule
How does RFG Troubleshooting handle its wipe days?
At their busiest, its recent wipes drew an average of 1 players. On the latest wipe, 0 hours passed before the crowd peaked. Half the peak or more was held until the next wipe in 0% of recent wipes. By day 2 it had fallen below half where the crowd did not hold.
How often does RFG Troubleshooting wipe, and at what times?
No next wipe can be predicted for RFG Troubleshooting, which wipes at irregular times. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 28 days 1 hours.
Tags and filters
Where does RFG Troubleshooting appear in Rust Wipe Tracker lists and filters?
You will find RFG Troubleshooting on the following Rust Wipe Tracker lists: Modded Rust servers. 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.
Who is behind RFG Troubleshooting?
RFG Troubleshooting and 11 other servers we track both publish a rfgam.ing hostname, which points to the same operator in all likelihood.
How should you read the tags on RFG Troubleshooting?
Read off the game's server browser, the tags for RFG Troubleshooting are: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): It holds 40 slots; ts12 (Group limit): Team size caps at 12; v2634 (Protocol): Protocol 2634 is required; a different version can't join; cs167058 (Build): Build number: 167058; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^v (Vanilla): No altered rates, kits or rules: the game as shipped by Facepunch; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon, a plugin framework, is installed here. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
Connecting
What steps do you take to join RFG Troubleshooting?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 199.231.185.234:27500. https://royalfamilygaming.com is its website.