RUST METRICSFlight deck · live data
Data live Servers11,626 Players40,285 Populated2,838 Fresh wipes 3 h132 Scan5 min
‹ All servers185.158.114.22:30015
Online Full Queue Fresh wipe Wipe due No query

(RU) GRIZZLY (SOLO) 28.10

Online EU 185.158.114.22:30015 checked 19m ago

weekly wipes oxide
COM 1 · connect
Launch Rust and join

Server instruments

last reading Fri 03:00 UTC
0 75 150 225 300 PAX 0 /300

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 227 SERVER FPS

Server fps

48 h low 164 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 4,495 ×1000

Entities

48 h range 1,991–4,711 · memory 709 MB
1239 ET SINCE RESTART 1D 20H

Uptime

1 days 20 hours since its last restart, at the last reading
7-day average1peak 2
Rank#3,744top 17% · #1388 in EU
Last wipe1d agoweekly schedule
Next wipe5d 1hWed 4 Nov, 06:25 UTC
Memory709MB48 h peak 1 players
REC 1

Players
AveragePeakWipe
00.250.50.75105:0014:0000:0009:0018:0003:00Wiped Wed 28 Oct, 06:25 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance
Server fpsWipe
010020030040005:0014:0000:0009:0018:0003: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.

REC 3

Rank

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

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

PLAN

Wipe schedule

from its schedule tag

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

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

Coming wipes

  1. WPT 1Wed 4 Nov, 06:25 UTC5d 1h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 14hFW
  3. WPT 3Wed 11 Nov, 06:25 UTC12d 1h
  4. WPT 4Wed 18 Nov, 06:25 UTC19d 1h
  5. WPT 5Wed 25 Nov, 06:25 UTC26d 1h
  6. WPT 6Wed 2 Dec, 06:25 UTC33d 1h
  7. WPT 7Thu 3 Dec, 19:00 UTC34d 14hFW
  8. WPT 8Wed 9 Dec, 06:25 UTC40d 1h

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.

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on (RU) GRIZZLY (SOLO) 28.10 when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. 1 hours after the wipe, the crowd peaked on the latest wipe.

How often does (RU) GRIZZLY (SOLO) 28.10 wipe, and when?

Its tag guides the prediction: too few of (RU) GRIZZLY (SOLO) 28.10's wipes are on record to confirm its schedule. Due on Wednesday 4 November at 06:25 UTC is its next wipe. The world it runs now was made 46 hours ago. A weekly wipe schedule is published in its tags.

Lists and filters

Which tags does (RU) GRIZZLY (SOLO) 28.10 carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp300 (Max players): 300 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^w (Weekly): Check: wipe cycle. Every week; ^t (Tutorial on): The Facepunch tutorial is open to new players here; ^o (Oxide): It runs Oxide, also known as uMod; EU (Europe): The server browser files it under Europe from (RU) GRIZZLY (SOLO) 28.10. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does (RU) GRIZZLY (SOLO) 28.10 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring (RU) GRIZZLY (SOLO) 28.10: Rust tutorial servers, EU Rust servers, checked and Rust community servers: live readings. These filters bring it up on the server list: 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 count

What position does (RU) GRIZZLY (SOLO) 28.10 hold among Rust servers?

Player hours over the last seven days put (RU) GRIZZLY (SOLO) 28.10 at #3,744, #1,388 in Europe, in the top 17% of all ranked servers.

What player count does (RU) GRIZZLY (SOLO) 28.10 carry?

0 of 300 slots are filled on (RU) GRIZZLY (SOLO) 28.10 right now. Check: players over seven days. Average 1, peak 2. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.

Server details

Which location does (RU) GRIZZLY (SOLO) 28.10 run from?

(RU) GRIZZLY (SOLO) 28.10 gives Europe as its location, with the EU tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 185.158.114.22:30015.

What Rust version is (RU) GRIZZLY (SOLO) 28.10 on?

Reading: (RU) GRIZZLY (SOLO) 28.10, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on (RU) GRIZZLY (SOLO) 28.10 within range?

Over the last 48 hours the average was 211 server fps; the floor was 164. Check: entities. The peak was 4,711, counting buildings, deployables and the rest of the world. Reading: 1,519 MB of memory at the highest. Expect lag when fps falls and entities climb.

Is (RU) GRIZZLY (SOLO) 28.10 up, and how often does it stay up?

Check: connection. (RU) GRIZZLY (SOLO) 28.10 is online at this moment. Reading: uptime. About 44 hours ago it restarted, on its own count. Reading: 99% uptime over the last 5 full days. It was up 119 of 120 hours. Check: first contact. Rust Metrics logged it on 24 October 2026.

Settings and map

What rules does (RU) GRIZZLY (SOLO) 28.10 enforce, and what are its settings?

Check: gather rate. The name (RU) GRIZZLY (SOLO) 28.10 does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on (RU) GRIZZLY (SOLO) 28.10?

Check: map. Procedural, size 1,000, seed 21189, generated by the game on (RU) GRIZZLY (SOLO) 28.10. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

What do you do to join (RU) GRIZZLY (SOLO) 28.10?

To join: start Rust, press F1 and type client.connect 185.158.114.22:30015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

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 Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Gameplay

^t
Tutorial on The Facepunch tutorial is open to new players here.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

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.