Working its way up from the back of the class: #16,915 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
37/ 100
F
Slipped a little: down 4,318 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.
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.
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 72% of all ranked servers, top 87% in EU, and #206 of the solo servers (top 92%). 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
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 5hThu 5 Nov, 19:00 UTCFW
13d 21hThu 12 Nov, 11:30 UTC
27d 21hThu 26 Nov, 11:30 UTC
35d 5hThu 3 Dec, 19:00 UTCFW
41d 21hThu 10 Dec, 11:30 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 17 Sep, 11:30 UTC42d ago
1
–
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
In Europe, according to its own listing, sits Summers' loop, with the EU tag. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 91.210.191.183:28015.
Is Summers' loop up, and how steady is its uptime?
You cannot join now: Summers' loop is offline, last seen 32 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is Summers' loop running?
Rust network protocol 2633 and build 165217 on Linux is what Summers' loop runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Summers' loop reset?
The prediction follows its tag, because too few of Summers' loop's wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 42 days 2 hours. Its tags say it wipes every two weeks.
What should you expect from wipe day on Summers' loop?
The average peak on its recent wipes was 1 players. 8 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Summers' loop sit among Rust servers?
Over the last seven days, Summers' loop has #16,915 for player hours, in the top 72% of all ranked servers and #2,586 in Europe. It comes #206 among servers in the solo group.
What does the population on Summers' loop look like?
The last sighting of Summers' loop was 32 days 8 hours ago, and it is offline right now.
Tags
What do Summers' loop's tags stand for?
You'll see Summers' loop tagged with gmsoftcore (Game mode): An easier ruleset, softcore; mp30 (Max players): The server holds 30 slots; ts1 (Group limit): No team may go above 1; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^s (Softcore): You keep some inventory when you die, as Facepunch's easier mode allows; EU (Europe): You will find it under Europe in the browser 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 Summers' loop appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Summers' loop among them: European Rust servers, graded, Best community servers, graded and Solo Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Game mode: Softcore; Server tag: Biweekly ^b and Softcore ^s; Group limit: Solo; Wipe schedule: Every two weeks.
Server rules
What settings and rules apply on Summers' loop?
You will find no gather rate in the name of Summers' loop. This is a solo-only server, so teams cannot form. You get softcore here, Facepunch's easier setting, with part of your loot kept. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Summers' loop runs which map?
The game generates the procedural map on Summers' loop at size 4,000 with seed 1047376214. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Summers' loop?
To connect, start Rust, press F1, and type client.connect 91.210.191.183:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2633,^b,^s,EU,gmsoftcore,cs165217,ts1
Game
gmsoftcore
Game modeAn easier ruleset, softcore.
mp30
Max playersThe server holds 30 slots.
ts1
Group limitNo team may go above 1.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^s
SoftcoreYou keep some inventory when you die, as Facepunch's easier mode allows.
Region
EU
EuropeYou will find it under Europe in the browser.
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.