Rust Server Analytics 102,237 players11,898 servers
All servers
Drill-through Server detail

(RU) GRIZZLY (SOLO) 28.10

Online EU 185.158.114.22:30015 checked 10m ago

Drill-through
FilterServeris (RU) GRIZZLY (SOLO) 28.10
Attributes
weekly wipes oxide
Last refreshed
Players now 1/ 300
7-day average 1 peak 2
Rank #3,821 top 17% · #1404 in EU
Last wipe 1d ago weekly schedule
Next wipe 5d 12h Wed 4 Nov, 06:25 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.250.50.75119:0004:0013:0022:0007:0016:00Wiped Wed 28 Oct, 06:25 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
010020030040019:0004:0013:0022:0007:0016:00Wiped Wed 28 Oct, 06:25 UTCWIPE

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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 17% of all ranked servers, top 48% in EU. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Wednesday 4 November, 06:25 UTC, in 5d 12h. Its weekly schedule tag · low confidence

usual gap1 daysbetween real wipes
wipe-day peak2players, last three wipes

Coming wipes

InWhen, UTCKind
5d 12hWed 4 Nov, 06:25 UTCits own
7d 0hThu 5 Nov, 19:00 UTCFW force wipe
12d 12hWed 11 Nov, 06:25 UTCits own
19d 12hWed 18 Nov, 06:25 UTCits own
26d 12hWed 25 Nov, 06:25 UTCits own
33d 12hWed 2 Dec, 06:25 UTCits own
35d 0hThu 3 Dec, 19:00 UTCFW force wipe
40d 12hWed 9 Dec, 06:25 UTCits own

The first 48 hours of its last wipes

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

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 06:25 UTC1d ago – – running 0
Tue 27 Oct, 06:26 UTC2d ago 2 – 1 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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 512 on average 346 / 400
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 280 on average 983 / 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average 45 / 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 265 on average 992 / 1000
Rustafied.com - EU Main EU · groups of 16+ · weekly · 225 on average 840 / 850
Magic Rust — Main | Kлaccикa x1 | Baйп 29.10 EU · groups of 100+ · 1x · weekly · 213 on average 577 / 600

Quick answers

from the figures on this page

Wipe cycle

When does (RU) GRIZZLY (SOLO) 28.10 wipe?

The prediction follows its tag, because too few of (RU) GRIZZLY (SOLO) 28.10's wipes are on record to confirm the schedule. Wednesday 4 November at 06:25 UTC is the date the next wipe falls on. 35 hours ago the current world was made. Its tags carry a weekly wipe schedule.

Wipe day on (RU) GRIZZLY (SOLO) 28.10: what should you expect?

Across recent wipes the busiest point averaged 2 players. 1 hours after the latest wipe the crowd peaked.

Server

In which region does (RU) GRIZZLY (SOLO) 28.10 sit?

Its EU tag puts (RU) GRIZZLY (SOLO) 28.10 in Europe. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 185.158.114.22:30015.

What Rust build does (RU) GRIZZLY (SOLO) 28.10 run?

On Linux, (RU) GRIZZLY (SOLO) 28.10 runs Rust network protocol 2635 and build 168909. The protocol has to match before you can join; Steam updates it automatically.

Is (RU) GRIZZLY (SOLO) 28.10 up, and how steady is its uptime?

The current status of (RU) GRIZZLY (SOLO) 28.10 is online. The uptime it reports puts the last restart at about 33 hours ago. Of 96 hours in the last 4 full days, 95 were up: 99%. 24 October 2026 is when Rust Server Analytics first recorded it.

Does (RU) GRIZZLY (SOLO) 28.10 perform well?

Server fps averaged 212 over the last 48 hours, with a floor of 164. Buildings, deployables and all other world objects brought the entity total to 4,635. Memory use reached 1,293 MB at peak. A climbing entity count and low fps are the lag players perceive.

Tags

Which meanings do the tags on (RU) GRIZZLY (SOLO) 28.10 carry?

gmvanilla (Game mode): Survival on vanilla settings; mp300 (Max players): 300 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^w (Weekly): Wipes run on a weekly cycle; ^t (Tutorial on): The Facepunch tutorial can be used here by new players; ^o (Oxide): It runs Oxide (uMod) for plugins; EU (Europe): The server browser files it under Europe are the tags (RU) GRIZZLY (SOLO) 28.10 publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature (RU) GRIZZLY (SOLO) 28.10?

Among the Rust Server Analytics lists (RU) GRIZZLY (SOLO) 28.10 fits are: Rust tutorial servers, EU Rust servers: live population data and Community Rust servers, live. On the server list, the filters that return it are: Region: Europe; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Tutorial on ^t and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days.

Player numbers

Where does (RU) GRIZZLY (SOLO) 28.10 sit among Rust servers?

(RU) GRIZZLY (SOLO) 28.10 holds #3,821 on seven-day player hours and #1,404 in Europe, inside the top 17% of the ranked field.

What is the population of (RU) GRIZZLY (SOLO) 28.10?

(RU) GRIZZLY (SOLO) 28.10 holds 1 players of its 300 slots as of the latest update. The seven-day mean is 1 players, against a peak of 2. Averaged over 48 hours, activity is highest at 19:00 UTC with 1 players.

Map and rules

How is (RU) GRIZZLY (SOLO) 28.10 configured, and what rules apply?

Gather rate is not mentioned in the name of (RU) GRIZZLY (SOLO) 28.10. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser, it appears under Community. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.

The map on (RU) GRIZZLY (SOLO) 28.10: which one is it?

(RU) GRIZZLY (SOLO) 28.10 uses a procedural map of size 1,000 with seed 21189, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Connection

How do you connect to (RU) GRIZZLY (SOLO) 28.10?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 185.158.114.22:30015.

Server tags

what each one means

Published as mp300,ptrak,$r?,v2635,^w,EU,^t,gmvanilla,cs168909,ts8,^o

Game

gmvanilla
Game mode Survival on vanilla settings.
mp300
Max players 300 slots in total.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code No region code has been set.

Wipe schedule

^w
Weekly Wipes run on a weekly cycle.

Gameplay

^t
Tutorial on The Facepunch tutorial can be used here by new players.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.

Region

EU
Europe The server browser files it 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.