Rust Server TrendsSeismic network · station log
Recording Stations11,697 Players44,561 Active3,120 Wipes · 3 h101 48 h

Station XX-10093 · no signal

KOVCHEG TEST 3500

Offline 92.38.92.203:28015 checked 8h ago

moddedoxide
Connect
Players now
0/ 20
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#10,093
top 45%
Last wipe
2d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-10093 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 20 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123402:0010:0018:0001:0009:0017:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020002:0010:0018:0001:0009: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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
10.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctSun 4 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 26 Oct, 07:36 UTC2d ago M0.0rising 1 – running 0
Sun 4 Oct, 18:57 UTC24d ago M0.0steady 0 – 21.5 days 0
Sun 4 Oct, 11:04 UTC24d ago M0.0rising 1 – 0.3 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 155 on average
38/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
40/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average
34/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
7/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
5/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on KOVCHEG TEST 3500?

KOVCHEG TEST 3500 runs a procedural map of size 3,500 with seed 369217113, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on KOVCHEG TEST 3500?

The name of KOVCHEG TEST 3500 gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

What is the current population on KOVCHEG TEST 3500?

KOVCHEG TEST 3500 is not responding at this moment and is offline, last seen 8 hours ago. The seven-day average is 0 players, with a peak of 1.

How does KOVCHEG TEST 3500 rank against other Rust servers?

On player hours for the past week, KOVCHEG TEST 3500 sits at #10,093, which puts it inside the top 45% of every ranked server.

Server facts

How reliably does KOVCHEG TEST 3500 stay online?

KOVCHEG TEST 3500 is down at the moment; the last recorded contact was 8 hours ago. Going by the uptime figure it reports, it restarted about 2 days 7 hours ago. It was up 48% of the time across the last 7 full days: 80 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 3 October 2026.

How well does KOVCHEG TEST 3500 perform under load?

Across the last 48 hours it averaged 117 server fps, with a floor of 94. The world held up to 73,503 entities at its peak, buildings and deployables included. Memory use peaked at 2,730 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does KOVCHEG TEST 3500 run from?

No region is published by KOVCHEG TEST 3500. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 92.38.92.203:28015 is the address it uses.

Which Rust version is KOVCHEG TEST 3500 running?

Rust network protocol 2635 and build 168909 on Windows is what KOVCHEG TEST 3500 runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on KOVCHEG TEST 3500?

1 players, on average, was the busiest crowd at its recent wipes. 1 hours after the latest wipe, the crowd peaked.

How often does KOVCHEG TEST 3500 wipe, and on which days?

There is no next wipe to predict at KOVCHEG TEST 3500, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 2 days 17 hours.

Lists and tags

What do the server tags on KOVCHEG TEST 3500 mean?

Tags published by KOVCHEG TEST 3500 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): The server has 20 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does KOVCHEG TEST 3500 appear?

These Rust Server Trends lists include KOVCHEG TEST 3500: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

What steps get you onto KOVCHEG TEST 3500?

To join, enter client.connect 92.38.92.203:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://vk.ru/rustkovcheg.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players The server has 20 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

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

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.