Rust_JP_workers
Key statistics
the figures behind the quote- Players now
- 0/ 50 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 2
- Rank
- #4,242 top 19%
- Rank · 7d ago
- #5,308 ▲1066 places up
- Last wipe
- 11d ago no schedule published
- Next wipe
- – no rhythm it keeps
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 83 player hours, last seven days
- Map
- 3500 Custom Map · seed 1337
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 2 players.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keeps- usual gap
- 0.7 days between real wipes
- on rhythm
- 33% of its recent wipes
- wipe-day peak
- 1 players, last three wipes
- crowd held
- 0% else halves by day 1
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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 02:26 UTC11d ago | 1 | – | running | 0 |
| Fri 2 Oct, 20:17 UTC11d ago | 1 | – | 0.3 days | 0 |
| Sat 26 Sep, 09:52 UTC18d ago | 1 | halved by day 1 | 6.4 days | 0 |
| Fri 25 Sep, 18:04 UTC19d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 145/300 | ▲+70+93.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 193/225 | ▲+73+60.4% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+1+1.2% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 30/1000 | ▼−31−50.8% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 18/1000 | ▼−1−4.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 58/700 | ▼−1−1.7% |
Quick answers
from the figures on this pageMap and Rules
How is Rust_JP_workers configured in terms of rules and settings?
No gather rate is given in the name of Rust_JP_workers. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.
Which map is played on Rust_JP_workers?
The map on Rust_JP_workers is procedural, size 3,500, with seed 1337, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page. The name of the map reads: Custom Map.
Population
What is the rank of Rust_JP_workers?
In the top 19% of all ranked servers, Rust_JP_workers is #4,242 on player hours over the last seven days.
What is the population on Rust_JP_workers?
0 of 50 slots on Rust_JP_workers are filled at the moment. Average players over seven days: 0; peak: 2. The busiest hour in the last 48 hours was 10:00 UTC, with an average of 1 players.
Wipe Schedule
What happens on wipe day at Rust_JP_workers?
The average peak across its recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. Below half by day 1 is where the crowd fell when it did not hold.
When does Rust_JP_workers schedule its wipes?
Rust_JP_workers wipes at times that do not follow a pattern, so no next wipe can be predicted. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 11 days 16 hours ago the current world was created.
Server Info
What is the location of Rust_JP_workers?
No region is published by Rust_JP_workers. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 133.117.73.141:28015 is its address.
Is Rust_JP_workers performing well?
The last 48 hours average 85 server fps, the low being 58. At its peak it held 78,843 entities: buildings, deployables and the rest of the world. Memory use peaked at 2,500 MB. Low fps and growing entities are the source of felt lag.
Rust_JP_workers runs which version of Rust?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of Rust_JP_workers?
Rust_JP_workers is up. It is taking players now. Its own uptime figure dates the last restart to roughly 33 minutes ago. 7 full days have passed with 100% uptime, 168 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.
Tags and Rankings
How should you interpret the tags on Rust_JP_workers?
These tags are published by Rust_JP_workers and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): Slot count: 50; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): To join, your game needs protocol 2634; cs166652 (Build): Build 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Rust_JP_workers appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature Rust_JP_workers: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connection
How can I connect to Rust_JP_workers?
Type client.connect 133.117.73.141:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. For more information, go to https://discord.com/invite/WtZuSsCm7a.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp50
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^o
^z
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.