Rust_JP_workers
Online 133.117.73.141:28015 checked 8m ago
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 25% 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 UTC15d ago | 1 | – | running | 0 |
| Fri 2 Oct, 20:17 UTC15d ago | 1 | – | 0.3 days | 0 |
| Sat 26 Sep, 09:52 UTC22d ago | 1 | halved by day 1 | 6.4 days | 0 |
| Fri 25 Sep, 18:04 UTC22d 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
- 17/ 100
- 294/ 400
- 180/ 225
- 127/ 100
- 410/ 1000
- 34/ 700
Quick answers
Tags and filters
Where does Rust_JP_workers appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Rust_JP_workers: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Rust_JP_workers?
gmrust (Game mode): This is the standard Rust survival experience; mp50 (Max players): The slot count is 50; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166652 (Build): This server runs build 166652; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Rust_JP_workers puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Is Rust_JP_workers lag-free?
Average server fps for the last 48 hours was 74, and the lowest was 45. The entity count reached a high of 79,364, covering buildings, deployables and everything else. 2,612 MB was the highest memory it used. Players experience lag when fps drops and entities climb.
What's the location of Rust_JP_workers?
There is no published region for Rust_JP_workers. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 133.117.73.141:28015.
What's the uptime like for Rust_JP_workers?
Rust_JP_workers is live as of this check. The uptime it gives puts the last restart at roughly 21 hours ago. In the last full 7 days, 168 of 168 hours were online, 100% uptime. The first sighting by Rust Going Deep was on 13 September 2026.
What Rust version is Rust_JP_workers on?
On Linux, Rust_JP_workers runs Rust network protocol 2634 and build 166652. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
How often does Rust_JP_workers wipe?
Rust_JP_workers wipes whenever it likes, so no next wipe can be predicted. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 15 days 10 hours ago.
What happens on wipe day at Rust_JP_workers?
Across its recent wipes, the average busiest point drew 1 players. On the latest wipe, 1 hours passed before the crowd peaked. Recent wipes kept the crowd above half that peak until the next wipe 0% of the time. By day 1, the pop had dropped under half.
Map and rules
Which rules and settings is Rust_JP_workers running?
No gather rate appears in the name of Rust_JP_workers. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Which map is active on Rust_JP_workers?
Rust_JP_workers uses a procedural map of size 3,500 with seed 1337, made by the game. RustMaps can display it from this page because the same size and seed yield the same map. It goes by the map name Custom Map.
Player stats
Is Rust_JP_workers busy?
Right now 0 players are on Rust_JP_workers, which has 50 slots. The seven-day average is 0 players, with a peak of 2. The busiest point in the last 48 hours was 14:00 UTC, averaging 1 players.
Where does Rust_JP_workers sit in the rankings?
Over the last seven days, Rust_JP_workers is #5,556 by player hours, among the top 25% of all ranked servers.
Getting in
What's the way to join Rust_JP_workers?
To join, open Rust, hit F1, and enter client.connect 133.117.73.141:28015. Or click Launch Rust on this page to open the game through Steam and connect. https://discord.com/invite/WtZuSsCm7a is its website.