Rust_JP_workers
Offline 133.117.73.141:28015 checked 2d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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.
Wipes
newest first| 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 UTC34d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 106/500
- 135/100
- 163/225
- 67/700
- 206/700
- 345/350
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Rust_JP_workers?
At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.
When does Rust_JP_workers wipe?
No next wipe can be predicted for Rust_JP_workers, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 26 days 17 hours ago.
Tags
How should you read the tags on Rust_JP_workers?
Tags published by Rust_JP_workers, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Rust_JP_workers appear in Rust Metrics lists and filters?
On Rust Metrics, Rust_JP_workers sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does Rust_JP_workers hold among Rust servers?
Player hours over seven days put Rust_JP_workers at #15,289, in the top 69% of all ranked servers.
How full does Rust_JP_workers get?
Reading for Rust_JP_workers: offline at this moment; last seen 2 days 3 hours ago. A seven-day average of 0 players is the reading.
Server
Where does Rust_JP_workers sit?
Reading: location. Rust_JP_workers gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 133.117.73.141:28015.
What Rust version is Rust_JP_workers on?
Reading: Rust_JP_workers, Rust network protocol 2634 and build 166652, Linux. To get in, your game needs the same protocol; Steam applies the update.
Is Rust_JP_workers up, and how often does it stay up?
Reading: offline. Rust_JP_workers last answered 2 days 3 hours ago. Uptime for the last 7 full days: 137 of 168 hours, or 82%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What settings and rules apply on Rust_JP_workers?
Reading the name gives no gather rate for Rust_JP_workers. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Rust_JP_workers?
Size 3,500 and seed 1337: the game generates the procedural map on Rust_JP_workers from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.
Connection
How do you connect to Rust_JP_workers?
Press F1 in Rust and enter client.connect 133.117.73.141:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/WtZuSsCm7a.