Station EA-1447 · recording
[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29
Online EA 162.43.55.237:28015 checked 13m ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 5
- peak 19
- Rank
- #1,447
- top 7% · #150 in EA
- Last wipe
- 11d ago
- biweekly schedule
- Next wipe
- 2d 0h
- Fri 30 Oct, 01:47 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- −5into Mon 06:00 UTC
- Peak · 48 h
- 7most players in any hour
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
daily · 1 is bestTop 7% of all ranked servers, top 27% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 01:47 UTC, in 2d 0h. Its biweekly schedule tag · low confidence
- usual gap
- 7.3 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 13players, last three wipes
- crowd held
- 50%else halves by day 11
Coming wipes
- 2d 0hFri 30 Oct, 01:47 UTC
- 8d 17hThu 5 Nov, 19:00 UTCFW
- 16d 0hFri 13 Nov, 01:47 UTC
- 30d 0hFri 27 Nov, 01:47 UTC
- 36d 17hThu 3 Dec, 19:00 UTCFW
- 44d 0hFri 11 Dec, 01:47 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 13, 32 hours in, with 1 in the queue.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 01:47 UTC11d ago | M1.1▲rising | 13+1 queue | – | running | 1 | |
| Thu 15 Oct, 16:09 UTC12d ago | M1.0▲rising | 13+1 queue | – | 0.4 days | 2 | |
| Fri 2 Oct, 11:20 UTC25d ago | M1.1▲rising | 12 | halved by day 11 | 13.2 days | 0 | |
| Fri 25 Sep, 03:27 UTC32d ago | M1.2▲rising | 16 | held half | 7.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29?
Generated by the game, the map on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 is procedural, size 3,500 with seed 14057. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29?
No gather rate appears in the name of [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29. It gives no group limit in its listing. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29?
At this moment, [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 records 0 players across 20 slots. Averaged across the last seven days the population was 5 players, reaching a peak of 19. Averaged over the last 48 hours, the busiest hour was 12:00 UTC at 6 players.
How does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 rank against other Rust servers?
The last seven days of player hours place [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 at #1,447, in the top 7% of all ranked servers and #150 in Asia.
Operator and location
How reliably does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 stay online?
As recorded now, [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 is running. The uptime it reports puts its last restart about 2 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 perform under load?
The 48-hour average is 127 server fps; 31 is the lowest observed. At its highest, it carried 95,537 entities: buildings, deployables and the world's other contents. It reached a ceiling of 2,879 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Where in the world is [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 hosted?
In Asia [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 lists itself, with the tag EA. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 162.43.55.237:28015.
What build of Rust does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 use?
On Linux, [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29?
On average, the busiest point of its recent wipes drew 13 players. With 1 more in the queue, the crowd on the latest wipe peaked 32 hours after the wipe. Until the next wipe the crowd remained above half that peak in 50% of its recent wipes. It fell under half by day 11 in the wipes where it didn't hold.
How often does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 wipe, and on which days?
The prediction follows its tag, because too few of [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29's wipes are on record to confirm its schedule. The date of its next wipe is Friday 30 October at 01:47 UTC. It has run its current world for 11 days 21 hours. In its tags it sets out a wipe schedule of every two weeks.
Tags
What do the server tags on [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 mean?
The game's server browser reads the tags [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 publishes: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; ts0 (Group limit): Team play is turned off; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): The server browser files it under East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 appear?
The Rust Server Trends lists that take in [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 are: Beginner Rust servers: live trends and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Join the server
How do you connect to [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29?
You can connect by pressing F1 in Rust and typing client.connect 162.43.55.237:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://discord.com/invite/7N9DeTMYHh is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.