Online 165.217.129.49:9105 checked 10m ago
BIGRUST 2X
Connect
srv = rust.server("165.217.129.49:9108")
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 Oct. 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW 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 | Mon 19 Oct, 16:10 UTC10d ago | 1 | NaN | running | 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
2100 · seed 45643
- map
- Procedural Map
- size
- 2100
- seed
- 45643
Server
srv.info()- address
- 165.217.129.49:9105
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 19 Oct 2026, 17:14 UTC
- hostname
- –
- first seen
- 17 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 838 on average | 788/850 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 614 on average | 1200/1200 |
| 2 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 378 on average | 152/200 |
| 3 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 348 on average | 799/845 |
| 4 | Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 299 on average | 1123/1150 |
| 5 | EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 282 on average | 345/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does BIGRUST 2X rank?
Over the last seven days BIGRUST 2X sits at #15,327 on player hours, in the top 69% of ranked servers.
How full does BIGRUST 2X run?
Current row: 0 players on BIGRUST 2X, against 40 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on BIGRUST 2X?
The 48-hour average is 236 server fps, with a low of 213. Buildings, deployables and all else in the world took the count as high as 21,275 entities. A high of 2,438 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does BIGRUST 2X run?
Version Rust network protocol 2634 and build 167781 on Linux is reported by BIGRUST 2X. Steam updates your game for you, but the protocol must match to join.
How reliable is BIGRUST 2X, and is it up?
Online is the state at the latest refresh for BIGRUST 2X. The uptime it reports puts the last restart about 9 days 22 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 17 October 2026.
Which location does BIGRUST 2X run from?
There is no region published for BIGRUST 2X. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 165.217.129.49:9105 is its address.
Settings and map
What rules and settings are recorded for BIGRUST 2X?
Gather sits at 2x, read from the server's own name: BIGRUST 2X. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.
What is the map on BIGRUST 2X?
Size 2,100, seed 45643: the procedural map on BIGRUST 2X, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does BIGRUST 2X wipe, and how often?
The only wipe BIGRUST 2X takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 10 days ago. A monthly wipe schedule is published in its tags.
What is wipe day on BIGRUST 2X like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does BIGRUST 2X appear among Rust Data lists and filters?
On Rust Data, BIGRUST 2X appears in these lists: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks; Gather rate: 2x.
How should you read the server tags on BIGRUST 2X?
Read by the game's server browser, the tags BIGRUST 2X publishes are: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into BIGRUST 2X?
Enter client.connect 165.217.129.49:9105 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.