Online NA 66.51.99.56:28000 checked 9m ago
[US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+
Connect
srv = rust.server("66.51.99.56: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 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 36% of all ranked servers, top 63% in NA, and #434 of the quad servers (top 52%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Sunday 1 November, 21:24 UTC, in 3d 5h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 5h | Sun 1 Nov, 21:24 UTC | wipe |
| 1 | 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 10d 5h | Sun 8 Nov, 21:24 UTC | wipe |
| 3 | 17d 5h | Sun 15 Nov, 21:24 UTC | wipe |
| 4 | 24d 5h | Sun 22 Nov, 21:24 UTC | wipe |
| 5 | 31d 5h | Sun 29 Nov, 21:24 UTC | wipe |
| 6 | 35d 3h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 38d 5h | Sun 6 Dec, 21:24 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 21:24 UTC3d ago | 1 | NaN | running | 0 |
| 1 | Sat 24 Oct, 01:16 UTC5d ago | 1 | NaN | 1.8 days | 0 |
| 2 | Fri 16 Oct, 00:12 UTC13d ago | 1 | halved by day 2 | 8 days | 0 |
| 3 | Sun 11 Oct, 20:40 UTC17d ago | 5 | halved by day 1 | 4.1 days | 1 |
| 4 | Sat 10 Oct, 00:31 UTC19d ago | 1 | NaN | 1.8 days | 0 |
| 5 | Thu 1 Oct, 18:20 UTC FW27d ago | 0 | NaN | 8.3 days | 0 |
| 6 | Mon 21 Sep, 21:54 UTC37d ago | 2 | halved by day 1 | 9.9 days | 0 |
| 7 | Thu 17 Sep, 19:06 UTC41d ago | 1 | halved by day 2 | 4.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())
Map
3000 · seed 1627336182
- map
- Procedural Map
- size
- 3000
- seed
- 1627336182
Server
srv.info()- address
- 66.51.99.56:28000
- region
- NA
- max players
- 100
- group limit
- quad
- wipe schedule
- weekly
- last wipe
- 25 Oct 2026, 21:24 UTC
- hostname
- –
- first seen
- 13 Sep 2026
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 | WARBANDITS.GG 2X |Solo/Duo/Trio/Quad| JUST FULLWIPED | NA · quad · 2x · weekly · 150 on average | 40/200 |
| 1 | [US] Spoonkid Rust - 2x Thursdays | Duo/Trio/Quad | Share BP | NA · quad · 2x · weekly · 37 on average | 2/75 |
| 2 | US Limitless 2x Solo/Duo/Trio/Quad|No BP Wipes|Noob Friendly | NA · quad · 2x · weekly · 2 on average | 0/200 |
| 3 | WARBANDITS.GG 2X Weekly |Solo/Duo/Trio/Quad|Shared BPs| Just Wi | NA · quad · 2x · weekly · 1 on average | 3/100 |
| 4 | Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip | NA · quad · 2x · monthly · 257 on average | 128/150 |
| 5 | US Limitless 2x Monthly Duo/Trio/Quad|No BP Wipes|Noob Friendly | NA · quad · 2x · monthly · 157 on average | 70/200 |
Quick answers
From the figures on this page.
Population data
What position does [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ take in the server rankings?
Ranked #8,085 on seven-day player hours, [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ is #1,171 in North America and in the top 36% of all ranked servers. Its position in the quad group is #434.
How many players does [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ hold at once?
[US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How well does [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ perform?
The 48-hour average is 5 server fps, with a low of 5. The entity count peaked at 46,088, covering buildings, deployables and the rest of the world. A high of 2,844 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+. The protocol has to match before you can join, and Steam does the updating.
How reliable is [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+, and is it up?
The current sample puts [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ online. Count back 3 days 16 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ sit?
The NA tag is what [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ uses to list itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 66.51.99.56:28000 is its address.
Settings and map
What rules and settings are recorded for [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+?
The name carries the figure: [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ runs 2x gather. Up to 4 players may share a group (quad). Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+?
[US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ runs a procedural map of size 3,000 with seed 1627336182, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ wipe, and on what schedule?
The tag sets the prediction: [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Sunday 1 November at 21:24 UTC. A new world was started 3 days 17 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.
On [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.5.
Tags, lists
Which lists on Rust Data hold [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+, and which filters?
On Rust Data, [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+ appears in these lists: Modded Rust servers, 2x Rust servers and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
How should you read the server tags on [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+?
The game's server browser reads these tags from [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts4 (Group limit): The team cap is 4; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; NA (North America): The server browser files it under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into [US] REVIVAL 2X WEEKLY | MAX 4 | SHARED BPS | LOOT+?
In Rust, F1 opens the console: type client.connect 66.51.99.56:28000. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://discord.com/invite/uz6kM6pUqq.