Working its way up from the back of the class: #15,585 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
51/ 100
D
Moving up: up 368 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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.
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 11 Oct. 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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 19:22 UTC17d ago
0
–
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
Where in the world is PimpMyRust QA routines 503871?
You'll find no region listed by PimpMyRust QA routines 503871. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 91.197.6.11:27994.
Is PimpMyRust QA routines 503871 up, and how steady is its uptime?
The server is down: PimpMyRust QA routines 503871 is offline now, with the last sighting 17 days ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 11 October 2026.
What Rust version is PimpMyRust QA routines 503871 on?
Rust network protocol 2634 and build 167398 on Linux is what PimpMyRust QA routines 503871 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does PimpMyRust QA routines 503871 wipe, and how often?
PimpMyRust QA routines 503871 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. 17 days 11 hours have passed since this world was made.
What happens on PimpMyRust QA routines 503871 when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does PimpMyRust QA routines 503871 sit among Rust servers?
In the top 71% of all ranked servers, PimpMyRust QA routines 503871 sits at #15,585 for player hours over the last seven days.
What does the population on PimpMyRust QA routines 503871 look like?
It has been 17 days since PimpMyRust QA routines 503871 was last seen, and it is offline right now.
Tags
What is meant by the tags on PimpMyRust QA routines 503871?
The game's browser takes its cue from the tags PimpMyRust QA routines 503871 has set: gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 Rust Server Score filters and lists feature PimpMyRust QA routines 503871?
These Rust Server Score lists count PimpMyRust QA routines 503871 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 PimpMyRust QA routines 503871?
The name of PimpMyRust QA routines 503871 gives no 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. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on PimpMyRust QA routines 503871?
The game generates the procedural map on PimpMyRust QA routines 503871 at size 1,000 with seed 31695. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join PimpMyRust QA routines 503871?
Enter client.connect 91.197.6.11:27994 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 asmp40,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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 momentum (D); standing is the one to work on (F).