Online NA 66.51.96.91:28000 checked 10m ago
[US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}
Connect
srv = rust.server("66.51.96.91:28001")
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 5 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 best
Top 66% of all ranked servers, top 78% in NA. 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 6d 10h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 10h | 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 3, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 21 Oct, 23:43 UTC8d ago | 3 | NaN | running | 0 |
| 1 | Mon 12 Oct, 21:53 UTC17d ago | 4 | halved by day 3 | 9.1 days | 2 |
| 2 | Mon 5 Oct, 21:21 UTC24d ago | 1 | halved by day 1 | 7 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())
Map
3500 · seed 471471404
- map
- Procedural Map
- size
- 3500
- seed
- 471471404
Server
srv.info()- address
- 66.51.96.91:28000
- region
- NA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 21 Oct 2026, 23:43 UTC
- hostname
- –
- first seen
- 5 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 - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 337 on average | 84/100 |
| 1 | US Limitless 2x Monthly Main | No BP Wipes | x2 | NA · groups of 12+ · 2x · monthly · 149 on average | 68/200 |
| 2 | [US] Spoonkid Rust - 2x Monthly | 8 MAX | No BP Wipes | NA · groups of 8+ · 2x · monthly · 8 on average | 6/67 |
| 3 | US Limitless 2x Monthly No Offlines|No BP Wipes|Noob Friendly | NA · groups of 12+ · 2x · monthly · 8 on average | 3/200 |
| 4 | [US] Ember Rust 2x Monthly | SOLO ONLY | No BP Wipes | NA · groups of 8+ · 2x · monthly · 5 on average | 1/200 |
| 5 | Exile.gg | US 2x Monthly | 12 Max | NA · groups of 12+ · 2x · monthly · 5 on average | 1/50 |
Quick answers
From the figures on this page.
Population
What position does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} take in the server rankings?
Player hours over the last seven days: #14,628 for [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}, #1,450 in North America, within the top 66% of the ranked set.
How many players does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} hold at once?
Current row: 0 players on [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}, against 100 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How well does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} perform?
The 48-hour average is 5 server fps, with a low of 5. Buildings, deployables and all else in the world took the count as high as 65,336 entities. A high of 2,301 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}?
Version Rust network protocol 2635 and build 168909 on Linux is reported by [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}, and is it up?
The current sample puts [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} online. Count back 18 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 5 October 2026.
Where does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} sit?
In North America, [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} lists itself, using the NA tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 66.51.96.91:28000.
Rules, settings, map
Which settings and rules does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} run?
The name carries the figure: [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} runs 2x gather. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} loaded?
[US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} runs a procedural map of size 3,500 with seed 471471404, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} wipe?
A single wipe each month, the force wipe, is all [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 8 days 8 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
On [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}, what happens on wipe day?
Recent wipes averaged 3 players at their peak. Peak population on the latest wipe came 1 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, lists
Where does [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} appear among Rust Data lists and filters?
These Rust Data lists include [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}: Modded Rust servers, 2x Rust servers and North America Rust servers. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Which meanings do the tags on [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} hold?
These tags are published by [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly} and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): North America is its listing in the server browser; sc1 (Custom tag): A plugin or the owner added this; standard Rust does not define it. 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
How can I connect to [US East] --- UNLISTED CREW | BLACKSITE 2X --- {BiWeekly}?
In Rust, F1 opens the console: type client.connect 66.51.96.91:28000. Launch Rust on this page does the same by opening the game through Steam and connecting.