Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO Z SRV11,766online PAX66,169playing OCC3,487with players WIPED 3H192
MODModded traffic
Callsign

OMS4218=

OMSK | WipeBlock |K i T | 16 - 30

Online 37.18.21.171:35000 checked 8m ago

biweekly wipes moddedoxide
Clearance · join
Players now 1/ 100 1% full
7-day average0peak 4
Rank#4,218top 19%
Last wipe13d agobiweekly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0123413:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

Server performance

05010015020013:0022:0007:0015:0001:0010: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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

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. 7d 6hThu 5 Nov, 19:00 UTCFW
  2. 14d 11hThu 12 Nov, 23:20 UTC
  3. 35d 6hThu 3 Dec, 19:00 UTCFW
  4. 42d 11hThu 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.

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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign STT017NA · groups of 8+ · biweekly · 42 on average Friendly Seattle: No KOS | Chill | Noob Friendly
    Players 15/100
  2. 02MOD
    Callsign EVN020EA · groups of 10+ · biweekly · 16 on average [JP]初心者PVPサーバー|RaidTime・ Events
    Players 14/100
  3. 03MOD
    Callsign EVN210EU · groups of 50+ · biweekly · 9 on average СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10
    Players 9/200
  4. 04MOD
    Callsign ACD001EU · groups of 8+ · biweekly · 8 on average RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ
    Players 9/200
  5. 05MOD
    Callsign EMP021groups of 8+ · biweekly · 6 on average Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS out
    Players 4/50
  6. 06MOD
    Callsign FDG017groups of 8+ · biweekly · 4 on average Fudge Begynderserver(Casual Beta:Ticket on discord for access)
    Players 0/50
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

On Rust Tracker, OMSK | WipeBlock |K i T | 16 - 30 sits in these lists: Modded servers, tracked live. These filters surface it 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.

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

Listed for the server browser to read, OMSK | WipeBlock |K i T | 16 - 30 publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): Slots: 100; ts10 (Group limit): Team limit: 10; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Schedule

What should you expect on OMSK | WipeBlock |K i T | 16 - 30 when wipe day lands?

The average peak across recent wipes: 10 players. 43 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The fall below half came by day 6.5 where it did not hold.

On what schedule does OMSK | WipeBlock |K i T | 16 - 30 wipe?

Wipe rhythm at OMSK | WipeBlock |K i T | 16 - 30: every 4 weeks on Thursday at 23:20 UTC. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its world went live 13 days 12 hours. Its tags carry an every-two-weeks wipe schedule.

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 and online at this moment. The uptime it reports puts the last restart about 12 hours ago. 165 of 168 hours up over the last 7 full days: 98% uptime. First contact for Rust Tracker: 13 September 2026.

Which Rust build is OMSK | WipeBlock |K i T | 16 - 30 running?

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

What is performance like on OMSK | WipeBlock |K i T | 16 - 30?

Average server fps over the last 48 hours: 144, with a low of 97. Buildings, deployables and the rest of the world took it to a maximum of 125,403 entities. Memory peaked at 3,920 MB. A climbing entity count and low fps are what register as lag for players.

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

Region: none published by OMSK | WipeBlock |K i T | 16 - 30. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 37.18.21.171:35000.

Player Count

How many players are on OMSK | WipeBlock |K i T | 16 - 30 right now?

Tracking OMSK | WipeBlock |K i T | 16 - 30: 1 of 100 slots filled. Over seven days: average 0, peak 4 players. At 19:00 UTC it drew its highest average of the last 48 hours: 3 players.

What rank does OMSK | WipeBlock |K i T | 16 - 30 carry among Rust servers?

Seven-day player hours put OMSK | WipeBlock |K i T | 16 - 30 at #4,218, within the top 19% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on OMSK | WipeBlock |K i T | 16 - 30?

Nothing in OMSK | WipeBlock |K i T | 16 - 30's name states a gather rate. The group limit is 10 players. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.

Which map is confirmed for OMSK | WipeBlock |K i T | 16 - 30?

A procedural map of size 4,500 runs on OMSK | WipeBlock |K i T | 16 - 30, generated by the game from seed 882159982. Look at it on RustMaps from this page: equal size and seed return the same map.

Connect

How do you get onto OMSK | WipeBlock |K i T | 16 - 30?

To connect: start Rust, press F1, enter client.connect 37.18.21.171:35000 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://discord.com/invite/khp73Xxq.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players Slots: 100.
ts10
Group limit Team limit: 10.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; 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.