On the class lists: C (64), with population over 48 hours and no performance mark.
Players now2/ 405% full
7-day average2peak 6
Rank#2,533top 11%
Last wipe1d agoweekly schedule
Next wipe5d 1hMon 2 Nov, 20:03 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
4/ 100
F
A quiet classroom so far: 2 of 40 on average. Plenty of space to grow.
Standingrank on player hours
89/ 100
A−
Holds a respectable place: #2,533 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
74/ 100
B−
Slows down under load at times: 44 server fps on average.
Wipeskeeping the crowd after a wipe
80/ 100
B+
Holds its players well after a wipe: 80% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 58 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in uptime (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
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 11% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
W······
W··F···
W······
W······
W······
W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Monday 2 November, 20:03 UTC, in 5d 1h.
Every Monday at 20:03 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak5players, last three wipes
crowd held80%else halves by day 3
Coming wipes
5d 1hMon 2 Nov, 20:03 UTC
8d 0hThu 5 Nov, 19:00 UTCFW
12d 1hMon 9 Nov, 20:03 UTC
19d 1hMon 16 Nov, 20:03 UTC
26d 1hMon 23 Nov, 20:03 UTC
33d 1hMon 30 Nov, 20:03 UTC
36d 0hThu 3 Dec, 19:00 UTCFW
40d 1hMon 7 Dec, 20:03 UTC
The first 48 hours of its last wipes
Mon 19 OctMon 12 OctMon 5 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 20:03 UTC1d ago
–
–
running
1
Mon 19 Oct, 20:04 UTC8d ago
5
halved by day 3
7 days
1
Mon 12 Oct, 20:05 UTC15d ago
5
✓ held half
7 days
1
Mon 5 Oct, 20:04 UTC22d ago
6
✓ held half
7 days
2
Thu 1 Oct, 18:10 UTCFW27d ago
5
✓ held half
4.1 days
3
Mon 28 Sep, 20:04 UTC29d ago
7
✓ held half
2.9 days
2
Mon 21 Sep, 20:03 UTC36d ago
9
✓ held half
7 days
2
Mon 14 Sep, 20:04 UTC43d ago
6
✓ held half
7 days
4
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
Which region is Nuclear Cargo/Oil Trainer based in?
You'll find no region listed by Nuclear Cargo/Oil Trainer. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 72.73.28.150:28040 is the address to use.
How dependable is Nuclear Cargo/Oil Trainer, and is it online at the moment?
You can join now: Nuclear Cargo/Oil Trainer is online. The uptime it reports puts the last restart at about 44 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Is Nuclear Cargo/Oil Trainer smooth to play on?
It never fell below 33 server fps in the last 48 hours, averaging 44. Buildings, deployables and everything else in the world added up to as many as 30,868 entities. Memory use reached up to 3,999 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Nuclear Cargo/Oil Trainer running?
Rust network protocol 2635 and build 168909 on Linux is what Nuclear Cargo/Oil Trainer runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Nuclear Cargo/Oil Trainer wipe, and how often?
The wipe rhythm on Nuclear Cargo/Oil Trainer is every Monday at 20:03 UTC. Monday 2 November at 20:03 UTC is the date set for its next wipe. It has been running its current world for 46 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on Nuclear Cargo/Oil Trainer?
The average peak on its recent wipes was 5 players. The crowd on the latest wipe was largest 23 hours after it began. Above half the peak until the next wipe: that was the pattern in 80% of its recent wipes. In the other wipes it slipped under half by day 3.
Player numbers
What position does Nuclear Cargo/Oil Trainer hold in the rankings?
In the top 11% of all ranked servers, Nuclear Cargo/Oil Trainer sits at #2,533 for player hours over the last seven days.
How many players does Nuclear Cargo/Oil Trainer usually have?
Nuclear Cargo/Oil Trainer is showing 2 players right now, with 40 slots in total. The seven-day average is 2 players, with a peak of 6. The highest average in the last 48 hours came at 20:00 UTC, with 4 players.
Tags
How should you read the tags on Nuclear Cargo/Oil Trainer?
The game's browser takes its cue from the tags Nuclear Cargo/Oil Trainer has set: gmvanilla (Game mode): You play vanilla survival here; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^e (Minigames): It hosts minigames such as arenas, Bedwars and parkour; ^d (Combat training): Practise aim and PvP, loot provided; ^i (Battlefield): Kits and high rates drive the fast PvP here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who is behind Nuclear Cargo/Oil Trainer?
A nucleargaming.io hostname is published by Nuclear Cargo/Oil Trainer and by 3 other tracked servers, which suggests one operator.
Which Rust Server Score filters and lists feature Nuclear Cargo/Oil Trainer?
Rust Server Score lists that include Nuclear Cargo/Oil Trainer: Modded Rust servers, graded, Rust combat training servers, graded and Rust battlefield servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Weekly ^w, Minigames ^e, Combat training ^d, Battlefield ^i, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days.
Server rules
Which rules does Nuclear Cargo/Oil Trainer enforce, and what are its settings?
You will find no gather rate in the name of Nuclear Cargo/Oil Trainer. With no change from the game default, groups take up to 8 players. minigames & battle royale is the mode here, battle royale, arenas, parkour and Bedwars. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Nuclear Cargo/Oil Trainer uses?
A procedural map of size 2,100 and seed 1337, generated by the game, is what Nuclear Cargo/Oil Trainer runs. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
Getting in
What is the way to join Nuclear Cargo/Oil Trainer?
To connect, start Rust, press F1, and type client.connect 72.73.28.150:28040. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://nuclearrust.net.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^z,^y,^w,^e,^d,^i,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Gameplay
^e
MinigamesIt hosts minigames such as arenas, Bedwars and parkour.
^d
Combat trainingPractise aim and PvP, loot provided.
^i
BattlefieldKits and high rates drive the fast PvP here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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 steady term. Strongest in uptime (A+); population is the one to work on (F).