[Uz/Ru/Kz] #2 UzRust - Classic
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 7m ago · 213.230.109.15:28025
Abstract
We describe the public Rust server [Uz/Ru/Kz] #2 UzRust - Classic, reached at 213.230.109.15:28025 and hosted in EA. At the last check it held 0 of 100 places, against a seven-day mean of 01. It ranks #15,290 of all servers, the top 69%, and #472 in EA. It last wiped 28d ago on a published biweekly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsbiweekly wipes vanilla modded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 69% of all ranked servers, the top 87% in EA. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: from its schedule tag
The next wipe is expected Thursday 5 November, 19:00 UTC, in 6d 19h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 14.3 days | between real wipes |
| Wipe-day peak | 2 | players, last three wipes |
| Crowd held | 100% | of its cycles kept half the crowd |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 6d 19h | force wipefw |
| Thu 12 Nov, 18:57 | 13d 19h | its own schedule |
| Thu 26 Nov, 18:57 | 27d 19h | its own schedule |
| Thu 3 Dec, 19:00 | 34d 19h | force wipefw |
| Thu 10 Dec, 18:57 | 41d 19h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 1 Oct, 18:57fw28d ago | 1 | – | running | 0 |
| Thu 17 Sep, 12:4842d ago | 2 | held half | 14.3 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 213.230.109.15:28025 |
|---|---|
| Region | EA |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | biweekly |
| Last wipe | 1 Oct 2026, 18:57 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3000 |
| Seed | 1974910435 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and predicted wipe schedule [3].
| Server | Players |
|---|---|
| [JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average | 1/100 |
| 瞌睡熊『5倍10废|10.30|萌新首选|无权限』EA · groups of 8+ · biweekly · 4 on average | 0/100 |
| [JPN] Apple Server | PvP | Vanilla | 2WeeklyEA · groups of 8+ · biweekly · 2 on average | 1/50 |
| [JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average | 2/50 |
| cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 2 on average | 1/50 |
| Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 78 on average | 101/200 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1Does [Uz/Ru/Kz] #2 UzRust - Classic perform well?
The server fps averaged 188 over the last 48 hours, never dropping below 164. Its entity count reached a maximum of 44,985, including buildings, deployables and all other world objects. Its highest memory usage was 6,214 MB. When fps is low and entity count climbs, players feel lag.
A.2What location does [Uz/Ru/Kz] #2 UzRust - Classic have?
In Asia, according to its own listing, [Uz/Ru/Kz] #2 UzRust - Classic appears with the EA tag. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 213.230.109.15:28025 is its address.
A.3What is the reliability of [Uz/Ru/Kz] #2 UzRust - Classic, and is it online?
[Uz/Ru/Kz] #2 UzRust - Classic is online at this time. The uptime it reports indicates a restart about 7 days 20 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. It was first observed on 13 September 2026 by Rust Statistics.
A.4What is the Rust version for [Uz/Ru/Kz] #2 UzRust - Classic?
Rust network protocol 2634 and build 167781 is the version that [Uz/Ru/Kz] #2 UzRust - Classic runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.5What schedule does [Uz/Ru/Kz] #2 UzRust - Classic follow for wipes?
Because too few wipes of [Uz/Ru/Kz] #2 UzRust - Classic are recorded to confirm the schedule, the tag governs the prediction. This server's next wipe coincides with the force wipe on Thursday 5 November at 19:00 UTC, which affects all Rust servers. The world currently in use was created 28 days 4 hours ago. Wipes every two weeks are published in the tags.
A.6How would you describe wipe day on [Uz/Ru/Kz] #2 UzRust - Classic?
Across its recent wipes, the average peak population was 2 players. The peak on the latest wipe came 3 hours after it began. The crowd stayed above half its peak until the next wipe in 100% of recent wipes.
Player count
A.7What is the rank of [Uz/Ru/Kz] #2 UzRust - Classic among Rust servers?
On player hours over seven days [Uz/Ru/Kz] #2 UzRust - Classic is #15,290, within the top 69% of all ranked servers; within Asia it is #472.
A.8What is the population level of [Uz/Ru/Kz] #2 UzRust - Classic?
The current population of [Uz/Ru/Kz] #2 UzRust - Classic is 0, drawn from 100 slots. The seven-day average for this server is 0 players.
Tags and filters
A.9What do the tags associated with [Uz/Ru/Kz] #2 UzRust - Classic signify?
The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): Build 167781 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): It wipes on a two-week cycle; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; EA (East Asia): East Asia is the region it appears under in the server browser, which [Uz/Ru/Kz] #2 UzRust - Classic publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.10Where can [Uz/Ru/Kz] #2 UzRust - Classic be found among the Rust Statistics lists and filters?
Modded Rust servers are the Rust Statistics lists that [Uz/Ru/Kz] #2 UzRust - Classic fits. You will find it on the server list filtered by: 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.
Rules, settings, map
A.11What are the settings and rules that govern [Uz/Ru/Kz] #2 UzRust - Classic?
No gather rate appears in the name of [Uz/Ru/Kz] #2 UzRust - Classic. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. By its own label, vanilla, this is the game as Facepunch ships it, with rates, kits and rules unaltered. VAC, Valve's anti-cheat, is enabled.
A.12On which map does [Uz/Ru/Kz] #2 UzRust - Classic take place?
The game generates [Uz/Ru/Kz] #2 UzRust - Classic's procedural map at size 3,000, from seed 1974910435. Equal size and seed yield an identical map, which this page offers to view on RustMaps.
Connection
A.13What is the process for joining [Uz/Ru/Kz] #2 UzRust - Classic?
Enter client.connect 213.230.109.15:28025 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. The website for this server is https://uzrust.uz.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs167781,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp100 | Max players. 100 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2634 | Protocol. The game protocol is 2634; your client must match it to join. |
cs167781 | Build. Build 167781 is the one running. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. No region code is set. |
| Wipe schedule | |
^b | Biweekly. It wipes on a two-week cycle. |
| Difficulty | |
^v | Vanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
| Region | |
EA | East Asia. East Asia is the region it appears under in the server browser. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.