Players
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Tuesday 3 November, 21:47 UTC, in 6d 2h. Its weekly schedule tag · low confidence
Coming wipes
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 21:47 UTC21h ago | – | – | running | 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.
Similar servers
Quick answers
Server details
Is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 online, and how reliable is it?
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 is up as you read this. The uptime it reports puts its last restart about 46 minutes ago. 24 of 24 hours is what it managed over the past 1 full day, 100% of the time. Its earliest entry with Rust Charts dates from 26 October 2026.
Where is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 located?
No region tag is published by [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27, but its name points to Asia. Where a server says it is — that's what Rust Charts shows, without checking the machine's real location. You'll find it at 1.34.205.31:28015.
Which version of Rust does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 run?
The build behind [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 is Rust network protocol 2635 and build 168909, hosted on Windows. Joining needs the same protocol on your game; Steam handles the update.
Does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 run smoothly?
The 48-hour average was 107 server fps; the lowest point was 58. Buildings, deployables and all the rest of the world came to as many as 123,236 entities. Memory use peaked at 3,919 MB. Rising entity counts and low fps are the source of the lag players report.
Who is on
How busy is [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 has 0 of its 100 slots filled right now. Over the last week it averaged 1 players; the high point was 4. The busiest stretch of the last 48 hours came at 06:00 UTC, averaging 4 players.
How does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 rank against other Rust servers?
In the seven-day player hours table, [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 is #5,261, inside the top 24% of all ranked servers.
Wipes and resets
What is the wipe schedule on [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
The record holds too few of [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27's wipes to confirm the schedule, so the tag drives the prediction. The wipe after this one is due Tuesday 3 November at 21:47 UTC. The world in play was made 21 hours. Its tags carry a wipe schedule of once a week.
Rules and world
What are the rules and settings on [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 goes by its name: gather rate 2x. Up to 8 players per group, as the game sets by default. survival is the game mode, gather, build and raid in the standard game. PvP is on: players fight and raid. In the server browser it is under Community, being a community server. Oxide plugins are running on it. The server describes itself as vanilla: this is plain Facepunch Rust, with no rate or kit changes. Premium status is required to get in. VAC is on: that is Valve's anti-cheat.
Which map does [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 run?
[HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 runs a procedural map of size 3,500 with seed 1955700823, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Tags explained
Which Rust Charts lists and filters include [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
The Rust Charts lists that carry [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 are: 2x Rust server charts, Rust community servers, unmodded and Vanilla Rust servers. These filters on the server list bring it up: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Weekly ^w, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 2x.
What do the server tags on [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 mean?
These are the tags [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27 makes public, and the server browser reads them: gmrust (Game mode): Standard survival rules apply; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, as the game ships it; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): This server reports build 168909; ptrak (Networking): RakNet handles the network, as standard for the game; $r? (Region code): The region code is unset; ^w (Weekly): A wipe comes each week; ^v (Vanilla): This is plain Facepunch Rust, with no rate or kit changes; ^q (Premium): Premium status is required to get in; ^o (Oxide): This server uses Oxide (uMod) for plugins. At the top of this page you'll see the tags' extra details: players now, the queue, and the age of the world.
Getting in
How do I join [HK/JP] YJ Rust | 2x Vanilla | Weekly | AutoUpdate 10/27?
The console is behind F1 in Rust: enter client.connect 1.34.205.31:28015 there. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. Premium status is required to get in. You can find its website at https://discord.com/invite/6dHFqxsRYZ.
