Working its way up from the back of the class: #15,300 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 6,444 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, and #628 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 13:08 UTC, in 12h.
Its weekly schedule tag · low confidence
wipe-day peak0players, last three wipes
Coming wipes
12hThu 29 Oct, 13:08 UTC
7d 18hThu 5 Nov, 19:00 UTCFW
14d 12hThu 12 Nov, 13:08 UTC
21d 12hThu 19 Nov, 13:08 UTC
28d 12hThu 26 Nov, 13:08 UTC
35d 18hThu 3 Dec, 19:00 UTCFW
42d 12hThu 10 Dec, 13:08 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 15 Oct, 13:08 UTC13d 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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe based in?
You'll find no region listed by ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 9.165.124.241:28014.
Is ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe up, and how steady is its uptime?
At this moment, ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is offline; the last time it was seen was 9 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
On what Rust version does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe sit?
Rust network protocol 2634 and build 167781 on Linux is what ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe wipe its map?
Its tag sets the prediction, as the record holds too few of ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe's wipes to confirm its schedule. It is due to wipe next on Thursday 29 October at 13:08 UTC. The world it runs now was created 13 days 11 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe sit among Rust servers?
Over the last seven days, ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe has #15,300 for player hours, in the top 69% of all ranked servers. It comes #628 among servers in the quad group.
What does the population on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe look like?
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe is offline at the moment; the last time it was seen was 9 days 17 hours ago.
Lists and filters
What do ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe's tags stand for?
You'll see ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): Its slot count is 200; ts4 (Group limit): Teams cap out at 4; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon; WA (West Asia): You will find it under West Asia in the browser in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which person or group runs ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
9 other servers we track also use a rust-apex.duckdns.org hostname, so they and ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe most likely share an operator.
Which Rust Server Score filters and lists feature ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
These Rust Server Score lists count ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe among them: 2x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
Which rules does ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe enforce, and what are its settings?
Going by its name, ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe runs 2x gather. You can have up to 4 players in a group (quad). survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe runs a game-generated procedural map at size 4,000, seed 1663376879. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto ME Apex 2x | Solo/Duo/Trio/Quad | Weekly | No BP Wipe?
Enter client.connect 9.165.124.241:28014 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^z,^y,^w,WA,gmrust,cs167781,ts4
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max playersIts slot count is 200.
ts4
Group limitTeams cap out at 4.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
Region
WA
West AsiaYou will find it under West Asia in the browser.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Even marks across the subjects, from F to F.