On the class lists: F (41), with population over 48 hours and no performance mark.
Players now1/ 2000% full
7-day average0peak 4
Rank#4,321top 19%
Last wipe14d agobiweekly schedule
Next wipe6d 22hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
81/ 100
B+
Holds a respectable place: #4,321 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 200 server fps on average.
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
29/ 100
F
Lost ground: down 1,774 places this week. A strong wipe could turn it round.
A term to build on.
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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 19% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
···F···
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h.
The force wipe · high confidence
usual gap13.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 3.5
Coming wipes
6d 22hThu 5 Nov, 19:00 UTCFW
13d 22hThu 12 Nov, 19:08 UTC
27d 22hThu 26 Nov, 19:08 UTC
34d 22hThu 3 Dec, 19:00 UTCFW
41d 22hThu 10 Dec, 19:08 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 4, 47 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 19:08 UTC14d ago
4
–
running
0
Thu 1 Oct, 19:10 UTCFW28d ago
3
halved by day 6
14 days
0
Fri 18 Sep, 02:16 UTC41d ago
4
halved by day 1
13.7 days
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
EU · groups of 100+ · 2x · biweekly · 30 on average
9 / 200
Quick answers
from the figures on this page
Server details
Where in the world is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
No region tag appears for [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits, but the name suggests Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 217.114.180.19:28015 is the address to use.
Is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits up, and how steady is its uptime?
Right now, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is online. According to its reported uptime, the last restart was about 19 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits smooth to play on?
The average over the last 48 hours was 200 server fps, and it never went below 169. Up to 154,485 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 4,824 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits running?
Rust network protocol 2635 and build 168909 on Linux is what [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits reset?
Its tag sets the prediction, as the record holds too few of [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits's wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 14 days 1 hours have passed since this world was made. Its tags say it wipes every two weeks.
What happens on [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits when wipe day arrives?
Recent wipes have peaked at 4 players on average. 47 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 3.5 in the wipes where it did not hold.
Population
Where does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits sit among Rust servers?
Over the last seven days, [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits has #4,321 for player hours, in the top 19% of all ranked servers.
How many players does [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits usually have?
[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits is showing 1 players right now, with 200 slots in total. The seven-day average is 0 players, with a peak of 4. The busiest time in the last 48 hours was 16:00 UTC, with an average of 3 players.
Lists and filters
What do [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits's tags stand for?
The game's browser takes its cue from the tags [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits has set: gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. 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.
Which Rust Server Score filters and lists feature [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
These Rust Server Score lists count [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits 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: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 2x.
Rules and settings
How is [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits set up, and what rules does it keep?
[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. 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. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
[RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs which map?
A procedural map of size 4,900 and seed 1739618184, generated by the game, is what [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto [RU] #1 HMAORUST|Classic +|Rate x2|Events| Team no limits?
Enter client.connect 217.114.180.19: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 asmp200,ptrak,$r?,v2635,^b,^v,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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 performance (A+); population is the one to work on (F).