Online 64.40.8.117:28054 checked 9m ago
Royal Family Gaming | Event/Dev|F1 Spawn|Staging|
Connect
srv = rust.server("64.40.8.117:27017")
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 17 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 55% 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, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 10:01 UTC14h ago | NaN | NaN | running | 0 |
| 1 | Sun 27 Sep, 19:07 UTC32d ago | 1 | NaN | NaN | 0 |
| 2 | Sat 26 Sep, 20:07 UTC33d ago | 1 | NaN | 1 days | 0 |
| 3 | Thu 24 Sep, 14:55 UTC35d ago | 1 | halved by day 1 | 2.2 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.
About this server · in its own words
print(srv.description)
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 | 31/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 15/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 215/260 |
Quick answers
From the figures on this page.
Population data
How does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| compare in the rankings?
Rank #12,225 on seven-day player hours for Royal Family Gaming | Event/Dev|F1 Spawn|Staging|, within the top 55% of all ranked servers.
How many players does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| hold at once?
Current row: 0 players on Royal Family Gaming | Event/Dev|F1 Spawn|Staging|, against 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 15:00 UTC is the busiest, at 0 players.
Server facts
How well does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| perform?
Averaged over 48 hours: 60 server fps, never under 60. Entity numbers reached 107,000, and that includes buildings, deployables and the rest. The memory field tops out at 3,005 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| run?
Rust network protocol 2636 and build 169627 on Linux is what Royal Family Gaming | Event/Dev|F1 Spawn|Staging| runs. Joining needs the same protocol on your game; Steam handles the update.
Is Royal Family Gaming | Event/Dev|F1 Spawn|Staging| up, and what does its uptime show?
Royal Family Gaming | Event/Dev|F1 Spawn|Staging| reports itself online at the current refresh. A restart about 12 hours ago is what its reported uptime implies. 143 of 168 hours up over the last 7 full days, or 85%. Rust Data logged it first on 13 September 2026.
In which location is Royal Family Gaming | Event/Dev|F1 Spawn|Staging| hosted?
There is no region published for Royal Family Gaming | Event/Dev|F1 Spawn|Staging|. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 64.40.8.117:28054.
Rules, settings, map
Which settings and rules does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| run?
No gather rate appears in the name: Royal Family Gaming | Event/Dev|F1 Spawn|Staging|. Group size tops out at 12 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.
What is the map on Royal Family Gaming | Event/Dev|F1 Spawn|Staging|?
Royal Family Gaming | Event/Dev|F1 Spawn|Staging| runs a procedural map of size 3,800 with seed 285119, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Royal Family Gaming FPS+.
Wipes and dates
When does Royal Family Gaming | Event/Dev|F1 Spawn|Staging| wipe, and how often?
Royal Family Gaming | Event/Dev|F1 Spawn|Staging| wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 14 hours ago.
What is wipe day on Royal Family Gaming | Event/Dev|F1 Spawn|Staging| like?
Recent wipes averaged 1 players at their peak. 2 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Lists and tags
Which Rust Data filters and lists contain Royal Family Gaming | Event/Dev|F1 Spawn|Staging|?
These Rust Data lists include Royal Family Gaming | Event/Dev|F1 Spawn|Staging|: 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; Last wipe: In the last 24 hours.
Which operator runs Royal Family Gaming | Event/Dev|F1 Spawn|Staging|?
The same operator most likely runs Royal Family Gaming | Event/Dev|F1 Spawn|Staging| and 11 other servers we track, as all publish a rfgam.ing hostname.
Which meanings do the tags on Royal Family Gaming | Event/Dev|F1 Spawn|Staging| hold?
The game's server browser reads these tags from Royal Family Gaming | Event/Dev|F1 Spawn|Staging|: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts12 (Group limit): No team may exceed 12; v2636 (Protocol): The server speaks protocol 2636, so match your game version; cs169627 (Build): The server runs build 169627; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 Royal Family Gaming | Event/Dev|F1 Spawn|Staging|?
The manual route: launch Rust, F1, then client.connect 64.40.8.117:28054. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.