Server profile
Rust_JP_workers
Offline, with 0 of 50 players on; ranked #15,335 of every public Rust server, the top 69%. It last wiped 26d ago.
Offline 133.117.73.141:28015 checked 1d ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 69% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
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.
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 02:26 UTC26d ago | 1 | – | running | 0 |
| Fri 2 Oct, 20:17 UTC26d 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 UTC33d ago | 1 | – | 0.7 days | 1 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
What does Rust_JP_workers look like once wipe day arrives?
The average busiest point of its recent wipes was 1 players. The peak crowd on this wipe came 1 hours after it started. In 0% of recent wipes, more than half the peak was still playing at the next wipe. In the other cases, it dropped below half by day 1.
On what schedule does Rust_JP_workers wipe?
No next wipe can be predicted for Rust_JP_workers, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. 26 days 11 hours have passed since its current world was created.
Server
Does Rust_JP_workers hold a steady frame rate?
Average server fps over the last 48 hours was 72, with a floor of 66. The world held a peak of 78,508 entities, counting buildings, deployables and all the rest. Memory use peaked at 3,277 MB. A climbing entity count and low fps are what players experience as lag.
Which Rust version is Rust_JP_workers on?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. Joining needs your game on the same protocol, which Steam updates for you.
What does uptime look like for Rust_JP_workers, and is it online?
Rust_JP_workers is offline at the moment; the last time it was seen was 46 hours ago. Going by the uptime figure it gives, its last restart was around 3 days 18 hours ago. It spent 137 of the last 7 full days' 168 hours up, 82% of the time. The first record Rust Insights has of it is 13 September 2026.
Where does Rust_JP_workers run from?
A region is not published by Rust_JP_workers. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 133.117.73.141:28015 is where it answers.
Server tags
What is meant by each tag on Rust_JP_workers?
These tags come from Rust_JP_workers and are read by the game's server browser: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): It holds 50 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2634 (Protocol): To join you need the same version; protocol 2634; cs166652 (Build): It runs game build 166652; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
On which Rust Insights lists does Rust_JP_workers appear?
These Rust Insights lists include Rust_JP_workers: Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
How many players are on Rust_JP_workers right now?
Rust_JP_workers is offline at the moment; the last sighting was 46 hours ago. Across the past week the mean was 0 players.
In the ranking of Rust servers, where does Rust_JP_workers place?
Player hours over seven days put Rust_JP_workers at #15,335, within the top 69% of the ranked field.
Map and rules
How is Rust_JP_workers configured, and what rules apply?
No gather rate appears in the name of Rust_JP_workers. Groups can reach 8 players, which is the default in the game. survival is the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. It is a Modded entry: plugins or settings modify the game. Plugins: Oxide run here. VAC is on: Valve's anti-cheat is active.
Which map is live on Rust_JP_workers?
Rust_JP_workers runs a procedural map of size 3,500 with seed 1337, generated by the game. You can look at the map on RustMaps from this page, since the same size and seed produce the same map. Read out, its map name is: Custom Map.
How to join
How do you connect to Rust_JP_workers?
Type client.connect 133.117.73.141:28015 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam. Its website can be found at https://discord.com/invite/WtZuSsCm7a.