WRK15335
Rust_JP_workers
Offline 133.117.73.141:28015 checked 1d 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 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 UTC33d 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.
-
01MODPlayers 172/500
-
02MODPlayers 130/100
-
03MODPlayers 133/225
-
04MODPlayers 78/700
-
05MODPlayers 48/200
-
06MODPlayers 242/700
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry Rust_JP_workers?
These Rust Tracker lists carry Rust_JP_workers: Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Rust_JP_workers?
The game's server browser reads these tags from Rust_JP_workers: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Schedule
What happens on Rust_JP_workers on wipe day?
Recent wipes averaged a peak of 1 players. The peak on the latest wipe came 1 hours after it. The crowd stayed above half the peak until the next wipe in 0% of recent wipes. The fall below half came by day 1 where it did not hold.
Which wipe times are confirmed for Rust_JP_workers?
Irregular wipe times at Rust_JP_workers: there is no next wipe to predict. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 26 days 12 hours since this world was made.
Server Details
What is the uptime on Rust_JP_workers, and is it online?
Offline: Rust_JP_workers confirmed offline, last seen 46 hours ago. The uptime it reports puts the last restart about 3 days 18 hours ago. Uptime stood at 82% for the last 7 full days, 137 of 168 hours online. First contact for Rust Tracker: 13 September 2026.
Which Rust version is confirmed on Rust_JP_workers?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. To join, your game must be on the same protocol; Steam handles the update.
How smoothly does Rust_JP_workers run?
Average server fps over the last 48 hours: 72, with a low of 66. Peak entity count: 78,508, covering buildings, deployables and all else in the world. It drew as much as 3,277 MB of memory. A climbing entity count and low fps are what register as lag for players.
What location is Rust_JP_workers hosted in?
Region: none published by Rust_JP_workers. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 133.117.73.141:28015.
Player Count
What is the player count on Rust_JP_workers?
Last seen 46 hours ago; Rust_JP_workers is offline at present. Seven-day average for this server: 0 players.
Where does Rust_JP_workers sit in the server rankings?
Seven-day player hours put Rust_JP_workers at #15,335, within the top 69% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on Rust_JP_workers?
Nothing in Rust_JP_workers's name states a gather rate. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build, raid, as the game intends. Fighting and raiding between players are on. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.
Which map is confirmed for Rust_JP_workers?
A procedural map of size 3,500 runs on Rust_JP_workers, generated by the game from seed 1337. Same size, same seed, same map. RustMaps shows it, linked from this page. Its map goes by the name Custom Map.
Connect
How do you get onto Rust_JP_workers?
To connect: start Rust, press F1, enter client.connect 133.117.73.141:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://discord.com/invite/WtZuSsCm7a.
Server tags
What each one means.
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.