Station XX-15269 · no signal
Rust_JP_workers
Offline 133.117.73.141:28015 checked 2d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,269
- top 68%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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 68% 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.
- usual gap
- 0.7 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 02:26 UTC26d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 2 Oct, 20:17 UTC27d ago | M0.0▲rising | 1 | – | 0.3 days | 0 | |
| Sat 26 Sep, 09:52 UTC33d ago | M0.0▲rising | 1 | halved by day 1 | 6.4 days | 0 | |
| Fri 25 Sep, 18:04 UTC34d ago | M0.0■steady | 1 | – | 0.7 days | 1 |
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 pageRules and settings
Which map is running on Rust_JP_workers?
Generated by the game, the map on Rust_JP_workers is procedural, size 3,500 with seed 1337. Size and seed produce the same map, so RustMaps can show it from this page. You will find the map named Custom Map.
Which settings and rules apply on Rust_JP_workers?
No gather rate appears in the name of Rust_JP_workers. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on Rust_JP_workers right now?
Rust_JP_workers is not responding at this moment and is offline, last seen 2 days 4 hours ago. The seven-day average for this server is 0 players.
How does Rust_JP_workers rank against other Rust servers?
On player hours for the past week, Rust_JP_workers sits at #15,269, which puts it inside the top 68% of every ranked server.
Operator and location
How reliably does Rust_JP_workers stay online?
Rust_JP_workers is down at the moment; the last recorded contact was 2 days 4 hours ago. 137 of 168 hours in the last 7 full days were up time, 82% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does Rust_JP_workers run from?
No region is published by Rust_JP_workers. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 133.117.73.141:28015.
What build of Rust does Rust_JP_workers use?
On Linux, Rust_JP_workers runs Rust network protocol 2634 and build 166652. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on Rust_JP_workers?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.
How often does Rust_JP_workers wipe, and on which days?
No next wipe can be predicted for Rust_JP_workers, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 26 days 18 hours is how long the current world has been running.
Server tags
What do the server tags on Rust_JP_workers mean?
Tags published by Rust_JP_workers and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): Game build: 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Rust_JP_workers appear?
These Rust Server Trends lists include Rust_JP_workers: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to Rust_JP_workers?
You can connect by pressing F1 in Rust and typing client.connect 133.117.73.141: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/WtZuSsCm7a 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.