StatusLive Servers online11,836 Players72,948 Populated3,667 Wiped · 3 h218 Interval5 min Date29 OCT 2026

DWG RG-S15326Server sheetchecked 1d ago

Rust_JP_workers

Offline 133.117.73.141:28015 checked 1d ago

moddedoxide
Connect
Players now 0/ 50 0% full
7-day average0peak –
Rank#15,326top 69%
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123414:0015:0016:00

Hourly average and peak, UTC.

Fig. 1Players on Rust_JP_workers
Fig. 2

Server performance

02040608014:0015:0016:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 149 on average
183 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
128 / 100
03
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
83 / 700
04
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
23 / 200
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
28 / 1000
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average
267 / 700
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

How reliable is Rust_JP_workers, and is it online now?

The current state of Rust_JP_workers is offline, with the last sighting 45 hours ago. Counted from its reported uptime, the last restart was about 3 days 18 hours ago. For the last 7 full days the record is 137 of 168 hours up, 82% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is Rust_JP_workers stable in the figures recorded?

70 server fps on average over the last 48 hours, and never under 66. Counted at its highest: 79,019 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,355 MB. A climbing entity count and low fps are the source of what players feel as lag.

In which location is Rust_JP_workers hosted?

There is no region published by Rust_JP_workers. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 133.117.73.141:28015.

What Rust version is recorded for Rust_JP_workers?

The platform is Linux and the version is Rust network protocol 2634 and build 166652 on Rust_JP_workers. The same protocol is required for joining, and Steam updates your game to it.

Population

How many players are plotted on Rust_JP_workers?

The latest refresh records Rust_JP_workers as offline, last seen 45 hours ago. The seven-day mean on this server is 0 players.

What rank has been recorded for Rust_JP_workers?

Within the top 69% of all ranked servers: Rust_JP_workers at #15,326 for player hours, seven days recorded.

Wipe times

On Rust_JP_workers, what does the data show for wipe day?

At their busiest, its recent wipes drew 1 players on average. At 1 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. In the other cases the crowd was below half by day 1.

What wipe schedule has been recorded for Rust_JP_workers?

There is no next wipe to predict at Rust_JP_workers, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 26 days 11 hours ago.

Map and rules

What settings and rules apply on Rust_JP_workers?

Gather rate for Rust_JP_workers: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

What is the map for Rust_JP_workers?

Size 3,500 with seed 1337: that is the procedural map Rust_JP_workers runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Custom Map.

Tags

Where does Rust_JP_workers appear among the Rust Graphs lists and filters?

These Rust Graphs lists include Rust_JP_workers: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meaning is attached to each tag on Rust_JP_workers?

The game's server browser reads these tags from Rust_JP_workers: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): Build: 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

How is Rust_JP_workers joined?

Enter client.connect 133.117.73.141:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://discord.com/invite/WtZuSsCm7a is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players Slots: 50.
ts8
Group limit Teams are capped at 8, the default setting.
v2634
Protocol Join only if your game is on protocol 2634.
cs166652
Build Build: 166652.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed 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.

KeyTag string decoded