Online133.117.73.141:28015checked 8m ago
Rust_JP_workers
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 UTC11d 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 wipesQuick answers
from the figures on this pageSettings and map
Which rules govern Rust_JP_workers?
No gather rate appears in the name of Rust_JP_workers. Groups are capped at 8 players, the default in the game. survival is the game mode, gather, build, raid: the standard game. PvP and raiding are enabled. The server browser lists it as Modded, with plugins or settings that alter the game. Plugins: Oxide. VAC is on, Valve's anti-cheat.
Which map is running on Rust_JP_workers?
A procedural map of size 3,500 is what Rust_JP_workers runs, generated by the game with seed 1337. The map is identical for the same size and seed, so it can be viewed on RustMaps from this page. The name of its map is: Custom Map.
Server tags
Where can Rust_JP_workers be found in Rust Player Count lists and filters?
The Rust Player Count lists that Rust_JP_workers fits are: 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.
What is the meaning of the tags on Rust_JP_workers?
For the game's server browser, Rust_JP_workers publishes: gmrust (Game mode): Survival as standard in Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the standard game limit; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): It appears under Modded because plugins or settings modify the game. At the top of this page, its tags show its current players, queue and world creation time as well.
Player count
How many players does Rust_JP_workers have?
With 50 slots, Rust_JP_workers has 0 players at the moment. With a peak of 2, the average over seven days is 0 players. The busiest time in the last 48 hours was 10:00 UTC, with an average of 1 players.
Where does Rust_JP_workers sit in the rankings?
For player hours in the last seven days, Rust_JP_workers ranks #4,244 and is in the top 19% of all ranked servers.
Server details
What is the uptime and reliability of Rust_JP_workers?
Right now, Rust_JP_workers is up. The uptime it gives suggests it restarted about 3 hours ago. In the last 7 full days, it was up for 168 of 168 hours, which is 100% uptime. Rust Player Count recorded it for the first time on 13 September 2026.
What Rust version is used on Rust_JP_workers?
On Linux, Rust_JP_workers runs Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam updates it for you.
What is the location of Rust_JP_workers?
No region is published by Rust_JP_workers. The location shown by Rust Player Count is the one a server provides; it does not verify where the machine actually is. It is located at 133.117.73.141:28015.
What is the performance like on Rust_JP_workers?
Over the last 48 hours, the average server fps was 84, and it never dropped below 58. The highest entity count was 78,889, covering buildings, deployables and all other objects. Peak memory use was 2,500 MB. What players perceive as lag comes from low fps and a rising entity count.
Wipe schedule
What changes on Rust_JP_workers on wipe day?
Recent wipes saw an average peak of 1 players. 1 hours after the latest wipe, the crowd hit its peak. Half that peak was maintained until the next wipe in 0% of recent wipes. Otherwise, it dropped below half by day 1.
How often does Rust_JP_workers wipe?
With irregular wipe times on Rust_JP_workers, no next wipe is possible to predict. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. The present world dates from 11 days 19 hours ago.
Connect to the server
How can I connect to Rust_JP_workers?
To get in, press F1 in Rust and enter client.connect 133.117.73.141:28015. You can also click Launch Rust here, which opens the game through Steam and brings you onto the server. https://discord.com/invite/WtZuSsCm7a is 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.