Rust Server IndexCard catalogue of Rust servers

Holdings11,897 servers102,621 players399 fresh wipes

Call no.15327 Off the shelf · offline

Rust_JP_workers

Offline 133.117.73.141:28015 checked 2d ago

Subjects 1. modded2. oxide
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,327
top 69%
Last wipeWiped3 OCT2026 · 26d 15h ago
26d ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

No hourly history yet.

Hourly average and peak, UTC.

Record sheet B · appended

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.

Record sheet C · appended

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.

Record sheet D · loan terms

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

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
3 OCT 2026Sat 3 Oct, 02:26 UTC26d ago
1 – running 0
2 OCT 2026Fri 2 Oct, 20:17 UTC26d ago
1 – 0.3 days 0
26 SEP 2026Sat 26 Sep, 09:52 UTC33d ago
1 halved by day 1 6.4 days 0
25 SEP 2026Fri 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.

Shelf list · shelved beside it

Similar servers

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

ShockRust | Blue | NoLimitno group limit · 151 on average
144/ 500
EU
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
131/ 100
EU
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
196/ 225
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
90/ 700
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average
226/ 700
EU
RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average
348/ 350
Reference desk

Quick answers

From the figures on this page.

Rules and settings

Where can you read the rules and settings that apply on Rust_JP_workers?

The name of Rust_JP_workers does not state a gather rate. 8 players per group is the default limit. The server runs survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. VAC, Valve's anti-cheat, is enabled.

Which map is in use on Rust_JP_workers?

Size 3,500, seed 1337: the game generates the procedural map on Rust_JP_workers. The map can be seen on RustMaps from this page, because the same size and seed give the same map. Filed under map name: Custom Map.

Tags

Which lists and filters on Rust Server Index is Rust_JP_workers filed under?

Filed under these Rust Server Index lists is Rust_JP_workers: Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which tags are attached to Rust_JP_workers, and what do they stand for?

These are the tags Rust_JP_workers publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): Player cap: 50; ts8 (Group limit): Teams cap at 8, the default setting; v2634 (Protocol): Joining needs you on game protocol 2634; cs166652 (Build): Build on file: 166652; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or changed settings put this under Modded. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipes and resets

What should you expect on Rust_JP_workers when wipe day comes?

The average peak across its recent wipes is 1 players. The latest wipe peaked 1 hours in. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 the crowd had fallen below half when it didn't hold.

Which wipe timetable does Rust_JP_workers follow?

No next wipe can be predicted for Rust_JP_workers: its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 26 days 15 hours.

Players and ranking

What position does Rust_JP_workers hold among Rust servers?

The seven-day player-hours ranking places Rust_JP_workers at #15,327, among the top 69% of ranked servers.

What does the player count on Rust_JP_workers look like?

At present Rust_JP_workers is offline; its last sighting was 2 days 1 hours ago. Averaged over the last seven days, the count is 0 players.

Server facts

What version does Rust_JP_workers use?

Rust network protocol 2634 and build 166652, on Linux, is what Rust_JP_workers runs. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of Rust_JP_workers?

Last seen 2 days 1 hours ago, Rust_JP_workers is offline right now. It was up 137 of 168 hours across the last 7 full days, or 82% of the time. The earliest sighting at Rust Server Index is 13 September 2026.

Where in the world is Rust_JP_workers hosted?

There is no region on record for Rust_JP_workers; it publishes none. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 133.117.73.141:28015.

Joining the server

How can you connect to Rust_JP_workers?

Two ways in. Type client.connect 133.117.73.141:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. The website can be found at https://discord.com/invite/WtZuSsCm7a.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp50
Max players Player cap: 50.
ts8
Group limit Teams cap at 8, the default setting.
v2634
Protocol Joining needs you on game protocol 2634.
cs166652
Build Build on file: 166652.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region code field is left empty.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Plugins or changed settings put this 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.