Rust StatisticsWorking papers on every public Rust server · 49,675 players now

Rust_JP_workers

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 2d ago · 133.117.73.141:28015

Abstract

We describe the public Rust server Rust_JP_workers, reached at 133.117.73.141:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,269 of all servers, the top 69%. It last wiped 26d ago.

Keywordsmodded oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,269top 69%
Last wipe26d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
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
Sat 3 OctFri 2 OctSat 26 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 3 Oct, 02:2626d ago 1 – running 0
Fri 2 Oct, 20:1727d ago 1 – 0.3 d 0
Sat 26 Sep, 09:5233d ago 1 halved by day 1 6.4 d 0
Fri 25 Sep, 18:0434d ago 1 – 0.7 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Rust_JP_workers
Figure 5: The map: Custom Map, size 3500, seed 1337.
Table 4: The server's published settings.
Address133.117.73.141:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe3 Oct 2026, 02:26 UTC
Hostname–
First seen13 Sep 2026
MapCustom Map
Size3500
Seed1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average15/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average33/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average4/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average15/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average128/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does Rust_JP_workers have?

A region is not published by Rust_JP_workers. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 133.117.73.141:28015.

A.2What is the online status and reliability of Rust_JP_workers?

Rust_JP_workers is currently offline, with the last sighting 2 days 10 hours ago. Of the 168 hours in the last 7 full days, 113 were served, an availability of 67%. The first record of it by Rust Statistics dates to 13 September 2026.

A.3What is the Rust version for Rust_JP_workers?

Rust network protocol 2634 and build 166652 is the version that Rust_JP_workers runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4On what cycle does Rust_JP_workers wipe?

Prediction of the next wipe is impossible for Rust_JP_workers, which wipes irregularly. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 26 days 23 hours have passed since the current world was generated.

A.5How would you describe wipe day on Rust_JP_workers?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 1 hours after the latest wipe. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. Otherwise, a fall below half took place by day 1.

Population

A.6What is the rank of Rust_JP_workers among Rust servers?

Ranked by player hours across seven days, Rust_JP_workers holds #15,269, in the top 69% of all ranked servers.

A.7How would you characterise the player activity on Rust_JP_workers?

The last recorded sighting of Rust_JP_workers was 2 days 10 hours ago; it is offline now. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.8What is the meaning of the tags on Rust_JP_workers?

Tags from Rust_JP_workers, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): This server runs game build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can Rust_JP_workers be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Rust_JP_workers fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.10Which settings and rules are in force on Rust_JP_workers?

Its name carries no gather rate for Rust_JP_workers. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.11On which map does Rust_JP_workers take place?

Generated by the game from seed 1337, the procedural map on Rust_JP_workers measures 3,500. Because size and seed determine the map, RustMaps can show it, linked from this page. The name of the map is Custom Map.

Connection

A.12What is the process for joining Rust_JP_workers?

Press F1 inside Rust to open the console and enter client.connect 133.117.73.141:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. The website for this server is https://discord.com/invite/WtZuSsCm7a.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp50Max players. 50 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Your game must run protocol 2634 to connect.
cs166652Build. This server runs game build 166652.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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.

Appendix CAbout this server, in its own words

[SERVER SPECIFICATIONS] - PvPvE Progress: Loot NPC/Bosses for Items. Crafting requires Blueprints. - Monument War: Fight other players to secure Boss kills and rare loot. - Housing Zone: Safe construction area available with No-Raid rules. - Skill System: Enhance various abilities based on your unique skill build.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.