Rust Data LabData lab · live
Live readings Servers11,634 Players41,075 Populated2,828 Fresh wipes · 3h109 Sampled every 5 min

Element card · group Modded · atomic number 15,270, its rank

Rust_JP_workers

Offline 133.117.73.141:28015 checked 2d ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak –
Rank · atomic number#15,270top 69%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.7 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sat 3 OctFri 2 OctSat 26 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 02:26 UTC27d ago 1 – running 0
Fri 2 Oct, 20:17 UTC27d 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 UTC34d 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
  1. 1 Sh ShockRust | Bl… 19
    ShockRust | Blue | NoLimit no group limit · 151 on average 19/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 126
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 126/ 100
  3. 3 Re RETRO RUST #1 … 51
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average 51/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 9
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average 9/ 700
  5. 5 Ru 404 RUST 2Х|ДЛ… 29
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average 29/ 700
  6. 6 Ru RustSpain.com … 49
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 49/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on Rust_JP_workers?

A procedural map of size 3,500 with seed 1337 runs on Rust_JP_workers, generated by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page. On the map name: Custom Map.

What settings and rules apply on Rust_JP_workers?

No gather rate appears in the name of Rust_JP_workers. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. Raids and player fights are part of play here. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins are running on it. Anti-cheat is on: Valve's VAC.

Server facts

What region hosts Rust_JP_workers?

There is no region on record for Rust_JP_workers. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 133.117.73.141:28015 is the address it uses.

On what Rust version does Rust_JP_workers operate?

Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How dependable is Rust_JP_workers for staying online?

Rust_JP_workers is not online at the moment; the last sighting was 2 days 12 hours ago. For the last 7 full days, 113 of 168 hours were online, giving 67% uptime. On 13 September 2026, Rust Data Lab saw it for the first time.

Wipe days

How often does a wipe happen on Rust_JP_workers, and at what time?

With no fixed rhythm, Rust_JP_workers wipes at irregular times, so the next wipe cannot be predicted. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 27 days 1 hours ago.

How does Rust_JP_workers look on the day of a wipe?

Averaged across its recent wipes, the busiest point drew 1 players. Peak numbers on the latest wipe came 1 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. Where it did not hold, the crowd dropped below half by day 1.

Where it appears

How should you read the tags on Rust_JP_workers?

The game's server browser reads the tags Rust_JP_workers publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it lists under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does Rust_JP_workers come up?

You will find Rust_JP_workers on the following Rust Data Lab lists: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does Rust_JP_workers hold among Rust servers?

The seven-day player-hours table has Rust_JP_workers at #15,270, in the top 69% of ranked servers.

How many players does Rust_JP_workers have at the moment?

No live signal from Rust_JP_workers right now, which was last seen 2 days 12 hours ago. The past week gives an average of 0 players.

Getting on

What is the way to join Rust_JP_workers?

In Rust, press F1 and enter client.connect 133.117.73.141:28015. Or click Launch Rust here to open Rust via Steam and connect automatically. For more, visit https://discord.com/invite/WtZuSsCm7a.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players 50 is the slot count.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166652
Build Build number: 166652.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.