Rust Data

rustdata.spaceservers91.210.191.183:28017.ipynb

Run all rust-data · live

‹ All servers

Offline EU 91.210.191.183:28015 checked 31d ago

Summers' loop

solo biweekly wipes softcore

Connect

srv = rust.server("91.210.191.183:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak –
rank #16,915 # top 72% · #2586 in EU
last wipe 41d ago # biweekly schedule
next wipe 9h # Thu 29 Oct, 11:30 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep23 Sep26 Sep28 Sep1 Oct4 Oct

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.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 29 October, 11:30 UTC, in 9h. # Its biweekly schedule tag · low confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
09hThu 29 Oct, 11:30 UTCwipe
17d 16hThu 5 Nov, 19:00 UTCFW force wipe
214d 9hThu 12 Nov, 11:30 UTCwipe
328d 9hThu 26 Nov, 11:30 UTCwipe
435d 16hThu 3 Dec, 19:00 UTCFW force wipe
542d 9hThu 10 Dec, 11:30 UTCwipe

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 8 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 17 Sep, 11:30 UTC41d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4000 · seed 1047376214
Map of Summers' loop
map
Procedural Map
size
4000
seed
1047376214
Open on RustMaps

Server

srv.info()
address
91.210.191.183:28015
region
EU
max players
30
group limit
solo
wipe schedule
biweekly
last wipe
17 Sep 2026, 11:30 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Adults only. Server is PvE oriented. PvP (including killing sleepers), base raiding, fighting, bullying, griefing strictly prohibited. Global chat is english only. Report any abuse with F7.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rust4Noobs | Solo only | Softcore 50% Bi-Weekly | No BP WipeEU · solo · biweekly · 6 on average2/100
1POLAR - EU Solo Only | Biweekly | No BP Wipes 10/15 15.10EU · solo · biweekly · 10 on average1/125
2Rock to Rockets - Solo only Bi-Weekly, no BP wipes. Vanilla.EU · solo · biweekly · 2 on average0/50
3Rusty Barrel || Solo Only || Bi-WeeklyEU · solo · biweekly · 2 on average0/100
4GALO | PT/EU | SOLO | Vanilla | BiweeklyEU · solo · biweekly · 2 on average1/100
5Rust4Noobs #1 | Solo only | Softcore 50% Monthly | No BP WipeEU · solo · monthly · 12 on average3/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Summers' loop rank?

Player hours over the last seven days: #16,915 for Summers' loop, #2,586 in Europe, within the top 72% of the ranked set. Its position in the solo group is #206.

How full does Summers' loop run?

The current row shows Summers' loop offline; the last response was 31 days 21 hours ago.

Server facts

Which Rust version is Summers' loop on?

Rust network protocol 2633 and build 165217 on Linux is what Summers' loop runs. Steam updates your game for you, but the protocol must match to join.

Is Summers' loop up, and what does its uptime show?

Summers' loop is offline at this refresh; the last response came 31 days 21 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does Summers' loop run from?

With its EU tag, Summers' loop lists itself in Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.210.191.183:28015 is its address.

Settings and map

Which settings and rules does Summers' loop run?

The name Summers' loop carries no gather rate. No teams here: solo only. softcore is the game mode here, and Facepunch's lighter mode, with partial loot kept. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has Summers' loop selected?

The game generates the map on Summers' loop: procedural, size 4,000, seed 1047376214. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does Summers' loop wipe?

Too few wipes are on record for Summers' loop to confirm its schedule, so the tag drives the prediction. Thursday 29 October at 11:30 UTC is when the next wipe is due. A new world was started 41 days 14 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.

On Summers' loop, what happens on wipe day?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 8 hours after it began.

Tags and filters

Which lists on Rust Data hold Summers' loop, and which filters?

The Rust Data lists that Summers' loop fits are: EU Rust servers, Rust community servers, unfiltered and Solo Rust servers, group limit 1. These filters bring it up on the server list: 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.

Which meanings do the tags on Summers' loop hold?

The game's server browser reads these tags from Summers' loop: gmsoftcore (Game mode): Softcore ruleset, the easier one; mp30 (Max players): The server lists 30 slots; ts1 (Group limit): No team may exceed 1; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^s (Softcore): Softcore: death costs you only part of your inventory; EU (Europe): Europe is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join Summers' loop?

The manual route: launch Rust, F1, then client.connect 91.210.191.183:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2633,^b,^s,EU,gmsoftcore,cs165217,ts1

Game

gmsoftcore
Game mode Softcore ruleset, the easier one.
mp30
Max players The server lists 30 slots.
ts1
Group limit No team may exceed 1.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs165217
Build Recorded game build: 165217.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

^s
Softcore Softcore: death costs you only part of your inventory.

Region

EU
Europe Europe is its listing in the server 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.

Rust Data 38,808 players 11,700 servers online