On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average0peak 1
Rank#8,666top 39%
Last wipe4h agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
49/ 100
D
Room for more players: 0 of 1 on average.
Standingrank on player hours
61/ 100
C
Working its way up from the back of the class: #8,666 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
42/ 100
F
Slipped a little: down 1,325 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in wipe hold (A+); uptime 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.
AveragePeakWipe
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 39% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WWWW
··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 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Wed 21 OctSun 18 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 15:43 UTC4h ago
–
–
running
1
Wed 21 Oct, 17:00 UTC6d ago
1
–
–
1
Sun 18 Oct, 12:36 UTC9d ago
1
–
3.2 days
1
Sat 17 Oct, 16:36 UTC10d ago
1
–
0.8 days
1
Fri 16 Oct, 10:16 UTC11d ago
1
–
1.3 days
1
Thu 15 Oct, 18:19 UTC12d ago
1
–
0.7 days
0
Thu 15 Oct, 08:02 UTC12d ago
1
–
0.4 days
1
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
The name of PL | PinkLoving Vanilla points to Europe, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 178.75.29.10:28015.
How reliable is PL | PinkLoving Vanilla, and is it up?
You cannot join now: PL | PinkLoving Vanilla is offline, last seen 2 hours ago. For the last 7 full days, it was up 11 of 168 hours, or 7% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
On what Rust version does PL | PinkLoving Vanilla sit?
The server PL | PinkLoving Vanilla is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does PL | PinkLoving Vanilla wipe its map?
There is no next wipe to predict on PL | PinkLoving Vanilla, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 4 hours.
What should you expect from wipe day on PL | PinkLoving Vanilla?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Population
Where does PL | PinkLoving Vanilla sit among Rust servers?
Over the last seven days, PL | PinkLoving Vanilla has #8,666 for player hours, in the top 39% of all ranked servers.
Is PL | PinkLoving Vanilla a busy server?
The last sighting of PL | PinkLoving Vanilla was 2 hours ago, and it is offline right now. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 17:00 UTC, averaging 0 players.
Tags and filters
How should you read the tags on PL | PinkLoving Vanilla?
You'll see PL | PinkLoving Vanilla tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; 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): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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 PL | PinkLoving Vanilla?
Rust Server Score lists that include PL | PinkLoving Vanilla: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Server rules
Which rules does PL | PinkLoving Vanilla enforce, and what are its settings?
You will find no gather rate in the name of PL | PinkLoving Vanilla. 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. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map PL | PinkLoving Vanilla uses?
PL | PinkLoving Vanilla runs a procedural map, which the game generates.
Getting in
What is the way to join PL | PinkLoving Vanilla?
Enter client.connect 178.75.29.10: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 asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
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
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. Strongest in wipe hold (A+); uptime is the one to work on (F).