Skip to the page
Network live 11,865 servers online 95,534 players aboard 381 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Rust_JP_workers

Offline 133.117.73.141:28015 checked 1d ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 26d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 50 players now 0% full
07-day averagepeak –
#15,341ranktop 69%
26d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

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.

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.

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.

0.7 daysusual gapbetween real wipes
33%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse 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.

Wipes

every wipe as a delivery, newest first
  1. Sat 3 Oct, 02:26 UTC 03:26 UK · 26d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Fri 2 Oct, 20:17 UTC 21:17 UK · 26d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.3 days
    Players before
    0
  3. Sat 26 Sep, 09:52 UTC 10:52 UK · 33d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    6.4 days
    Players before
    0
  4. Fri 25 Sep, 18:04 UTC 19:04 UK · 33d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.7 days
    Players before
    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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 150 on average 171 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 120 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average 186 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average 80 / 700
  5. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 87 on average 255 / 700
  6. RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average 350 / 350
Help desk

Quick answers

From the figures on this page.

Player count

Where does Rust_JP_workers place among Rust servers?

In the top 69% of all ranked servers sits Rust_JP_workers, at #15,341 on hours played over seven days.

How many players are on Rust_JP_workers right now?

At the moment Rust_JP_workers is offline, having last been seen 47 hours ago. For the last seven days the average player count was 0.

Server rules

What is the current map on Rust_JP_workers?

Generated by the game with seed 1337, the procedural map on Rust_JP_workers is size 3,500. Size and seed match means the map matches, so you can view it on RustMaps from this page. You will see this map name: Custom Map.

What are the rules on Rust_JP_workers, and what settings does it run?

The name of Rust_JP_workers gives no gather rate. 8 players is the group limit, since the game's default applies. survival is the mode, the usual game: build, gather, raid. Fighting and raiding between players is allowed. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Oxide. The VAC anti-cheat from Valve is enabled.

Operator and location

What is the location of Rust_JP_workers?

No region is published by Rust_JP_workers. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. 133.117.73.141:28015 is its address.

Is Rust_JP_workers up, and how good is its uptime?

The current status for Rust_JP_workers is offline, last seen 47 hours ago. It was up 137 of 168 hours over the last 7 full days, 82% of the time. 13 September 2026 is when Rust Wipe Tracker first recorded it.

On what Rust version does Rust_JP_workers operate?

The version on Rust_JP_workers is Rust network protocol 2634 and build 166652, running on Linux. Steam keeps your game updated; it has to be on the same protocol to join.

Map resets

What happens on Rust_JP_workers when wipe day arrives?

1 players is the average peak across its recent wipes. 1 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 1 it had fallen below half where the crowd did not hold.

How often does Rust_JP_workers wipe, and at what times?

Rust_JP_workers wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. The world it is running was made 26 days 13 hours.

Server tags

On Rust Wipe Tracker, which lists and filters is Rust_JP_workers part of?

You will find Rust_JP_workers on the following Rust Wipe Tracker lists: Modded Rust servers. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What is the meaning of the server tags on Rust_JP_workers?

Read off the game's server browser, the tags for Rust_JP_workers are: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Team limit: 8, the standard default; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Getting started

What steps do you take to join Rust_JP_workers?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 133.117.73.141:28015. Its website can be found at 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 standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit Team limit: 8, the standard default.
v2634
Protocol To join, your game must match protocol 2634.
cs166652
Build Build number: 166652.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded Plugins or settings alter the game, so it's 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.