On the class lists: C (62), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 1
Rank#8,351top 38%
Last wipe26d agono schedule published
Next wipe8d 14hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
62/ 100
C
Working its way up from the back of the class: #8,351 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 95 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
88/ 100
A−
Climbing fast: up 6,330 places this week.
A steady term.
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.
AveragePeakWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 14h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
8d 14hThu 5 Nov, 19:00 UTCFW
36d 14hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 29 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 21:14 UTCFW26d ago
1
–
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
No region is published for Zomsaba_RUST3. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 162.43.37.59:28015.
How dependable is Zomsaba_RUST3, and is it online at the moment?
Right now, Zomsaba_RUST3 is online. According to its reported uptime, the last restart was about 6 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Zomsaba_RUST3 run?
It averaged 95 server fps over the last 48 hours, with a low of 61. Up to 94,034 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 2,747 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Zomsaba_RUST3 sit?
You will find Zomsaba_RUST3 on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Zomsaba_RUST3 reset?
Zomsaba_RUST3 wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 26 days 7 hours have passed since this world was made.
What should you expect from wipe day on Zomsaba_RUST3?
Recent wipes have peaked at 1 players on average. 29 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Zomsaba_RUST3 sit among Rust servers?
Over the last seven days, Zomsaba_RUST3 has #8,351 for player hours, in the top 38% of all ranked servers.
How many players does Zomsaba_RUST3 usually have?
With 20 slots available, Zomsaba_RUST3 currently has 0 players. The seven-day average is 0 players, with a peak of 1. The highest average in the last 48 hours came at 10:00 UTC, with 1 players.
Tags
What is meant by the tags on Zomsaba_RUST3?
gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Zomsaba_RUST3 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 lists and filters on Rust Server Score show Zomsaba_RUST3?
These Rust Server Score lists count Zomsaba_RUST3 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does Zomsaba_RUST3 enforce, and what are its settings?
You will find no gather rate in the name of Zomsaba_RUST3. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Zomsaba_RUST3 runs which map?
Zomsaba_RUST3 runs a game-generated procedural map at size 4,000, seed 19686. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join Zomsaba_RUST3?
To connect, start Rust, press F1, and type client.connect 162.43.37.59:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 steady term. Strongest in performance (A+); population is the one to work on (F).