Online NA 91.229.114.207:28019 checked 14m ago
DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep
Connect
srv = rust.server("91.229.114.207:28021")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 bestTop 11% of all ranked servers, top 22% in NA, and #148 of the quad servers (top 18%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 17:02 UTC, in 2d 8h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 2d 8h | Sat 31 Oct, 17:02 UTC | wipe |
| 1 | 7d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 16d 8h | Sat 14 Nov, 17:02 UTC | wipe |
| 3 | 30d 8h | Sat 28 Nov, 17:02 UTC | wipe |
| 4 | 35d 10h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 44d 8h | Sat 12 Dec, 17:02 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 7, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 17:02 UTC11d ago | 7 | NaN | running | 1 |
| 1 | Thu 1 Oct, 17:36 UTC FW27d ago | 9 | halved by day 11 | 16 days | 3 |
| 2 | Thu 1 Oct, 11:19 UTC27d ago | 9 | NaN | 0.3 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
3800 · seed 129394987
- map
- Custom Map
- size
- 3800
- seed
- 129394987
- custom map
- download
Server
srv.info()- address
- 91.229.114.207:28019
- region
- NA
- max players
- 200
- group limit
- quad
- wipe schedule
- biweekly
- last wipe
- 17 Oct 2026, 17:02 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 | AceRust.com 2x Solo/Duo | 50% Upkeep | Shared BPs | NA · quad · 2x · biweekly · 2 on average | 2/150 |
| 1 | The Green 2.0 | 2x, 1/4 Upkeep | Free Minis | Weather | No BP W | NA · quad · 2x · biweekly · 4 on average | 3/50 |
| 2 | Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip | NA · quad · 2x · monthly · 253 on average | 107/125 |
| 3 | US Limitless 2x Monthly Duo/Trio/Quad|No BP Wipes|Noob Friendly | NA · quad · 2x · monthly · 153 on average | 122/200 |
| 4 | WARBANDITS.GG 2X |Solo/Duo/Trio/Quad| JUST FULLWIPED | NA · quad · 2x · weekly · 149 on average | 39/200 |
| 5 | [US] Spoonkid Rust - 2x Thursdays | Duo/Trio/Quad | Share BP | NA · quad · 2x · weekly · 37 on average | 1/75 |
Quick answers
From the figures on this page.
Population data
What position does DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep take in the server rankings?
Ranked #2,534 on seven-day player hours, DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep is #411 in North America and in the top 11% of all ranked servers. The quad group places it at #148.
How full does DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep run?
Current row: 0 players on DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep, against 200 slots. Over the last seven days it averaged 2 players and peaked at 7. Peak hour in the last 48 hours: 00:00 UTC, mean 4 players.
About the server
How well does DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep perform?
Server fps over the last 48 hours averages 116; the floor is 97. Entity numbers reached 86,009, and that includes buildings, deployables and the rest. A high of 3,319 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep. Steam updates your game for you, but the protocol must match to join.
Is DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep up, and what does its uptime show?
The current sample puts DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep online. The uptime it reports puts the last restart about 19 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
In which location is DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep hosted?
In North America, DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep lists itself, using the NA tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.229.114.207:28019 is its address.
Settings and map
What rules and settings are recorded for DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep?
2x gather is what the name states, and the name is DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep. The group limit is 4 players, the quad setting. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Joining requires Rust's premium status. Anti-cheat status: VAC on.
What is the map on DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep?
Map size 3,800, custom, on DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep. Download the published file from this page.
Wipes and dates
When does DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep wipe, and on what schedule?
Too few wipes are on record for DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep to confirm its schedule, so the tag drives the prediction. Saturday 31 October at 17:02 UTC is when the next wipe is due. The world it runs now was generated 11 days 15 hours ago. The tags list a two-weekly wipe cycle.
On DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep, what happens on wipe day?
Recent wipes averaged 8 players at their peak. Peak population on the latest wipe came 2 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 11.
Tags, lists
Which lists on Rust Data hold DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep, and which filters?
These Rust Data lists include DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep: Modded Rust servers, 2x Rust servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Modded; Game mode: Premium; Server tag: Biweekly ^b, Premium ^q, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Which meanings do the tags on DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep hold?
The game's server browser reads these tags from DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep: gmrust (Game mode): Rust survival in its standard form; mp200 (Max players): Slot count: 200; ts4 (Group limit): The team cap is 4; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; ^q (Premium): Joining requires Rust's premium status; NA (North America): The server browser files it under North America; rustmaps (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into DadCore US Bi-Weekly-ish Main | 2x | Quad | 50% Upkeep?
In Rust, F1 opens the console: type client.connect 91.229.114.207:28019. Launch Rust on this page does the same by opening the game through Steam and connecting. Joining requires Rust's premium status. https://www.dadcorerust.com/ is the website recorded for it.