On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,349top 69%
Last wipe110d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,349 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
97/ 100
A+
Runs smoothly: 58 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 176 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
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 5 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. Ranked on player hours over the last seven days.
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
ZapX Rust Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 134.255.217.101:28015.
How dependable is ZapX Rust Server, and is it online at the moment?
Right now, ZapX Rust Server is online. According to its reported uptime, the last restart was about 2 days 1 hours ago. It was up 85% of the time over the last 7 full days, 143 of 168 hours. On 5 October 2026, Rust Server Score saw it for the first time.
Does ZapX Rust Server perform well?
The average over the last 48 hours was 58 server fps, and it never went below 29. At its peak, it held 68,713 entities, including buildings, deployables and all else in the world. At its highest, it used 2,169 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does ZapX Rust Server sit?
You will find ZapX Rust Server on Rust network protocol 2631 and build 156812, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does ZapX Rust Server wipe, and how often?
ZapX Rust Server has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 110 days 12 hours.
Population
Where does ZapX Rust Server sit among Rust servers?
Over the last seven days, ZapX Rust Server has #15,349 for player hours, in the top 69% of all ranked servers.
How many players does ZapX Rust Server usually have?
ZapX Rust Server is showing 0 players right now, with 50 slots in total. For the last seven days, the average number of players was 0.
Tags and filters
What do ZapX Rust Server's tags stand for?
You'll see ZapX Rust Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2631 (Protocol): Join only if your game runs protocol 2631; cs156812 (Build): The game build is 156812; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded 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 lists and filters on Rust Server Score show ZapX Rust Server?
These Rust Server Score lists count ZapX Rust Server among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does ZapX Rust Server enforce, and what are its settings?
You will find no gather rate in the name of ZapX Rust Server. 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. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
ZapX Rust Server runs which map?
The game generates the procedural map on ZapX Rust Server at size 3,500 with seed 12345. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to ZapX Rust Server?
To connect, start Rust, press F1, and type client.connect 134.255.217.101:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2631
ProtocolJoin only if your game runs protocol 2631.
cs156812
BuildThe game build is 156812.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).