Rust_JP_workers
Online 133.117.73.141:28015 checked 10m 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Server tags
Can you explain the tags on Rust_JP_workers?
Here are the tags Rust_JP_workers lists, which the game's browser uses: gmrust (Game mode): The standard survival game mode; mp50 (Max players): 50 player slots; ts8 (Group limit): Teams cap at 8, the standard game limit; v2634 (Protocol): To join, your game version must line up with protocol 2634; cs166652 (Build): Build 166652; ptrak (Networking): This is the standard RakNet layer the game uses; $r? (Region code): The region code is left blank; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded: plugins or settings change how it plays. Tags also carry its current players, its queue and when the world was made, all up top on this page.
On Rust Vending Machine, which lists and filters can you find Rust_JP_workers in?
These Rust Vending Machine lists include Rust_JP_workers: Modded Rust servers. 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.
Map and rules
What map is in play on Rust_JP_workers?
Rust_JP_workers runs a procedural map of size 3,500 with seed 1337, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page. The map goes by: Custom Map.
Which settings and rules apply on Rust_JP_workers?
There is no gather rate in the name Rust_JP_workers. 8 players is the default group size, and that is the cap here. You play survival, gather, build, raid: the standard game. Player versus player combat and raiding are on. Plugins or settings change the game, so it is listed under Modded. Oxide plugins are running on it. VAC is on.
About the server
What location is Rust_JP_workers in?
You will find no region published for Rust_JP_workers. Rust Vending Machine displays the location a server gives and does not look up the machine's true place. You can reach it at 133.117.73.141:28015.
How stable is Rust_JP_workers, and is it currently online?
The shelves show Rust_JP_workers in stock and online right now. By its own uptime report, the last restart was about 9 hours ago. Across the last 7 days, it was available for 168 of 168 hours, or 100% of the time. Its first record on Rust Vending Machine is dated 13 September 2026.
How well does Rust_JP_workers perform?
Over the last 48 hours the average server fps was 81, with a low of 58. The entity count reached 78,978: that includes buildings, deployables and everything else. Memory use peaked at 2,500 MB. The feel of lag traces back to fps dropping and entities piling up.
What version does Rust_JP_workers use?
On Linux, Rust_JP_workers is running Rust network protocol 2634 and build 166652. The protocol has to line up on your side to join, and Steam does the updating.
Player count
How does Rust_JP_workers compare to other Rust servers in the rankings?
The last seven days of player hours place Rust_JP_workers at #4,231, in the top 19% of all ranked servers.
How many players are on Rust_JP_workers right now?
Right now 50 slots in Rust_JP_workers hold 0 players. The seven-day average is 0, and the busiest point reached 2. Its busiest point in the last 48 hours was 10:00 UTC, averaging 1 players.
Wipe schedule
On what schedule does Rust_JP_workers wipe?
No next wipe can be predicted for Rust_JP_workers, which wipes at irregular times. When the monthly force wipe arrives on Thursday 5 November at 19:00 UTC, every Rust server wipes. It has been running its current world since 12 days ago.
How does Rust_JP_workers handle wipe day?
An average of 1 players turned up at the peak of its recent wipes. On the latest wipe, 1 hours after it began, the crowd peaked. Half the peak was kept until the next wipe in 0% of its recent wipes. The crowd fell under half by day 1 in the wipes that did not hold.
Join the server
What is the way to join Rust_JP_workers?
In the Rust console (F1), type client.connect 133.117.73.141:28015. You can also press Launch Rust on this page, which opens Steam and connects. Head to https://discord.com/invite/WtZuSsCm7a for its website.
Server tags
what each one meansPublished 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.