Local forecast
Rust_JP_workers
Offline 133.117.73.141:28015 checked 1d ago
Current conditions
observed 1d agoplayers now
0% full
- 7-day average
- 0
- peak –
- Rank
- #15,323
- top 69%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
Next wipe
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 03:26 UKSat 3 Oct, 02:26 UTC · 26d ago | 1 | – | running | 0 |
| Fri 2 Oct, 21:17 UKFri 2 Oct, 20:17 UTC · 26d ago | 1 | – | 0.3 days | 0 |
| Sat 26 Sep, 10:52 UKSat 26 Sep, 09:52 UTC · 33d ago | 1 | halved by day 1 | 6.4 days | 0 |
| Fri 25 Sep, 19:04 UKFri 25 Sep, 18:04 UTC · 33d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
How smoothly does Rust_JP_workers run?
Its average over the last 48 hours was 72 server fps, and it never dropped below 66. Buildings, deployables and all else in the world took the entity count to a peak of 79,019. Memory use reached 3,355 MB at its peak. Players feel lag when fps drops and the entity count climbs.
How reliable is Rust_JP_workers, and is it online now?
Rust_JP_workers is currently offline, with the last sighting 43 hours ago. Going by its reported uptime, the last restart was about 3 days 18 hours ago. In the last 7 full days it stayed up 137 of 168 hours, 82% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
Where does Rust_JP_workers run from?
There is no published region for Rust_JP_workers. Rust Wipe Stats does not look up where the machine stands; it shows where the server says it is. 133.117.73.141:28015 is its address.
What version of Rust is running on Rust_JP_workers?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. To join you need the same protocol, and Steam handles the update.
Tags, lists and filters
Which meaning sits behind each tag on Rust_JP_workers?
The server browser reads these tags from Rust_JP_workers: gmrust (Game mode): The mode is plain Rust survival; mp50 (Max players): Capacity: 50; ts8 (Group limit): Teams are at the game default of 8; v2634 (Protocol): Game protocol 2634 applies; match it to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region field is left blank; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Modded is its category, with plugins or settings changing the game. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does Rust_JP_workers appear among the Rust Wipe Stats lists and filters?
These Rust Wipe Stats lists include Rust_JP_workers: Modded Rust servers. These filters on the server list will bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What map is Rust_JP_workers on?
The game generates the map on Rust_JP_workers, procedural, size 3,500, seed 1337. From this page RustMaps opens it, since equal size and seed give an equal map. You will see the map named Custom Map.
What settings does Rust_JP_workers use, and what rules does it enforce?
No gather rate appears in the name Rust_JP_workers. The default of 8 players is the group limit here. It plays as survival, gathering, building and raiding, as the game normally plays. Both PvP and raiding are on. The server browser lists it as Modded, where plugins or settings alter the game. Oxide are the plugin frameworks it runs. This server has VAC switched on.
Wipe schedule
Which days and times does Rust_JP_workers schedule its wipes for?
Rust_JP_workers keeps no regular rhythm, and its wipes fall at irregular times, so no next wipe can be named. A monthly force wipe hits every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 26 days 9 hours is how long the current world has been running.
What happens on Rust_JP_workers when wipe day arrives?
At their busiest, its recent wipes averaged 1 players. 1 hours after the latest wipe, the crowd hit its peak. 0% of recent wipes kept more than half the peak until the next wipe. The fall below half came by day 1 when the crowd did not hold.
Population history
Is Rust_JP_workers busy or quiet?
The last time Rust_JP_workers was seen was 43 hours ago; it is offline right now. The average for the past week is 0 players.
What position does Rust_JP_workers hold among Rust servers?
The last seven days of player hours rank Rust_JP_workers at #15,323, in the top 69% of ranked servers.
Join the server
How do you get into Rust_JP_workers?
Two ways in: press F1 and enter client.connect 133.117.73.141:28015, or join from this page with Launch Rust, which opens Steam and connects you. You can find its website at https://discord.com/invite/WtZuSsCm7a.