RUST METRICSFlight deck · live data
Data live Servers11,792 Players68,594 Populated3,568 Fresh wipes 3 h191 Scan5 min
‹ All servers37.18.21.171:35000
Online Full Queue Fresh wipe Wipe due No query

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 9m ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 25 50 75 100 PAX 1 /100

Players now

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

Server fps

48 h low 97 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 125,039 ×1000

Entities

48 h range 122,335–125,403 · memory 3,621 MB
1239 ET SINCE RESTART 13:56

Uptime

13 h 56 min since its last restart, at the last reading
7-day average0peak 4
Rank#4,218top 19%
Last wipe13d agobiweekly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Memory3,621MB48 h peak 3 players
REC 1

Players

AveragePeak
0123413:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020013:0022:0007:0016:0002:0011:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 19% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe · high confidence

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak10players, last three wipes
crowd held0%else halves by day 6.5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 6hFW
  2. WPT 2Thu 12 Nov, 23:20 UTC14d 10h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 6hFW
  4. WPT 4Thu 10 Dec, 23:20 UTC42d 10h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 43 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 23:20 UTC13d ago 7 – running 0
Thu 1 Oct, 21:05 UTC FW27d ago 8 halved by day 6 14.1 days 0
Thu 17 Sep, 23:15 UTC41d ago 15 halved by day 7 13.9 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 OMSK | WipeBlock |K i T | 16 - 30 when wipe day comes?

The busiest point of its recent wipes drew 10 players on average. Peak crowd on the latest wipe: 43 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 6.5 it fell below half.

How often does OMSK | WipeBlock |K i T | 16 - 30 wipe, and when?

The wipe rhythm of OMSK | WipeBlock |K i T | 16 - 30 is every 4 weeks on Thursday at 23:20 UTC. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 13 days 13 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Lists and filters

Which tags does OMSK | WipeBlock |K i T | 16 - 30 carry, and what do they mean?

These are the tags OMSK | WipeBlock |K i T | 16 - 30 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts10 (Group limit): Teams are capped at 10; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show OMSK | WipeBlock |K i T | 16 - 30?

On Rust Metrics, OMSK | WipeBlock |K i T | 16 - 30 sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

Where does OMSK | WipeBlock |K i T | 16 - 30 sit in the rankings?

Ranking for OMSK | WipeBlock |K i T | 16 - 30: #4,218 on seven-day player hours, top 19% of all ranked servers.

What is the population on OMSK | WipeBlock |K i T | 16 - 30?

Current headcount on OMSK | WipeBlock |K i T | 16 - 30: 1 players, 100 slots available. Check: players over seven days. Average 0, peak 4. Check: 48-hour peak. 19:00 UTC, 3 players on average.

Operator and location

Which location does OMSK | WipeBlock |K i T | 16 - 30 run from?

No region comes from OMSK | WipeBlock |K i T | 16 - 30. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 37.18.21.171:35000.

What Rust version is OMSK | WipeBlock |K i T | 16 - 30 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by OMSK | WipeBlock |K i T | 16 - 30. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for OMSK | WipeBlock |K i T | 16 - 30?

Over the last 48 hours the average was 143 server fps; the floor was 97. Peak entity count: 125,403. Buildings, deployables and all else included. Memory peak: 3,920 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is OMSK | WipeBlock |K i T | 16 - 30, and is it online now?

Check: connection. OMSK | WipeBlock |K i T | 16 - 30 is online at this moment. Check: restart. The uptime it reports puts the last restart about 13 hours ago. Uptime for the last 7 full days: 165 of 168 hours, or 98%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does OMSK | WipeBlock |K i T | 16 - 30 enforce, and what are its settings?

Check: gather rate. The name OMSK | WipeBlock |K i T | 16 - 30 does not state one. The cap on groups is 10 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on OMSK | WipeBlock |K i T | 16 - 30?

Check: map. Procedural, size 4,500, seed 882159982, generated by the game on OMSK | WipeBlock |K i T | 16 - 30. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

What do you do to join OMSK | WipeBlock |K i T | 16 - 30?

Check: join. Open Rust, press F1, then enter client.connect 37.18.21.171:35000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/khp73Xxq is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts10,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts10
Group limit Teams are capped at 10.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.