ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe
Offline 87.109.150.119:28014 checked 29d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers, and #614 of the quad servers (top 75%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 22 October, 13:09 UTC, in 4d 3h. Its weekly schedule tag · low confidence
Coming wipes
- 4d 3hThu 22 Oct, 13:09 UTC
- 11d 3hThu 29 Oct, 13:09 UTC
- 18d 9hThu 5 Nov, 19:00 UTCFW
- 25d 3hThu 12 Nov, 13:09 UTC
- 32d 3hThu 19 Nov, 13:09 UTC
- 39d 3hThu 26 Nov, 13:09 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 17 Sep, 13:09 UTC30d ago | 0 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 127/ 200
- 61/ 200
- 156/ 200
- 15/ 75
- 13/ 100
- 33/ 150
Quick answers
Tags and listings
Where does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe are: 2x Rust servers and Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Weekly; Gather rate: 2x.
Who operates ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
The rust-apex.duckdns.org hostname from ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe also appears on 7 other servers we track, suggesting a common operator.
What's the meaning of the tags on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
The server browser shows these tags for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe: gmrust (Game mode): Survival, as standard Rust does it; mp200 (Max players): The slot count is 200; ts4 (Group limit): The team limit is 4; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs164530 (Build): This server runs build 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^w (Weekly): Weekly wipes; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): This server relies on Carbon for plugins; WA (West Asia): In the server browser it appears under West Asia. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
Where can you find ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 87.109.150.119:28014.
What's the uptime like for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Right now ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is offline, having last been seen 29 days 12 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 13 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
The version on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is Rust network protocol 2633 and build 164530, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
How often does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe wipe?
With too few wipes recorded for ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe to confirm the schedule, the prediction goes by its tag. Expect the next wipe on Thursday 22 October at 13:09 UTC. The world you are on now was created 30 days 20 hours. Its tags carry a wipe schedule that runs weekly.
What happens on wipe day at ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Across its recent wipes, the average busiest point drew 0 players. On the latest wipe, 0 hours passed before the crowd peaked.
Map and rules
What settings and rules have been applied to ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Gather rates here are 2x, as ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe announces in its name. A group can have at most 4 players (quad). It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Carbon plugins are running here. The server runs Valve's anti-cheat, VAC.
Which map is active on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
A game-generated procedural map of size 4,000 with seed 2053839577 is in play on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Population
How many players are on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Right now ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is offline, with its last appearance 29 days 12 hours ago.
Where does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe sit in the rankings?
Over the last seven days, ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is #15,490 by player hours, among the top 70% of all ranked servers. It ranks #614 among quad servers.
Getting in
What's the process to join ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 87.109.150.119:28014.
