Skip to the content
Dive report

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 15m ago

biweekly wipes moddedoxide
Drop in
2/ 100 players now 2% full
17-day averagepeak 7
#3,676ranktop 17%
2d agolast wipebiweekly schedule
18d 10hnext wipeThu 5 Nov, 19:00 UTC FW

Players

AveragePeak
0246809:0018:0003:0013:0022:0007:00

Hourly average and peak, UTC.

Server performance

010020030040009:0018:0003:0013:0022:0007: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

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

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 18d 10h. 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

  • 18d 10h
    Thu 5 Nov, 19:00 UTC
    FW
  • 25d 14h
    Thu 12 Nov, 23:20 UTC

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 23:20 UTC2d ago 7 – running 0
Thu 1 Oct, 21:05 UTC FW16d ago 8 halved by day 6 14.1 days 0
Thu 17 Sep, 23:15 UTC30d 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.

Neighbouring dive spots

Similar servers

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

From the figures on this page

Quick answers

Tags and filters

Where does OMSK | WipeBlock |K i T | 16 - 30 appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include OMSK | WipeBlock |K i T | 16 - 30: Modded Rust servers. The server list shows it under 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 3 days.

How should you read the tags on OMSK | WipeBlock |K i T | 16 - 30?

OMSK | WipeBlock |K i T | 16 - 30's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp100 (Max players): The slot count is 100; ts10 (Group limit): You can have up to 10 in a team; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): The build number is 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^b (Biweekly): It wipes fortnightly; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

About the server

Is OMSK | WipeBlock |K i T | 16 - 30 lag-free?

It averaged 171 server fps over the last 48 hours, with a low of 113. Buildings, deployables and all other world objects added up to as many as 121,667 entities. Memory use peaked at 3,808 MB. What players notice as lag comes from low fps and a rising entity count.

What location is OMSK | WipeBlock |K i T | 16 - 30 in?

OMSK | WipeBlock |K i T | 16 - 30 does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 37.18.21.171:35000.

Is OMSK | WipeBlock |K i T | 16 - 30 up, and how often does it stay online?

OMSK | WipeBlock |K i T | 16 - 30 is up and reachable at the moment. According to its reported uptime, the last restart was about 9 hours ago. Over the past full 7 days it stayed up for 168 of 168 hours, or 100%. 13 September 2026 is when Rust Going Deep first saw it.

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

On Windows, OMSK | WipeBlock |K i T | 16 - 30 runs Rust network protocol 2634 and build 167781. The protocol must match to join; Steam will update your game.

Wipe details

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

OMSK | WipeBlock |K i T | 16 - 30 follows a every 4 weeks on Thursday at 23:20 UTC wipe pattern. On Thursday 5 November at 19:00 UTC the force wipe arrives, wiping every Rust server, and that is its next wipe. The world you are on now was created 2 days 9 hours. The tags show wipes scheduled every two weeks.

What can you expect on wipe day at OMSK | WipeBlock |K i T | 16 - 30?

The average peak across recent wipes is 10 players. The peak crowd on the latest wipe came 43 hours in. Above half that peak until the next wipe: the crowd managed this in 0% of recent wipes. Otherwise, the crowd sank below half by day 6.5.

Settings and map

What settings are in place on OMSK | WipeBlock |K i T | 16 - 30?

The name of OMSK | WipeBlock |K i T | 16 - 30 contains no gather rate. The group limit is 10 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.

What's the map on OMSK | WipeBlock |K i T | 16 - 30?

The map on OMSK | WipeBlock |K i T | 16 - 30 is procedural and size 4,500, generated by the game with seed 882159982. The map is reproducible from its size and seed, so RustMaps can show it from this page.

Player stats

Is OMSK | WipeBlock |K i T | 16 - 30 busy?

Out of 100 slots, 2 are filled on OMSK | WipeBlock |K i T | 16 - 30 right now. The seven-day average is 1 players, with a peak of 7. The busiest point in the last 48 hours was 18:00 UTC, averaging 6 players.

What position does OMSK | WipeBlock |K i T | 16 - 30 hold in the server rankings?

Over the last seven days, OMSK | WipeBlock |K i T | 16 - 30 is #3,676 by player hours, among the top 17% of all ranked servers.

Getting in

What's the process to join OMSK | WipeBlock |K i T | 16 - 30?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 37.18.21.171:35000. https://discord.com/invite/khp73Xxq is its website.

What each one means

Server tags

Published as mp100,ptrak,$r?,v2634,^b,gmrust,cs167781,ts10,^o^z

Game

gmrust
Game mode Survival, as standard Rust does it.
mp100
Max players The slot count is 100.
ts10
Group limit You can have up to 10 in a team.
v2634
Protocol This server runs game protocol 2634, so your game must match that version to join.
cs167781
Build The build number is 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly It wipes fortnightly.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded You'll see it in Modded, since plugins or settings modify the game.

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.