- Players now
- 1/50 2% full
- 7-day average
- 0 peak 2
- Rank
- #4,423 ▲ 1651 this week
- Wiped
- 7d 14h ago · 3 Oct, 02:26 UTC
- Next wipe
- – no rhythm it keeps
- Team limit
- 8 no published schedule
Evaluation
six readings of the figures on this page, 0 to 100 each| Population0 of 50 on average | 1 | |
|---|---|---|
| Standing#4,423 on player hours | 81 | |
| Uptime47 of the last 48 hours | 98 | |
| Performance146 server fps on average | 100 | |
| Wipe hold0% of wipes kept half their crowd | 0 | |
| Momentumup 1,651 places this week | 69 |
The score is the average of the readings that have figures. Population is the seven-day average against the slots; standing is how near the top of the rank it is; uptime the hours of the last 48 on the list; performance its server fps, 60 or more counting as full; wipe hold the share of its recent wipes that kept half their crowd; momentum its rank against a week ago, 50 for no change. The tier is the rank alone: Titanium is the top 10, Master the top 50, Diamond 150, Platinum 400, Gold 1,000, Silver 2,500.
Population
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.
Wipe record
4 on recordIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- 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
| Date | Time | Peak | Lasted |
|---|---|---|---|
| 3 Oct | Sat 02:26 | 1 | running |
| 2 Oct | Fri 20:17 | 1 | 0.3 days |
| 26 Sep | Sat 09:52 | 1 | 6.4 days |
| 25 Sep | Fri 18:04 | 1 | 0.7 days |
Performance
48 hours: hourly readings. 30 to 90 days: a point a day, measured since 17 Sep. Low fps and a climbing entity count mean lag.
Rank history
daily · 1 is bestTop 19% of all ranked servers. Ranked on player hours over the last seven days.
Intel
- Map
- Custom Map
- Size
- 3500
- Seed
- 1337
- 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
Server tags
what each tag it publishes means ·mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z| Game | gmrust | Game mode Standard Rust survival is the game mode. |
mp50 | Max players The server holds 50. | |
ts8 | Group limit The default applies: 8 to a team. | |
v2634 | Protocol Your game must run protocol 2634. | |
cs166652 | Build This server runs build 166652. | |
ptrak | Networking The network layer is RakNet, standard for Rust. | |
$r? | Region code The region code is blank. | |
| Mods and access | ^o | Oxide Plugin framework: Oxide (uMod). |
^z | Modded Modded listing: plugins or settings make the difference. |
Flag meanings are Facepunch's.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 1Survivors.gg | 2 x Vanilla | Monthlygroups of 30+ · monthly · 134 on averageUnranked105/200
- 2ShockRust | Blue | NoLimitno group limit · 132 on averageUnranked322/400
- 3RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 9.10EU · groups of 16+ · weekly · 112 on averageUnranked197/225
- 4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 07.10EU · groups of 16+ · monthly · 111 on averageUnranked61/1000
- 5МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 91 on averageUnranked91/100
- 6STEEL RUST /ДЛЯ НОВИЧКОВ /EU Thursday 08.10EU · groups of 70+ · monthly · 89 on averageUnranked28/300
Briefing
quick answers, from the figures on this page01What is the rank position of Rust_JP_workers?
In the top 19% of all ranked servers, Rust_JP_workers holds #4,423 for player hours over the last seven days.
02How many players are on Rust_JP_workers right now?
Right now, 1 players occupy the 50 slots on Rust_JP_workers. Averaging 0 players over seven days, it peaked at 2. The 48-hour peak time is 09:00 UTC, when it averaged 2 players.
03What Rust version is Rust_JP_workers on?
Rust network protocol 2634 and build 166652 on Linux is what Rust_JP_workers runs. Joining requires your game to be on the same protocol; Steam handles the update.
04How smooth is the performance on Rust_JP_workers?
Server fps over the last 48 hours: 146 average, 48 lowest. Entities peaked at 78,288, including buildings, deployables and all other world objects. Memory usage reached 2,968 MB at its highest. Players feel lag when fps drops and entities climb.
05What is the host location for Rust_JP_workers?
No region is published by Rust_JP_workers. What Rust Server Now shows is a server's stated location, not where its machine is actually located. You reach it at 133.117.73.141:28015.
06Current online status and reliability of Rust_JP_workers: what is the data?
Rust_JP_workers reports online at this moment. About 3 hours ago was its last restart, based on reported uptime. Over the last 7 full days, 166 of 168 hours were online, or 99%. First seen by Rust Server Now on 13 September 2026.
07The tags on Rust_JP_workers: what do they mean?
The server browser reads these tags from Rust_JP_workers: gmrust (Game mode): Standard Rust survival is the game mode; mp50 (Max players): The server holds 50; ts8 (Group limit): The default applies: 8 to a team; v2634 (Protocol): Your game must run protocol 2634; cs166652 (Build): This server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for Rust; $r? (Region code): The region code is blank; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: plugins or settings make the difference. The tags also carry its live players, its queue and its world creation time, and those appear at the top of this page.
08On which Rust Server Now lists does Rust_JP_workers appear?
Rust_JP_workers appears on the following Rust Server Now lists: Modded Rust servers. Under these filters, it appears 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.
09Rust_JP_workers wipes on what schedule?
Wipes on Rust_JP_workers happen irregularly, leaving no next wipe to forecast. A monthly force wipe hits every Rust server; the next one is Thursday 5 November at 19:00 UTC. It has been running its current world for 7 days 14 hours.
10On wipe day, what changes for Rust_JP_workers?
1 players on average marked the busiest point of its recent wipes. The latest wipe saw its peak 1 hours in. The crowd held above half that peak until the next wipe in 0% of its recent wipes. If not, it dropped below half by day 1.
11The map for Rust_JP_workers: which one?
For Rust_JP_workers, the map is procedural at size 3,500 with seed 1337, generated by the game. Size and seed together determine the map, which can be viewed on RustMaps from this page. The name of the map is: Custom Map.
12Which rules apply on Rust_JP_workers, and what settings?
You will not find a gather rate in the name Rust_JP_workers. Up to 8 players can group, which is the game's default. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players is allowed. The server browser lists it as Modded: plugins or settings change the game. You will find Oxide plugins running here. VAC, Valve's anti-cheat, is enabled.
13What is the process to join Rust_JP_workers?
To connect, open Rust, press F1, and enter client.connect 133.117.73.141:28015. You can also click Launch Rust here to open the game via Steam and join. https://discord.com/invite/WtZuSsCm7a is where its website lives.