On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 6
Rank#3,077top 14% · #1162 in EU
Last wipe28d agomonthly schedule
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,077 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: 112 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
43/ 100
F
Slipped a little: down 423 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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 14% of all ranked servers, top 40% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·····W·
·······
·······
··WW·
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 gap9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak6players, last three wipes
crowd held50%else halves by day 4
The first 48 hours of its last wipes
Sat 10 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 8, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 10:14 UTC17h ago
–
–
running
1
Wed 28 Oct, 21:07 UTC1d ago
–
–
–
2
Sat 10 Oct, 18:02 UTC19d ago
8
halved by day 4
18.1 days
4
Thu 1 Oct, 18:06 UTCFW28d ago
4
✓ held half
9 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
EU · groups of 300+ · 2x · monthly · 141 on average
19 / 500
Quick answers
from the figures on this page
Server details
In what location does RUST - PAIN | X2 | NO LIMIT sit?
You'll see RUST - PAIN | X2 | NO LIMIT listed in Europe, tagged EU. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 87.252.252.228:28015.
Is RUST - PAIN | X2 | NO LIMIT up, and how steady is its uptime?
You can join now: RUST - PAIN | X2 | NO LIMIT is online. The uptime it reports puts the last restart at about 2 hours ago. It was up 166 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does RUST - PAIN | X2 | NO LIMIT run?
It never fell below 71 server fps in the last 48 hours, averaging 112. Up to 131,824 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,567 MB of memory. Players feel lag when fps drops and entities pile up.
Which Rust version is RUST - PAIN | X2 | NO LIMIT running?
Rust network protocol 2635 and build 168909 on Windows is what RUST - PAIN | X2 | NO LIMIT runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does RUST - PAIN | X2 | NO LIMIT wipe its map?
RUST - PAIN | X2 | NO LIMIT wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 28 days 4 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What happens on RUST - PAIN | X2 | NO LIMIT when wipe day arrives?
The average peak on its recent wipes was 6 players. 14 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 50% of its recent wipes. In the other wipes it slipped under half by day 4.
Player count
Where does RUST - PAIN | X2 | NO LIMIT place in the wider field of Rust servers?
In Europe, RUST - PAIN | X2 | NO LIMIT is #1,162, and overall it is #3,077 on player hours over the last seven days, in the top 14% of all ranked servers.
How many players does RUST - PAIN | X2 | NO LIMIT usually have?
RUST - PAIN | X2 | NO LIMIT is showing 0 players right now, with 100 slots in total. Averaging 1 players over seven days, it peaked at 6. The highest average in the last 48 hours came at 12:00 UTC, with 1 players.
Tags
How should you read the tags on RUST - PAIN | X2 | NO LIMIT?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): In the server browser it appears under Europe are the tags RUST - PAIN | X2 | NO LIMIT publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature RUST - PAIN | X2 | NO LIMIT?
These Rust Server Score lists count RUST - PAIN | X2 | NO LIMIT among them: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Map and rules
How is RUST - PAIN | X2 | NO LIMIT set up, and what rules does it keep?
Going by its name, RUST - PAIN | X2 | NO LIMIT runs 2x gather. The default of 8 players applies as the group cap. survival is the mode 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. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
RUST - PAIN | X2 | NO LIMIT runs which map?
A procedural map of size 4,500 and seed 1337, generated by the game, is what RUST - PAIN | X2 | NO LIMIT runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Getting in
How should you connect to RUST - PAIN | X2 | NO LIMIT?
Enter client.connect 87.252.252.228:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://rim.gamestores.app/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^m,^v,EU,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EU
EuropeIn the server browser it appears under Europe.
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).