[EA]Japan-Server |PvP|
Online EA 133.117.73.110:28015 checked 9m ago
Measurements
Players
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 25% of all ranked servers, top 67% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 09:00 UTC, in 7h. Its biweekly schedule tag · low confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 24 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 09:00 UTC13d ago | 2 | – | running | 0 |
| Thu 1 Oct, 18:55 UTC FW28d ago | 4 | halved by day 1 | 14.6 days | 0 |
| Wed 16 Sep, 13:05 UTC43d ago | 0 | – | 15.2 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.
Quick answers
Player counts
How does [EA]Japan-Server |PvP| rank against other Rust servers?
Seven-day player hours put [EA]Japan-Server |PvP| at #5,498, or #362 in Asia, inside the top 25% of all ranked servers.
How busy is [EA]Japan-Server |PvP|?
The count reads 0 players on [EA]Japan-Server |PvP|, which has 100 slots. Averaged over seven days, it drew 0 players and reached a peak of 3. The busiest hour in the last 48 was 05:00 UTC, when an average of 1 players were on.
Lists and tags
What do the server tags on [EA]Japan-Server |PvP| mean?
What the game's server browser reads from [EA]Japan-Server |PvP| is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is left blank; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; EA (East Asia): Its place in the server browser is under East Asia. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include [EA]Japan-Server |PvP|?
These Rust Population lists include [EA]Japan-Server |PvP|: Modded Rust servers, counted. Filter the server list by Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks and it will show up.
Wipe notes
What does wipe day look like on [EA]Japan-Server |PvP|?
Averaged over recent wipes, 2 players were counted at the busiest point. Peak came 24 hours into the latest wipe. In 0% of recent wipes, half the peak was held until the next wipe. In those that did not hold, the fall below half came by day 1.
What is the wipe schedule on [EA]Japan-Server |PvP|?
Its tag sets the prediction: too few of [EA]Japan-Server |PvP|'s wipes are on record to confirm the schedule. Due on Friday 30 October at 09:00 UTC is its next wipe. Counted from 13 days 16 hours ago, that is how long the current world has stood. Its tags set out a wipe schedule of one wipe every two weeks.
Map and rules
Which map does [EA]Japan-Server |PvP| run?
A procedural map of size 4,096 from seed 1337, generated by the game, is in use on [EA]Japan-Server |PvP|. You can look at it on RustMaps from this page: size and seed determine the map. The name on the map is Custom Map.
What are the rules and settings on [EA]Japan-Server |PvP|?
The name tells you nothing about gather rates: [EA]Japan-Server |PvP| states none. The group limit is 8 players, which is the default. survival is what it runs, raid, build and gather: the standard game. You can raid and fight other players here. Modded is its browser category: plugins or settings change the game. Oxide plugins are in use here. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does [EA]Japan-Server |PvP| run?
Rust network protocol 2635 and build 168909 on Linux is what [EA]Japan-Server |PvP| uses. Your game needs the same protocol to join; Steam takes care of updating it.
Does [EA]Japan-Server |PvP| run smoothly?
It ran at 106 server fps on average over the last 48 hours, and never went below 52. Entities peaked at 101,145, including buildings, deployables and everything else. Memory use peaked at 3,186 MB. Players feel lag when fps is low and the entity count climbs.
Is [EA]Japan-Server |PvP| online, and how reliable is it?
[EA]Japan-Server |PvP| is up and running at the moment. About 3 hours ago, it restarted, according to its uptime. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.
Where is [EA]Japan-Server |PvP| located?
The EA tag is how [EA]Japan-Server |PvP| places itself in Asia. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 133.117.73.110:28015.
Getting in
How do I join [EA]Japan-Server |PvP|?
To connect directly, open Rust's console with F1 and type client.connect 133.117.73.110:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://discord.com/invite/473S8yCnC7.