On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,353top 69%
Last wipe16d 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,353 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 200 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 228 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 20 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
You'll find no region listed by MX Rust Server Pituka. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 189.179.91.237:28015.
How reliable is MX Rust Server Pituka, and is it up?
You can join now: MX Rust Server Pituka is online. The uptime it reports puts the last restart at about 5 days 5 hours ago. It was up 143 of 168 hours over the last 7 full days, which is 85% of the time. On 20 October 2026, Rust Server Score saw it for the first time.
Does MX Rust Server Pituka perform well?
The average over the last 48 hours was 200 server fps, and it never went below 155. Buildings, deployables and everything else in the world added up to as many as 54,496 entities. Up to 2,488 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does MX Rust Server Pituka sit?
Rust network protocol 2635 and build 168909 on Linux is what MX Rust Server Pituka runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does MX Rust Server Pituka reset?
MX Rust Server Pituka has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 16 days 3 hours.
Player count
Where does MX Rust Server Pituka place in the wider field of Rust servers?
In the top 69% of all ranked servers, MX Rust Server Pituka sits at #15,353 for player hours over the last seven days.
How many players does MX Rust Server Pituka usually have?
With 50 slots available, MX Rust Server Pituka currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
What is meant by the tags on MX Rust Server Pituka?
gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags MX Rust Server Pituka publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does MX Rust Server Pituka appear in the Rust Server Score lists and filters?
Rust Server Score lists that include MX Rust Server Pituka: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does MX Rust Server Pituka enforce, and what are its settings?
The name of MX Rust Server Pituka gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
MX Rust Server Pituka runs which map?
The game generates the procedural map on MX Rust Server Pituka at size 3,000 with seed 591144989. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto MX Rust Server Pituka?
Enter client.connect 189.179.91.237:28015 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 asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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).