Summers' loop
Offline EU 91.210.191.183:28015 checked 32d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 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.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 2h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 13d 18h | Thu 12 Nov, 11:30 UTC | its own |
| 27d 18h | Thu 26 Nov, 11:30 UTC | its own |
| 35d 2h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 41d 18h | Thu 10 Dec, 11:30 UTC | its own |
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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Rust4Noobs | Solo only | Softcore 50% Bi-Weekly | No BP Wipe | EU · solo · biweekly · 5 on average | 3 / 100 |
| POLAR - EU Solo Only | Biweekly | No BP Wipes 10/15 15.10 | EU · solo · biweekly · 9 on average | 6 / 125 |
| Rock to Rockets - Solo only Bi-Weekly, no BP wipes. Vanilla. | EU · solo · biweekly · 2 on average | 0 / 50 |
| Rusty Barrel || Solo Only || Bi-Weekly | EU · solo · biweekly · 2 on average | 1 / 100 |
| GALO | PT/EU | SOLO | Vanilla | Biweekly | EU · solo · biweekly · 2 on average | 2 / 100 |
| Rust4Noobs #1 | Solo only | Softcore 50% Monthly | No BP Wipe | EU · solo · monthly · 12 on average | 15 / 100 |
Quick answers
from the figures on this pageWipe data
When does Summers' loop wipe?
The tag sets the prediction: too few of Summers' loop's wipes are on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The world now in play was created 42 days 5 hours ago. Its tags publish a wipe schedule of every two weeks.
On Summers' loop, what happens on wipe day?
The average busiest count over recent wipes is 1 players. 8 hours after the latest wipe the crowd peaked.
Server
What is the hosting location of Summers' loop?
In Europe, according to its EU tag, sits Summers' loop. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 91.210.191.183:28015.
Which Rust version is Summers' loop on?
On Linux, Summers' loop runs Rust network protocol 2633 and build 165217. Joining requires the same protocol on your game; Steam handles the update.
What uptime does Summers' loop show, and is it up?
Last seen 32 days 11 hours ago, Summers' loop now reports offline. Of 168 hours in the last 7 full days, 0 were up: 0%. It entered Rust Server Analytics records on 13 September 2026.
Lists and tags
What do Summers' loop's tags stand for?
Tags from Summers' loop, as read by the game's server browser, are: gmsoftcore (Game mode): Softcore ruleset, the easier one; mp30 (Max players): 30 slots in total; ts1 (Group limit): Teams hold no more than 1; v2633 (Protocol): Joining needs your game on protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^b (Biweekly): A two-week wipe cycle; ^s (Softcore): On softcore, death keeps part of the inventory, per Facepunch's mode; EU (Europe): Europe is the region it appears under in the browser. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does Summers' loop appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists Summers' loop fits are: EU Rust servers: live population data, Community Rust servers, live and Solo Rust servers. It appears on the server list under the following 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.
Population
Where does Summers' loop sit among Rust servers?
Summers' loop holds #16,915 on seven-day player hours and #2,586 in Europe, inside the top 72% of the ranked field. The solo segment places it at #206.
How many players does Summers' loop carry?
No response from Summers' loop at the latest check, with a last sighting 32 days 11 hours ago.
Settings
How is Summers' loop configured, and what rules apply?
No gather rate is given in the name of Summers' loop. It is a solo-only server. It runs softcore, An easier mode from Facepunch, where some loot is retained. Both fighting and raiding between players are allowed. Community is its listing; it is a community server. The server runs with VAC, Valve's anti-cheat, enabled.
The map on Summers' loop: which one is it?
A procedural map of size 4,000 with seed 1047376214, generated by the game, runs on Summers' loop. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Connection
How do you connect to Summers' loop?
In the Rust console (F1), enter client.connect 91.210.191.183:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.