Rust HeatmapInfrared · players
IR live Players45,403 Servers11,694 Warm3,140 Fresh wipes · 3h97 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–100° · slots

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 12m ago

biweekly wipes moddedoxide
Sp1 · players now 0/ 100
0% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 3°
Tue 01:00flare: a wipe in that hourWed 23:00
0
7-day average
peak 4
#4,164
rank
top 19%
13d ago
last wipe
biweekly schedule
7d 18h
next wipe
Thu 5 Nov, 19:00 UTC FW
UTC checked 12m ago

Li2Players

AveragePeak
0123401:0010:0019:0004:0013:0023:00

Hourly average and peak, UTC.

Li3Server performance

05010015020001:0010:0019:0004:0013:0023: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.

Li4Rank

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

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

Bx1Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. 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 18h
Thu 5 Nov, 19:00 UTC
FW
14d 22h
Thu 12 Nov, 23:20 UTC
35d 18h
Thu 3 Dec, 19:00 UTC
FW
42d 22h
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
Friendly Seattle: No KOS | Chill | Noob Friendly
NA · groups of 8+ · biweekly · 40 on average
48 / 100
[JP]初心者PVPサーバー|RaidTime・ Events
EA · groups of 10+ · biweekly · 17 on average
4 / 100
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10
EU · groups of 50+ · biweekly · 9 on average
3 / 200
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ
EU · groups of 8+ · biweekly · 8 on average
5 / 200
Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS out
groups of 8+ · biweekly · 5 on average
9 / 50
[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29
EA · no group limit · biweekly · 4 on average
1 / 20

LogQuick answers

from the figures on this page

Wipe day

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

Its recent wipes drew an average peak of 10 players. 43 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. It fell below half by day 6.5 when it did not hold.

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

OMSK | WipeBlock |K i T | 16 - 30 runs a wipe schedule of every 4 weeks on Thursday at 23:20 UTC. On Thursday 5 November at 19:00 UTC the force wipe comes, and that is its next wipe, as for every Rust server. The world in play now was made 13 days 1 hours ago. Its tags state a wipe every two weeks.

Population

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

Of 100 slots on OMSK | WipeBlock |K i T | 16 - 30, 0 are in use right now. Averaged over the past week: 0 players, peaking at 4. Look at 19:00 UTC for the last 48 hours: that hour averaged 3 players.

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

Ranked #4,164 on seven-day player hours, OMSK | WipeBlock |K i T | 16 - 30 is in the top 19% of all ranked servers.

Rules and settings

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

OMSK | WipeBlock |K i T | 16 - 30 runs a procedural map of size 4,500 with seed 882159982, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page.

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

No gather rate appears in the name OMSK | WipeBlock |K i T | 16 - 30. The group limit is 10 players. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. VAC is on, which is Valve's anti-cheat.

Server details

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

Rust network protocol 2635 and build 168909 is the build OMSK | WipeBlock |K i T | 16 - 30 runs, on Windows. To join, your game must match the protocol; Steam handles the update.

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

The server is up at the moment: OMSK | WipeBlock |K i T | 16 - 30 is online. The uptime it reports puts the last restart at about 1 hours ago. 142 of 168 hours up over the last 7 full days, which is 85%. Rust Heatmap has had it on record since 13 September 2026.

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

No region is published by OMSK | WipeBlock |K i T | 16 - 30. Rust Heatmap shows the location a server states. It does not look up the machine's location. 37.18.21.171:35000 is its address.

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

It averaged 148 server fps over the last 48 hours, with a low of 101. Buildings, deployables and the rest of the world came to as much as 125,424 entities. Memory use reached 3,920 MB at most. What players call lag is low fps together with a growing entity count.

Tags

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

The Rust Heatmap lists that OMSK | WipeBlock |K i T | 16 - 30 fits are: Modded Rust servers, by live population. These are the filters that return it on the 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.

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

gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): The slot count is 100; ts10 (Group limit): Teams cap at 10; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^b (Biweekly): The wipe interval is two weeks; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game are the tags OMSK | WipeBlock |K i T | 16 - 30 publishes, and the server browser reads them. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

Connect

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

To join by console, open it with F1 in Rust and enter client.connect 37.18.21.171:35000. Or press Launch Rust on this page, which connects you through Steam. The server's site sits at https://discord.com/invite/khp73Xxq.

KeyServer 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 form.
mp100
Max players The slot count is 100.
ts10
Group limit Teams cap at 10.
v2635
Protocol To join, run the same version: game protocol 2635.
cs168909
Build The game build here is 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Wipe schedule

^b
Biweekly The wipe interval is two weeks.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Listed as Modded, since settings or plugins change 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.