Skip to the page
Every Rust server graded on real, live numbers. 81,677 players on the roll · 11,911 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 28 October 2026 Pupil no. 37.18.21.171:35000
Name of server

OMSK | WipeBlock |K i T | 16 - 30

RegisterPresentOnline
Region–
Address37.18.21.171:35000
Last checked11m ago
biweekly wipes moddedoxide
Launch Rust and join Website
Overall grade

Working towards

52 out of 100, the average of 6 subjects

On the class lists: F (43), with population over 48 hours and no performance mark.

Players now 0/ 100 0% full
7-day average1peak 4
Rank#4,073top 18%
Last wipe12d agobiweekly schedule
Next wipe7d 22hThu 5 Nov, 19:00 UTC FW

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average 1/ 100 A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours 82/ 100 Holds a respectable place: #4,073 on player hours.
Uptimehours on the list, last 48 94/ 100 Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours 100/ 100 Runs smoothly: 151 server fps on average.
Wipeskeeping the crowd after a wipe 0/ 100 Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago 37/ 100 Slipped a little: down 1,051 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in performance (A+); wipes are the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

AveragePeak
0123421:0006:0015:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

05010015020021:0006:0015: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.

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.

Attendance: the wipe record

3 wipe days in the last 16 weeks

W wiped that day F the force wipe · today. From the wipes in the table below.

Wipe schedule

fixed weekdays

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

  • 7d 22hThu 5 Nov, 19:00 UTCFW
  • 15d 2hThu 12 Nov, 23:20 UTC
  • 35d 22hThu 3 Dec, 19:00 UTCFW
  • 43d 2hThu 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 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.

Similar servers

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

Quick answers

from the figures on this page

Server facts

In what location does OMSK | WipeBlock |K i T | 16 - 30 sit?

OMSK | WipeBlock |K i T | 16 - 30 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 37.18.21.171:35000.

How dependable is OMSK | WipeBlock |K i T | 16 - 30, and is it online at the moment?

You can join now: OMSK | WipeBlock |K i T | 16 - 30 is online. The uptime it reports puts the last restart at about 18 hours ago. For the last 7 full days, it was up 166 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.

Is OMSK | WipeBlock |K i T | 16 - 30 smooth to play on?

It never fell below 128 server fps in the last 48 hours, averaging 151. Up to 125,424 entities were in the world, covering buildings, deployables and the rest. Up to 3,920 MB of memory was used. When fps is low and entities climb, that is lag to players.

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

You will find OMSK | WipeBlock |K i T | 16 - 30 on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.

Wipe schedule

How frequently does OMSK | WipeBlock |K i T | 16 - 30 wipe its map?

Its wipe pattern: OMSK | WipeBlock |K i T | 16 - 30 wipes every 4 weeks on Thursday at 23:20 UTC. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 12 days 21 hours. Its tags say it wipes every two weeks.

What happens on OMSK | WipeBlock |K i T | 16 - 30 when wipe day arrives?

The average peak on its recent wipes was 10 players. 43 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 6.5 is when it sank below half in the wipes that did not hold.

Population

Where does OMSK | WipeBlock |K i T | 16 - 30 place in the wider field of Rust servers?

Over the last seven days, OMSK | WipeBlock |K i T | 16 - 30 has #4,073 for player hours, in the top 18% of all ranked servers.

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

Right now, 0 players are on OMSK | WipeBlock |K i T | 16 - 30, which has 100 slots. The seven-day average is 1 players, with a peak of 4. The busiest time in the last 48 hours was 19:00 UTC, with an average of 3 players.

Tags

What do OMSK | WipeBlock |K i T | 16 - 30's tags stand for?

The game's browser takes its cue from the tags OMSK | WipeBlock |K i T | 16 - 30 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts10 (Group limit): No team may go above 10; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.

Which Rust Server Score filters and lists feature OMSK | WipeBlock |K i T | 16 - 30?

These Rust Server Score lists count OMSK | WipeBlock |K i T | 16 - 30 among them: Modded Rust servers, graded. It shows under the following 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.

Server rules

How is OMSK | WipeBlock |K i T | 16 - 30 set up, and what rules does it keep?

The name of OMSK | WipeBlock |K i T | 16 - 30 gives no gather rate. The limit for a group is 10 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.

Which map is in play on OMSK | WipeBlock |K i T | 16 - 30?

The game generates the procedural map on OMSK | WipeBlock |K i T | 16 - 30 at size 4,500 with seed 882159982. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.

Getting in

How should you connect to OMSK | WipeBlock |K i T | 16 - 30?

Enter client.connect 37.18.21.171:35000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/khp73Xxq.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, played by the standard rules.
mp100
Max players 100 slots are available.
ts10
Group limit No team may go above 10.
v2635
Protocol The game protocol is 2635, so your game must match that version to join.
cs168909
Build This runs on build 168909.
ptrak
Networking RakNet handles it, the game's default network layer.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly A wipe happens once a fortnight.

Mods and access

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