Rust HeatmapInfrared · players
IR live Players41,101 Servers11,642 Warm2,829 Fresh wipes · 3h110 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–50° · slots

Rust_JP_workers

Offline 133.117.73.141:28015 checked 2d ago

moddedoxide
Sp1 · players now 0/ 50
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,270
rank
top 69%
27d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 2d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server 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.

Li4Rank

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.

Bx1Wipe 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 days
usual gap
between real wipes
33%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
0%
crowd held
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 151 on average
19 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
126 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 122 on average
49 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 97 on average
9 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 94 on average
28 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
28 / 200

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on Rust_JP_workers?

At their busiest, its recent wipes averaged 1 players. 1 hours into the latest wipe, player numbers topped out. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 1 when it did not hold.

What is the wipe schedule on Rust_JP_workers?

Wipes come at irregular times on Rust_JP_workers, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 27 days 1 hours ago.

Player counts

How busy is Rust_JP_workers?

The last time Rust_JP_workers was seen was 2 days 12 hours ago, and it is offline now. The average across the last seven days is 0 players.

How does Rust_JP_workers rank against other Rust servers?

Player hours over seven days put Rust_JP_workers at #15,270, in the top 69% of ranked servers.

Rules and settings

Which map does Rust_JP_workers run?

Rust_JP_workers runs a procedural map of size 3,500 with seed 1337, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map. The map is called Custom Map.

What are the rules and settings on Rust_JP_workers?

No gather rate appears in the name Rust_JP_workers. The group limit is 8 players, which is the game's default. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. In the server browser it is Modded, meaning plugins or settings modify the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.

About the server

Which version of Rust does Rust_JP_workers run?

The build on Rust_JP_workers is Rust network protocol 2634 and build 166652, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.

Is Rust_JP_workers online, and how reliable is it?

Last seen 2 days 12 hours ago, Rust_JP_workers is offline right now. 113 of 168 hours up over the last 7 full days, which is 67%. It first appears in Rust Heatmap records on 13 September 2026.

Where is Rust_JP_workers located?

A region is not published for Rust_JP_workers. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 133.117.73.141:28015 is its address.

Tags

Which Rust Heatmap lists and filters include Rust_JP_workers?

These Rust Heatmap lists include Rust_JP_workers: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more brings it up.

What do the server tags on Rust_JP_workers mean?

These are the tags Rust_JP_workers publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp50 (Max players): The slot count is 50; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs166652 (Build): Build 166652; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

Connect

How do I join Rust_JP_workers?

Enter client.connect 133.117.73.141:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you. The server's site sits at https://discord.com/invite/WtZuSsCm7a.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard rules.
mp50
Max players The slot count is 50.
ts8
Group limit The game default applies: 8 per team at most.
v2634
Protocol The server runs game protocol 2634, so your game has to match it.
cs166652
Build Build 166652.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Settings or plugins alter the game, which puts it 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.