Working its way up from the back of the class: #15,966 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
16/ 100
F
Lost ground: down 10,976 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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
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.
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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
13 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
WWWWWWW
····WW·
··WF·W·
W······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 5 OctSat 3 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 07:56 UTC23d ago
2
–
running
1
Sat 3 Oct, 09:05 UTC25d ago
2
–
2 days
1
Thu 1 Oct, 19:25 UTCFW26d ago
3
–
1.6 days
1
Thu 1 Oct, 07:59 UTC27d ago
3
–
0.5 days
2
Wed 30 Sep, 05:21 UTC28d ago
3
–
1.1 days
0
Sat 26 Sep, 10:55 UTC32d ago
2
halved by day 1
3.8 days
2
Fri 25 Sep, 10:56 UTC33d ago
2
–
1 days
0
Sun 20 Sep, 12:18 UTC38d ago
2
halved by day 2
4.9 days
1
Sun 20 Sep, 05:17 UTC38d ago
2
–
0.3 days
1
Sat 19 Sep, 15:25 UTC39d ago
2
–
0.6 days
1
Sat 19 Sep, 08:03 UTC39d ago
2
–
0.3 days
0
Fri 18 Sep, 13:03 UTC40d ago
2
–
0.8 days
0
Thu 17 Sep, 16:32 UTC41d ago
2
–
0.9 days
1
Thu 17 Sep, 03:54 UTC41d ago
2
–
0.5 days
0
Wed 16 Sep, 04:32 UTC42d ago
2
–
1 days
0
Tue 15 Sep, 04:47 UTC43d ago
2
–
1 days
1
Mon 14 Sep, 05:33 UTC44d ago
2
–
1 days
2
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
Where in the world is Mad Mappers | KpucTaJl Server Oxide?
No region is published for Mad Mappers | KpucTaJl Server Oxide. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 37.153.157.216:50000.
How dependable is Mad Mappers | KpucTaJl Server Oxide, and is it online at the moment?
At this moment, Mad Mappers | KpucTaJl Server Oxide is offline; the last time it was seen was 23 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is Mad Mappers | KpucTaJl Server Oxide on?
You will find Mad Mappers | KpucTaJl Server Oxide on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does Mad Mappers | KpucTaJl Server Oxide wipe, and how often?
No next wipe can be predicted for Mad Mappers | KpucTaJl Server Oxide, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 23 days 9 hours have passed since this world was made.
What happens on Mad Mappers | KpucTaJl Server Oxide when wipe day arrives?
Recent wipes have peaked at 2 players on average. 0 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
Where does Mad Mappers | KpucTaJl Server Oxide place in the wider field of Rust servers?
In the top 71% of all ranked servers, Mad Mappers | KpucTaJl Server Oxide sits at #15,966 for player hours over the last seven days.
What does the population on Mad Mappers | KpucTaJl Server Oxide look like?
It has been 23 days 9 hours since Mad Mappers | KpucTaJl Server Oxide was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Mad Mappers | KpucTaJl Server Oxide?
The game's browser takes its cue from the tags Mad Mappers | KpucTaJl Server Oxide has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Mad Mappers | KpucTaJl Server Oxide appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Mad Mappers | KpucTaJl Server Oxide 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
What settings and rules apply on Mad Mappers | KpucTaJl Server Oxide?
You will find no gather rate in the name of Mad Mappers | KpucTaJl Server Oxide. The group limit stays at the game's default of 8 players. survival is the mode 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. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Mad Mappers | KpucTaJl Server Oxide uses?
A procedural map, generated by the game, is what Mad Mappers | KpucTaJl Server Oxide runs.
How to join
How do you get onto Mad Mappers | KpucTaJl Server Oxide?
To connect, start Rust, press F1, and type client.connect 37.153.157.216:50000. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmvanilla,cs166652,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 term to build on. Strongest in standing (F); wipes are the one to work on (F).