Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
EU · groups of 12+ · 2x · monthly · 255 on average
378 / 380
Quick answers
from the figures on this page
Server facts
Which region is Apex Rust | 2X based in?
No region is published for Apex Rust | 2X. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 212.22.93.43:28024.
How dependable is Apex Rust | 2X, and is it online at the moment?
At this moment, Apex Rust | 2X is offline; the last time it was seen was 41 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Apex Rust | 2X sit?
Rust network protocol 2632 and build 160556 on Windows is what Apex Rust | 2X runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Apex Rust | 2X wipe its map?
The estimate for Apex Rust | 2X's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 71 days 11 hours. Its tags record that it wipes monthly.
Player numbers
What position does Apex Rust | 2X hold in the rankings?
In the top – of all ranked servers, Apex Rust | 2X sits at #15,468 for player hours over the last seven days.
Is Apex Rust | 2X a busy server?
It has been 41 days 16 hours since Apex Rust | 2X was last seen, and it is offline right now.
Tags
What do Apex Rust | 2X's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp30 (Max players): 30 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs160556 (Build): The game build is 160556; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Apex Rust | 2X publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Apex Rust | 2X?
Rust Server Score lists that include Apex Rust | 2X: 2x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Rules and settings
How is Apex Rust | 2X set up, and what rules does it keep?
The name of Apex Rust | 2X points to a 2x gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Apex Rust | 2X uses?
Apex Rust | 2X runs a procedural map, which the game generates.
How to join
How should you connect to Apex Rust | 2X?
Enter client.connect 212.22.93.43:28024 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 asmp30,ptrak,$r?,v2632,^m,gmrust,cs160556,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp30
Max players30 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs160556
BuildThe game build is 160556.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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.
Not enough figures yet to write a report. Check back after a few days on the list.