Offline 9.165.140.176:28014 checked 4h ago
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe
Connect
srv = rust.server("9.165.140.176:28017")
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 24 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 68% of all ranked servers, and #611 of the quad servers (top 74%). Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 29 October, 13:08 UTC, in 1h. # Weekly: 7 days after its last wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
4000 · seed 2105665827
- map
- Procedural Map
- size
- 4000
- seed
- 2105665827
Server
srv.info()- address
- 9.165.140.176:28014
- region
- –
- max players
- 200
- group limit
- quad
- wipe schedule
- weekly
- last wipe
- 22 Oct 2026, 13:08 UTC
- hostname
- rust-apex.duckdns.org:28014
- first seen
- 24 Oct 2026
Operator · rust-apex.duckdns.org
rust.servers(operator="rust-apex.duckdns.org").sort_values("players")
11 servers publish a rust-apex.duckdns.org hostname; the busiest are listed.
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 EU 2X |Solo/Duo/Trio/Quad|X2 JUST WIPED | EU · quad · 2x · weekly · 211 on average | 134/200 |
| 1 | WARBANDITS.GG 2X |Solo/Duo/Trio/Quad| JUST FULLWIPED | NA · quad · 2x · weekly · 149 on average | 39/200 |
| 2 | SURVIVORS.GG #6 [ 2x Solo/Duo/Trio/Quad ] FULLWIPED 24.10 | quad · 2x · weekly · 65 on average | 8/200 |
| 3 | [US] Spoonkid Rust - 2x Thursdays | Duo/Trio/Quad | Share BP | NA · quad · 2x · weekly · 37 on average | 2/75 |
| 4 | [EU] SLIMI RUST | 2X | WEEKLY WIPE | PVP | Solo/Duo/Trio/Quad | EU · quad · 2x · weekly · 24 on average | 1/150 |
| 5 | UltimateRust.com - Zombie Land | Squad | x2 | Procedural | 23.1 | quad · 2x · weekly · 20 on average | 16/150 |
Quick answers
From the figures on this page.
Player counts
How does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe compare in the rankings?
Player hours over seven days put ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe at #15,165, in the top 68% of the ranked set. Its position in the quad group is #611.
How many players does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe hold at once?
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe returns no live count at this refresh, having last been seen 4 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
How well does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe perform?
Averaged over 48 hours: 89 server fps, never under 73. Buildings, deployables and all else in the world took the count as high as 94,714 entities. A high of 3,110 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe. Steam updates your game for you, but the protocol must match to join.
How reliable is ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe, and is it online now?
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is offline at this refresh; the last response came 4 hours ago. Count back 5 hours from its reported uptime to get the last restart. 86 of 96 hours up over the last 4 full days, or 90%. Rust Data logged it first on 24 October 2026.
Which location does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe run from?
For ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 9.165.140.176:28014.
Settings and map
What rules and settings are recorded for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
2x gather is what the name states, and the name is ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe. 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. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe loaded?
The game generates the map on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe: procedural, size 4,000, seed 2105665827. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe wipe, and on what schedule?
The next wipe for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is an estimate, drawn from weekly: 7 days after its last wipe. Thursday 29 October at 13:08 UTC is when the next wipe is due. A new world was started 6 days 22 hours ago, and that is the one in play. Its tags carry a weekly wipe schedule.
Tags and filters
Which Rust Data filters and lists contain ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
These Rust Data lists include ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Who operates ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
The same operator most likely runs ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe and 10 other servers we track, as all publish a rust-apex.duckdns.org hostname.
Which meanings do the tags on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe hold?
The game's server browser reads these tags from ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): 200 slots in total; ts4 (Group limit): The team cap is 4; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon; WA (West Asia): West Asia is its listing in the server browser. 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
How can I connect to ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
In Rust, F1 opens the console: type client.connect 9.165.140.176:28014. Launch Rust on this page does the same by opening the game through Steam and connecting.
