Offline 133.117.73.141:28015 checked 2d ago
Rust_JP_workers
Connect
srv = rust.server("133.117.73.141:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()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 wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 02:26 UTC26d ago | 1 | NaN | running | 0 |
| 1 | Fri 2 Oct, 20:17 UTC27d ago | 1 | NaN | 0.3 days | 0 |
| 2 | Sat 26 Sep, 09:52 UTC33d ago | 1 | halved by day 1 | 6.4 days | 0 |
| 3 | Fri 25 Sep, 18:04 UTC34d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3500 · seed 1337
- map
- Custom Map
- size
- 3500
- seed
- 1337
Server
srv.info()- address
- 133.117.73.141:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 02:26 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 15/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 8/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 38/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 143/200 |
Quick answers
From the figures on this page.
Population
How does Rust_JP_workers compare in the rankings?
Player hours over seven days put Rust_JP_workers at #15,284, in the top 69% of the ranked set.
How many players does Rust_JP_workers hold at once?
The current row shows Rust_JP_workers offline; the last response was 2 days 9 hours ago. Over the last seven days it averaged 0 players.
About the server
Which Rust version is Rust_JP_workers on?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Rust_JP_workers, and is it up?
Offline now for Rust_JP_workers, last seen 2 days 9 hours ago. 113 of 168 hours up over the last 7 full days, or 67%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Rust_JP_workers run from?
No region is published by Rust_JP_workers. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 133.117.73.141:28015.
Rules, settings, map
Which settings and rules does Rust_JP_workers run?
The name Rust_JP_workers carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Rust_JP_workers selected?
The game generates the map on Rust_JP_workers: procedural, size 3,500, seed 1337. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.
Wipe data
When does Rust_JP_workers wipe, and how often?
Irregular wipe times on Rust_JP_workers leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 26 days 23 hours ago, and that is the one in play.
What is wipe day on Rust_JP_workers like?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.
Lists and tags
Which Rust Data filters and lists contain Rust_JP_workers?
On Rust Data, Rust_JP_workers appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Rust_JP_workers hold?
These tags are published by Rust_JP_workers and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Rust_JP_workers?
In Rust, F1 opens the console: type client.connect 133.117.73.141:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://discord.com/invite/WtZuSsCm7a.