Offline 92.38.92.203:28015 checked 10h ago
KOVCHEG TEST 3500
Connect
srv = rust.server("92.38.92.203:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 45% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 07:36 UTC2d ago | 1 | NaN | running | 0 |
| 1 | Sun 4 Oct, 18:57 UTC24d ago | 0 | NaN | 21.5 days | 0 |
| 2 | Sun 4 Oct, 11:04 UTC24d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3500 · seed 369217113
- map
- Procedural Map
- size
- 3500
- seed
- 369217113
Server
srv.info()- address
- 92.38.92.203:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 07:36 UTC
- hostname
- –
- first seen
- 3 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 38/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 10/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population data
How does KOVCHEG TEST 3500 compare in the rankings?
Rank #10,089 on seven-day player hours for KOVCHEG TEST 3500, within the top 45% of all ranked servers.
What population does KOVCHEG TEST 3500 carry?
The current row shows KOVCHEG TEST 3500 offline; the last response was 10 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
How smoothly does KOVCHEG TEST 3500 run?
Averaged over 48 hours: 117 server fps, never under 94. Buildings, deployables and all else in the world took the count as high as 73,036 entities. A high of 2,730 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on KOVCHEG TEST 3500?
The build is Rust network protocol 2635 and build 168909 on Windows, run by KOVCHEG TEST 3500. Steam updates your game for you, but the protocol must match to join.
How reliable is KOVCHEG TEST 3500, and is it up?
The latest sample has KOVCHEG TEST 3500 offline, with a last sighting 10 hours ago. The uptime it reports puts the last restart about 2 days 7 hours ago. Over the last 7 full days the hours up number 80 of 168, 48%. The first row Rust Data holds for it is dated 3 October 2026.
In which location is KOVCHEG TEST 3500 hosted?
There is no region published for KOVCHEG TEST 3500. Rust Data does not look up where the machine stands; it shows where a server says it is. 92.38.92.203:28015 is its address.
Settings and map
What rules and settings are recorded for KOVCHEG TEST 3500?
The name KOVCHEG TEST 3500 carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on KOVCHEG TEST 3500?
KOVCHEG TEST 3500 runs a procedural map of size 3,500 with seed 369217113, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does KOVCHEG TEST 3500 wipe, and how often?
No next wipe can be predicted for KOVCHEG TEST 3500, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 2 days 20 hours ago.
What is wipe day on KOVCHEG TEST 3500 like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain KOVCHEG TEST 3500?
On Rust Data, KOVCHEG TEST 3500 appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on KOVCHEG TEST 3500?
The game's server browser reads these tags from KOVCHEG TEST 3500: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to KOVCHEG TEST 3500?
In Rust, F1 opens the console: type client.connect 92.38.92.203:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. https://vk.ru/rustkovcheg is the website recorded for it.