Working its way up from the back of the class: #13,881 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
39/ 100
F
Slipped a little: down 2,987 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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 60% 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
In what location does Mad Mappers | KpucTaJl Staging sit?
Mad Mappers | KpucTaJl Staging leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 37.153.157.216:45000.
How dependable is Mad Mappers | KpucTaJl Staging, and is it online at the moment?
At this moment, Mad Mappers | KpucTaJl Staging is offline; the last time it was seen was 27 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 1 October 2026.
On what Rust version does Mad Mappers | KpucTaJl Staging sit?
Rust network protocol 2634 and build 166493 on Windows is what Mad Mappers | KpucTaJl Staging runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Mad Mappers | KpucTaJl Staging wipe, and how often?
The record holds too few of Mad Mappers | KpucTaJl Staging's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 27 days 12 hours have passed since this world was made.
Population
Where does Mad Mappers | KpucTaJl Staging place in the wider field of Rust servers?
In the top 60% of all ranked servers, Mad Mappers | KpucTaJl Staging sits at #13,881 for player hours over the last seven days.
How many players does Mad Mappers | KpucTaJl Staging usually have?
It has been 27 days 9 hours since Mad Mappers | KpucTaJl Staging was last seen, and it is offline right now.
Tags
What do Mad Mappers | KpucTaJl Staging's tags stand for?
You'll see Mad Mappers | KpucTaJl Staging tagged with gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166493 (Build): This runs on build 166493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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 Mad Mappers | KpucTaJl Staging appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Mad Mappers | KpucTaJl Staging: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Mad Mappers | KpucTaJl Staging set up, and what rules does it keep?
Nothing in the name of Mad Mappers | KpucTaJl Staging states a gather rate. 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. 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. You are not covered by VAC, Valve's anti-cheat.
Mad Mappers | KpucTaJl Staging runs which map?
The game generates a procedural map for Mad Mappers | KpucTaJl Staging.
How to join
What is the way to join Mad Mappers | KpucTaJl Staging?
Enter client.connect 37.153.157.216:45000 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?,v2634,gmvanilla,cs166493,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166493
BuildThis runs on build 166493.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 term to build on. Even marks across the subjects, from F to F.