Rust PopulationField survey · Rust servers
Observing 89,289 players 11,829 servers 4,008 with someone on 23 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 4,033habitat unknownfirst seen 13 Sep 2026

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 2h ago

biweekly wipes moddedoxide

Measurements

Players now
1/ 100
= 1 player
1% full
7-day average
1
peak 4
Rank
#4,033
top 18%
Last wipe
12d ago
biweekly schedule
Next wipe
7d 23h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

05010015020020:0005:0014:0023:0008:0017: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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Obs. 4 · the wipe cycle

Wipe schedule

fixed weekdays

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

28 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
10
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 6.5

Coming wipes

7d 23h
Thu 5 Nov, 19:00 UTC
FW
15d 3h
Thu 12 Nov, 23:20 UTC
35d 23h
Thu 3 Dec, 19:00 UTC
FW
43d 3h
Thu 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

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

Log · wipes seen

Wipes

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

Field questions

Quick answers

from the figures on this page

Population

How does OMSK | WipeBlock |K i T | 16 - 30 rank against other Rust servers?

By player hours over the last seven days, OMSK | WipeBlock |K i T | 16 - 30 places at #4,033, within the top 18% of ranked servers.

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

The count reads 1 players on OMSK | WipeBlock |K i T | 16 - 30, which has 100 slots. We counted an average of 1 players in the past week, with 4 at the busiest. The busiest hour in the last 48 was 19:00 UTC, when an average of 3 players were on.

Lists and tags

What do the server tags on OMSK | WipeBlock |K i T | 16 - 30 mean?

These are the tags OMSK | WipeBlock |K i T | 16 - 30 publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts10 (Group limit): You may team with up to 10 players; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include OMSK | WipeBlock |K i T | 16 - 30?

These Rust Population lists include OMSK | WipeBlock |K i T | 16 - 30: Modded Rust servers, counted. Look for it under 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.

Wipe notes

What does wipe day look like on OMSK | WipeBlock |K i T | 16 - 30?

Averaged over recent wipes, 10 players were counted at the busiest point. Peak came 43 hours into the latest wipe. In 0% of recent wipes, half the peak was held until the next wipe. The crowd dropped below half by day 6.5 when it did not hold.

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

Counted by rhythm, OMSK | WipeBlock |K i T | 16 - 30 wipes every 4 weeks on Thursday at 23:20 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. The world it runs now dates from 12 days 20 hours ago. A wipe every two weeks is what the tags publish.

Map and rules

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

OMSK | WipeBlock |K i T | 16 - 30 uses a map the game generates, procedural, at size 4,500 with seed 882159982. Size and seed together fix the map, so you can view it on RustMaps from this page.

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

Nothing in OMSK | WipeBlock |K i T | 16 - 30's name says how gather works. A group may hold 10 players at most. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. Modded is its browser category: plugins or settings change the game. The plugins it runs are Oxide. You play with Valve's anti-cheat on: VAC.

About the server

Which version of Rust does OMSK | WipeBlock |K i T | 16 - 30 run?

The setup is Rust network protocol 2635 and build 168909 on Windows for OMSK | WipeBlock |K i T | 16 - 30. The protocol must match for you to join, and Steam updates it for you.

Does OMSK | WipeBlock |K i T | 16 - 30 run smoothly?

In the last 48 hours, it averaged 151 server fps, with a low of 128. The entity count reached 125,424: buildings, deployables and all other objects. Up to 3,920 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.

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

Right now, OMSK | WipeBlock |K i T | 16 - 30 is online. About 18 hours ago, it restarted, according to its uptime. It was up 99% of the time over the last 7 full days, 166 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.

Where is OMSK | WipeBlock |K i T | 16 - 30 located?

Nothing published by OMSK | WipeBlock |K i T | 16 - 30 states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 37.18.21.171:35000.

How to join

How do I join OMSK | WipeBlock |K i T | 16 - 30?

To connect directly, open Rust's console with F1 and type client.connect 37.18.21.171:35000; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://discord.com/invite/khp73Xxq.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players 100 slots are available.
ts10
Group limit You may team with up to 10 players.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The server wipes on a two-week cycle.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The game is changed by plugins or settings, 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.