On the class lists: F (12), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,326top 69%
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,326 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 70 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
24/ 100
F
Lost ground: down 7,943 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
····WW·
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
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
The first 48 hours of its last wipes
Sat 3 OctFri 2 OctSat 26 Sep
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 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
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Rust_JP_workers. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 133.117.73.141:28015.
Is Rust_JP_workers up, and how steady is its uptime?
The server is down: Rust_JP_workers is offline now, with the last sighting 45 hours ago. About 3 days 18 hours ago, it restarted, based on the uptime it reports. It was up 137 of 168 hours over the last 7 full days, which is 82% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does Rust_JP_workers run?
It averaged 70 server fps over the last 48 hours, with a low of 66. Up to 79,019 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,355 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Rust_JP_workers running?
You will find Rust_JP_workers on Rust network protocol 2634 and build 166652, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Rust_JP_workers reset?
Rust_JP_workers wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 26 days 11 hours have passed since this world was made.
What should you expect from wipe day on Rust_JP_workers?
Recent wipes have peaked at 1 players on average. 1 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does Rust_JP_workers sit among Rust servers?
Over the last seven days, Rust_JP_workers has #15,326 for player hours, in the top 69% of all ranked servers.
Is Rust_JP_workers a busy server?
The last sighting of Rust_JP_workers was 45 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Tags and filters
What do Rust_JP_workers's tags stand for?
You'll see Rust_JP_workers tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Rust_JP_workers?
Rust Server Score lists that include Rust_JP_workers: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Rust_JP_workers?
The name of Rust_JP_workers gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Rust_JP_workers runs which map?
Rust_JP_workers runs a game-generated procedural map at size 3,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Connecting
What is the way to join Rust_JP_workers?
To connect, start Rust, press F1, and type client.connect 133.117.73.141:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/WtZuSsCm7a.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.
A term to build on. Strongest in performance (A+); population is the one to work on (F).