At press time 11,894 servers99,159 players396 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 10,035

KOVCHEG TEST 3500

Offline 92.38.92.203:28015 checked 1d ago

KOVCHEG TEST 3500 is a Rust server. It was offline at the last count; over the past week it averaged 0, with a peak of 1. It stands at No. 10,035 of the ranked servers, the top 45%. It last wiped 3d ago. Its own tags class it as modded, oxide.

§ 1Attendance

AveragePeak
0123418:0023:0003:0008:0012:0017:00

Hourly average and peak, UTC.

§ 2Performance

05010015020018:0023:0003:0008:0012: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.

§ 3Standingthe 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.

§ 4The wipe scheduleno rhythm it keeps

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

The rhythm
Usual gap10.9 days

between real wipes

On rhythm0%

of its recent wipes

Wipe-day peak1

players, 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.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 07:36 UTC3d ago 1 – running 0
Sun 4 Oct, 18:57 UTC24d ago 0 – 21.5 days 0
Sun 4 Oct, 11:04 UTC25d ago 1 – 0.3 days 0

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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 ShockRust | Blue | NoLimit157/500 no group limit · 151 on average
  2. 2 МИНИ-КАРТА 2Х | STORM | FPS+ 28.10133/100 EU · groups of 8+ · weekly · 128 on average
  3. 3 RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10185/225 EU · groups of 16+ · weekly · 118 on average
  4. 4 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.1094/700 EU · groups of 16+ · monthly · 94 on average
  5. 5 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10231/700 EU · groups of 16+ · monthly · 88 on average
  6. 6 RustSpain.com | EU Main348/350 EU · groups of 12+ · weekly · 84 on average

§ 7Questions answeredfrom the figures in this entry

Server record

What Rust version is KOVCHEG TEST 3500 on?

Rust network protocol 2635 and build 168909 on Windows is what KOVCHEG TEST 3500 runs. The protocol must match on your game to join; the update comes through Steam.

What does uptime look like on KOVCHEG TEST 3500, and is it up?

The records show KOVCHEG TEST 3500 offline, last answering 24 hours ago. Of note: the reported uptime places the last restart about 2 days 7 hours ago. In the last 7 full days it was up for 80 of 168 hours, 48% of the time. The first sighting at Rust Server Stats was on 3 October 2026.

What is the performance of KOVCHEG TEST 3500 like?

For the last 48 hours the average was 115 server fps, with a low of 94. The entity count reached 72,689: buildings, deployables and all else in the world. Of note: memory use reached 2,730 MB. Lag, as players meet it, comes from low fps and an entity count on the rise.

Where does KOVCHEG TEST 3500 operate from?

No region is published by KOVCHEG TEST 3500. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. At 92.38.92.203:28015 stands the address.

The rules and map

The map for KOVCHEG TEST 3500: which one is it?

KOVCHEG TEST 3500 runs a procedural map, generated by the game, of size 3,500 with seed 369217113. RustMaps can display it from this page, since equal size and seed yield the same map.

The rules and settings of KOVCHEG TEST 3500: what are they?

No gather rate appears in the name of KOVCHEG TEST 3500. Groups are capped at 8 players, the standard default. survival is the game mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. The server browser lists it under Modded, where plugins or settings alter the game. Plugins run here: Oxide. VAC, Valve's anti-cheat, is enabled.

The players

What are the player numbers on KOVCHEG TEST 3500?

No answer from KOVCHEG TEST 3500 at the latest refresh; it was last seen 24 hours ago. The seven-day record: an average of 0 players and a peak of 1.

Where does KOVCHEG TEST 3500 sit in the rankings?

Ranked by player hours over the last seven days, KOVCHEG TEST 3500 stands at #10,035, in the top 45% overall.

The tags and lists

KOVCHEG TEST 3500 sits in which Rust Server Stats lists and filters?

The Rust Server Stats lists KOVCHEG TEST 3500 fits: Modded Rust servers. On the server list it comes up under these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings attach to the tags on KOVCHEG TEST 3500?

gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): Slot count: 20; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): The build number is 168909; ptrak (Networking): RakNet carries it, the standard layer for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded — that is the set of tags KOVCHEG TEST 3500 publishes for the game's browser. At the top of this page are its current players, queue and world creation time, all taken from the tags.

Wipe schedule

What happens on KOVCHEG TEST 3500 when wipe day arrives?

Across its recent wipes, the busiest point averaged 1 players. 1 hours into the latest wipe the crowd reached its peak.

The wipe timetable for KOVCHEG TEST 3500: what does it show?

No next wipe can be predicted for KOVCHEG TEST 3500, whose wipes fall at irregular times. The monthly force wipe falls on every Rust server alike, and Thursday 5 November at 19:00 UTC is the next one. Of note: the current world is 3 days 9 hours old.

How to join

How does one connect to KOVCHEG TEST 3500?

To connect, open the console with F1 in Rust and enter client.connect 92.38.92.203:28015. The Launch Rust and join button on this page does the same through Steam. https://vk.ru/rustkovcheg carries the server's website.

§ 8Key to the tagswhat each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp20
Max players Slot count: 20.
ts8
Group limit Set at the game default of 8 per team.
v2635
Protocol Join only on protocol 2635; other versions cannot connect.
cs168909
Build The build number is 168909.
ptrak
Networking RakNet carries it, the standard layer for the game.
$r?
Region code No region code is set.

Mods and access

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