Rust_JP_workers
133.117.73.141:28015 checked 7m 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 19% 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 UTC12d ago | 1 | – | running | 0 |
| Fri 2 Oct, 20:17 UTC12d ago | 1 | – | 0.3 days | 0 |
| Sat 26 Sep, 09:52 UTC18d ago | 1 | halved by day 1 | 6.4 days | 0 |
| Fri 25 Sep, 18:04 UTC19d 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
Quick answers
Server rules
Which settings and rules apply on Rust_JP_workers?
No gather rate appears in the name Rust_JP_workers. That is the game's default: groups of up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Raiding and fighting other players are allowed. This one sits under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running on it. VAC, Valve's anti-cheat, is switched on.
Which map is active on Rust_JP_workers?
A procedural map, size 3,500 with seed 1337, generated by the game, is what Rust_JP_workers runs. From this page, RustMaps can show it: size and seed produce the same map each time. Under map name you will find: Custom Map.
Population
How many players are on Rust_JP_workers?
The server Rust_JP_workers is currently at 0 players out of 50 slots. Averaging 0 players over seven days, it peaked at 2. The busiest time in the last 48 hours was 10:00 UTC, when it averaged 1 players.
What position does Rust_JP_workers hold in the server rankings?
In the top 19% of ranked servers, Rust_JP_workers holds #4,230 for player hours over the last seven days.
Tags and filters
What is the meaning of the tags on Rust_JP_workers?
For the game's server browser, Rust_JP_workers publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp50 (Max players): It holds 50 players; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): There's no region code here; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded listing means plugins or settings have changed the game. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.
Which Rust Zerg Life filters and lists cover Rust_JP_workers?
The Rust Zerg Life lists that include Rust_JP_workers are Modded Rust servers for clans and zergs. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server details
What is the uptime and reliability of Rust_JP_workers?
Rust_JP_workers is up and running as you read this. It reports an uptime that puts the last restart at roughly 8 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Rust Zerg Life has been tracking it since 13 September 2026.
How well does Rust_JP_workers perform?
Over the past 48 hours, server fps averaged 82 and never dropped below 58. It reached a maximum of 78,978 entities, covering buildings, deployables and the rest of the world. At its highest, memory usage hit 2,500 MB. What players experience as lag comes from low fps and a rising entity count.
Which Rust build does Rust_JP_workers use?
On Linux, Rust_JP_workers runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam will update your game to that protocol.
Where can you find Rust_JP_workers?
There is no region published by Rust_JP_workers. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 133.117.73.141:28015.
Wipe schedule
What can you expect on wipe day on Rust_JP_workers?
At their busiest, its recent wipes drew an average of 1 players. On the latest wipe, 1 hours after the wipe, the crowd hit its peak. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. Otherwise, it slipped below half by day 1.
How often does Rust_JP_workers wipe, and on what days?
No next wipe can be predicted for Rust_JP_workers because it wipes at irregular times. Come Thursday 5 November at 19:00 UTC, the monthly force wipe arrives for every Rust server. The world it is running now dates from 12 days ago.
Connect
What steps do I take to join Rust_JP_workers?
You can join by opening the console with F1 and typing client.connect 133.117.73.141:28015. Or hit Launch Rust on this page to open Rust through Steam and connect. You can find its website at https://discord.com/invite/WtZuSsCm7a.
Server tags
Published as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp50
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.