Rust HeatmapInfrared · players
IR live Players97,865 Servers11,882 Warm3,914 Fresh wipes · 3h398 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–100° · slots

[Uz/Ru/Kz] #2 UzRust - Classic

Online EA 213.230.109.15:28025 checked 8m ago

biweekly wipes vanillamoddedoxide
Sp1 · players now 0/ 100
0% full
Li1 · players, the last 48 hours · hourly average, UTC
Tue 17:00flare: a wipe in that hourThu 15:00
0
7-day average
peak 2
#9,700
rank
top 43% · #428 in EA
27d ago
last wipe
biweekly schedule
2h
next wipe
Thu 29 Oct, 18:57 UTC
UTC checked 8m ago

Li2Players

AveragePeak
0123417:0002:0011:0021:0006:0015:00

Hourly average and peak, UTC.

Li3Server performance

010020030040017:0002:0011:0021:0006:0015: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.

Li4Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 43% of all ranked servers, top 79% in EA. Ranked on player hours over the last seven days.

Bx1Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 18:57 UTC, in 2h. Its biweekly schedule tag · low confidence

14.3 days
usual gap
between real wipes
2
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

Coming wipes

2h
Thu 29 Oct, 18:57 UTC
7d 2h
Thu 5 Nov, 19:00 UTC
FW
14d 2h
Thu 12 Nov, 18:57 UTC
28d 2h
Thu 26 Nov, 18:57 UTC
35d 2h
Thu 3 Dec, 19:00 UTC
FW
42d 2h
Thu 10 Dec, 18:57 UTC

The first 48 hours of its last wipes

Thu 1 OctThu 17 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:57 UTC FW27d ago 1 – running 0
Thu 17 Sep, 12:48 UTC42d ago 2 held half 14.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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
[JP]初心者PVPサーバー|RaidTime・ Events
EA · groups of 10+ · biweekly · 15 on average
9 / 100
[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29
EA · no group limit · biweekly · 4 on average
1 / 20
瞌睡熊『5倍10废|10.29|萌新首选|无权限』
EA · groups of 8+ · biweekly · 4 on average
3 / 100
[JP/PvE][BPリサーチ]MatoyServer初しん者〇
EA · groups of 8+ · biweekly · 2 on average
0 / 50
[JPN] Apple Server | PvP | Vanilla | 2Weekly
EA · groups of 8+ · biweekly · 2 on average
1 / 50
cczsbwd/solo/独狼/原倍半月清/月图/公益服
EA · no group limit · biweekly · 2 on average
1 / 50

LogQuick answers

from the figures on this page

Wipe schedule

What does wipe day look like on [Uz/Ru/Kz] #2 UzRust - Classic?

The average peak across its recent wipes is 2 players. The crowd on the latest wipe reached its peak 3 hours in. Half the peak was held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on [Uz/Ru/Kz] #2 UzRust - Classic?

Its tag guides the prediction because [Uz/Ru/Kz] #2 UzRust - Classic's wipe record is too thin to confirm the schedule. Thursday 29 October at 18:57 UTC is when its next wipe is due. 27 days 21 hours ago the server made the world it is on now. Its tags state a wipe every two weeks.

Player counts

How busy is [Uz/Ru/Kz] #2 UzRust - Classic?

The current population of [Uz/Ru/Kz] #2 UzRust - Classic is 0, against 100 slots. A seven-day average of 0 players, with a peak of 2.

How does [Uz/Ru/Kz] #2 UzRust - Classic rank against other Rust servers?

On player hours over the last seven days, [Uz/Ru/Kz] #2 UzRust - Classic is #9,700 globally (top 43%) and #428 in Asia.

Map and rules

Which map does [Uz/Ru/Kz] #2 UzRust - Classic run?

A procedural map of size 3,000 with seed 1974910435, generated by the game, runs on [Uz/Ru/Kz] #2 UzRust - Classic. The map is the same for a given size and seed, so RustMaps can show it from this page.

What are the rules and settings on [Uz/Ru/Kz] #2 UzRust - Classic?

The name [Uz/Ru/Kz] #2 UzRust - Classic does not specify a gather rate. 8 players is the default group size, and that is the limit here. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Oxide. Vanilla is the server's own description: unchanged rates, kits and rules: the game in Facepunch's own form. Anti-cheat: Valve's VAC is on.

Server details

Which version of Rust does [Uz/Ru/Kz] #2 UzRust - Classic run?

The build on [Uz/Ru/Kz] #2 UzRust - Classic is Rust network protocol 2634 and build 167781, running on Windows. To join, your game must match the protocol; Steam handles the update.

Is [Uz/Ru/Kz] #2 UzRust - Classic online, and how reliable is it?

Right now [Uz/Ru/Kz] #2 UzRust - Classic shows as online. The uptime it reports puts the last restart at about 7 days 13 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. It first appears in Rust Heatmap records on 13 September 2026.

Where is [Uz/Ru/Kz] #2 UzRust - Classic located?

With its EA tag, [Uz/Ru/Kz] #2 UzRust - Classic lists itself in Asia. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 213.230.109.15:28025.

Does [Uz/Ru/Kz] #2 UzRust - Classic run smoothly?

It averaged 189 server fps over the last 48 hours, with a low of 164. Entities peaked at 45,123, counting buildings, deployables and all the rest of the world. At its peak it held 6,214 MB of memory. What players call lag is low fps together with a growing entity count.

Tags

Which Rust Heatmap lists and filters include [Uz/Ru/Kz] #2 UzRust - Classic?

The Rust Heatmap lists that [Uz/Ru/Kz] #2 UzRust - Classic fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Region: Asia; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

What do the server tags on [Uz/Ru/Kz] #2 UzRust - Classic mean?

gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): The slot count is 100; ts8 (Group limit): At most 8 per team: the default the game ships with; v2634 (Protocol): Your game must match protocol 2634 to get in; cs167781 (Build): This build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^b (Biweekly): It wipes on a two-week cycle; ^v (Vanilla): Unchanged rates, kits and rules: the game in Facepunch's own form; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Listed as Modded, since settings or plugins change the game; EA (East Asia): East Asia is where the server browser puts it are the tags [Uz/Ru/Kz] #2 UzRust - Classic publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Connect

How do I join [Uz/Ru/Kz] #2 UzRust - Classic?

To join by console, open it with F1 in Rust and enter client.connect 213.230.109.15:28025. Or press Launch Rust on this page, which connects you through Steam. https://uzrust.uz is where its website is.

KeyServer tags

what each one means

Published as mp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust form.
mp100
Max players The slot count is 100.
ts8
Group limit At most 8 per team: the default the game ships with.
v2634
Protocol Your game must match protocol 2634 to get in.
cs167781
Build This build is 167781.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Wipe schedule

^b
Biweekly It wipes on a two-week cycle.

Difficulty

^v
Vanilla Unchanged rates, kits and rules: the game in Facepunch's own form.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Listed as Modded, since settings or plugins change the game.

Region

EA
East Asia East Asia is where the server browser puts it.

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.