StatusLive Servers online11,618 Players39,799 Populated2,961 Wiped · 3 h88 Interval5 min Date29 OCT 2026

DWG RG-S4153Server sheetchecked 9m ago

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 9m ago

biweekly wipes moddedoxide
Connect
Players now 0/ 100 0% full
7-day average0peak 4
Rank#4,153top 19%
Last wipe13d agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0123408:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Fig. 1Players on OMSK | WipeBlock |K i T | 16 - 30
Fig. 2

Server performance

05010015020008:0017:0002:0011:0021:0006: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.

Fig. 2FPS, entities and memory
Fig. 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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. 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. 7d 11hThu 5 Nov, 19:00 UTCFW
  2. 14d 15hThu 12 Nov, 23:20 UTC
  3. 35d 11hThu 3 Dec, 19:00 UTCFW
  4. 42d 15hThu 10 Dec, 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 42 on average
28 / 100
02
[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 16 on average
6 / 100
03
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average
3 / 200
04
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average
4 / 200
05 4 / 50
06 0 / 50
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

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

OMSK | WipeBlock |K i T | 16 - 30 is up at this moment. About 8 hours ago is when it last restarted, measured from the uptime it reports. 165 of 168 hours up over the last 7 full days, which is 98% of the time. First seen by Rust Graphs on 13 September 2026.

How does OMSK | WipeBlock |K i T | 16 - 30 perform, as measured?

The last 48 hours give an average of 145 server fps and a floor of 97. Counted at its highest: 125,403 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,920 MB. What players feel as lag is low fps together with a climbing entity count.

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

No region is published by OMSK | WipeBlock |K i T | 16 - 30. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 37.18.21.171:35000.

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

Rust network protocol 2635 and build 168909 on Windows: that is what OMSK | WipeBlock |K i T | 16 - 30 runs. Steam updates your game, which must be on the same protocol for you to join.

Counts

What does the population history show for OMSK | WipeBlock |K i T | 16 - 30?

At the last refresh, OMSK | WipeBlock |K i T | 16 - 30 recorded 0 players across 100 slots. Averaged across seven days, the player count is 0, with a peak of 4. Averaged over the last 48 hours, the player count is highest at 19:00 UTC: 3 players.

What rank has been recorded for OMSK | WipeBlock |K i T | 16 - 30?

Player hours over seven days place OMSK | WipeBlock |K i T | 16 - 30 at #4,153, within the top 19% of ranked servers.

Wipe data

What is recorded on OMSK | WipeBlock |K i T | 16 - 30 on wipe day?

An average of 10 players was recorded at the busiest point of its recent wipes. At 43 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 6.5.

Which times and days are wipes plotted at on OMSK | WipeBlock |K i T | 16 - 30?

The wipe rhythm at OMSK | WipeBlock |K i T | 16 - 30 is every 4 weeks on Thursday at 23:20 UTC. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The world it runs now was made 13 days 8 hours ago. Its tags give a wipe schedule of one wipe every two weeks.

Settings

What settings and rules apply on OMSK | WipeBlock |K i T | 16 - 30?

Gather rate for OMSK | WipeBlock |K i T | 16 - 30: not stated in the name. 10 players per group at most. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.

Which map has OMSK | WipeBlock |K i T | 16 - 30 loaded?

Seed 882159982 and size 4,500 define the procedural map OMSK | WipeBlock |K i T | 16 - 30 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does OMSK | WipeBlock |K i T | 16 - 30 appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry OMSK | WipeBlock |K i T | 16 - 30 are: Modded Rust servers. It is returned by these filters on the server list: 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.

On OMSK | WipeBlock |K i T | 16 - 30, what is meant by each tag?

Tags published by OMSK | WipeBlock |K i T | 16 - 30, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts10 (Group limit): The team limit is 10; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

How is OMSK | WipeBlock |K i T | 16 - 30 joined?

Enter client.connect 37.18.21.171:35000 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://discord.com/invite/khp73Xxq is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts10
Group limit The team limit is 10.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

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.

KeyTag string decoded