Rust_JP_workers
Offline 133.117.73.141:28015 checked 1d 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 02:26 UTC26d ago | 1 | – | running | 0 |
| Fri 2 Oct, 20:17 UTC26d ago | 1 | – | 0.3 days | 0 |
| Sat 26 Sep, 09:52 UTC33d ago | 1 | halved by day 1 | 6.4 days | 0 |
| Fri 25 Sep, 18:04 UTC33d ago | 1 | – | 0.7 days | 1 |
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 Rust_JP_workers rank against other Rust servers?
Over the past week it ranks #15,335 for player hours, which puts Rust_JP_workers in the top 69% of all ranked servers.
How busy is Rust_JP_workers?
Rust_JP_workers is offline at this count; we last saw it 46 hours ago. A seven-day average of 0 players was counted here.
Lists and tags
What do the server tags on Rust_JP_workers mean?
The game's server browser reads the tags Rust_JP_workers publishes: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): Plugins or settings change the game; it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include Rust_JP_workers?
Rust_JP_workers appears among the Rust Population lists that follow: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.
Wipe schedule
What does wipe day look like on Rust_JP_workers?
Across its recent wipes the busiest crowds averaged 1 players. 1 hours after the latest wipe the crowd peaked. In 0% of recent wipes, half the peak was held until the next wipe. The crowd dropped below half by day 1 when it did not hold.
What is the wipe schedule on Rust_JP_workers?
No next wipe can be predicted for Rust_JP_workers, which wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 26 days 11 hours ago.
Settings
Which map does Rust_JP_workers run?
The map on Rust_JP_workers is procedural, made by the game at size 3,500 from seed 1337. Size and seed together fix the map, so you can view it on RustMaps from this page. You will see the map named Custom Map.
What are the rules and settings on Rust_JP_workers?
Nothing in Rust_JP_workers's name says how gather works. No limit is set beyond the standard 8 players per group. You get survival here, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does Rust_JP_workers run?
On Linux, Rust_JP_workers runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam updates it for you.
Does Rust_JP_workers run smoothly?
In the last 48 hours, it averaged 72 server fps, with a low of 66. The entity count reached 78,508: buildings, deployables and all other objects. The highest memory usage was 3,277 MB. Players feel lag when fps is low and the entity count climbs.
Is Rust_JP_workers online, and how reliable is it?
We last saw Rust_JP_workers 46 hours ago, and it is offline now. The uptime it reports suggests a restart roughly 3 days 18 hours ago. Over the last 7 full days, 137 of 168 hours were online, or 82%. The first sighting by Rust Population was on 13 September 2026.
Where is Rust_JP_workers located?
No region is published by Rust_JP_workers. 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.141:28015.
How to join
How do I join Rust_JP_workers?
Open the console with F1 in Rust and enter client.connect 133.117.73.141:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you. For more, visit its website: https://discord.com/invite/WtZuSsCm7a.