A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
66/ 100
C+
Working its way up from the back of the class: #7,512 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
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
46/ 100
D
Slipped a little: down 609 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); wipes are 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 34% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·····W·
·······
W······
·······
····
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 gap12.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3.5
The first 48 hours of its last wipes
Mon 12 OctSat 3 OctFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 20:30 UTC16d ago
1
–
running
0
Sat 3 Oct, 15:02 UTC25d ago
1
halved by day 3
9.2 days
0
Fri 18 Sep, 00:36 UTC41d ago
1
halved by day 4
15.6 days
0
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 Nitram's Rust server | Powered by AMP based in?
No region is published for Nitram's Rust server | Powered by AMP. Rust Server Score takes the server's word for its location and does not trace the hardware. 68.107.148.131:28015 is the address to use.
How dependable is Nitram's Rust server | Powered by AMP, and is it online at the moment?
Right now, Nitram's Rust server | Powered by AMP is online. It was up 86% of the time over the last 7 full days, 144 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is Nitram's Rust server | Powered by AMP on?
You will find Nitram's Rust server | Powered by AMP on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Nitram's Rust server | Powered by AMP reset?
No next wipe can be predicted for Nitram's Rust server | Powered by AMP, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 16 days 4 hours.
What should you expect from wipe day on Nitram's Rust server | Powered by AMP?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 3.5 is when it sank below half in the wipes that did not hold.
Population
Where does Nitram's Rust server | Powered by AMP place in the wider field of Rust servers?
In the top 34% of all ranked servers, Nitram's Rust server | Powered by AMP sits at #7,512 for player hours over the last seven days.
How many players does Nitram's Rust server | Powered by AMP usually have?
Right now, 0 players are on Nitram's Rust server | Powered by AMP, which has 10 slots. Averaging 0 players over seven days, it peaked at 1.
Lists and filters
How should you read the tags on Nitram's Rust server | Powered by AMP?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags Nitram's Rust server | Powered by AMP publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Nitram's Rust server | Powered by AMP?
These Rust Server Score lists count Nitram's Rust server | Powered by AMP among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does Nitram's Rust server | Powered by AMP enforce, and what are its settings?
The name of Nitram's Rust server | Powered by AMP gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Nitram's Rust server | Powered by AMP uses?
Nitram's Rust server | Powered by AMP runs a procedural map, which the game generates.
Getting in
What is the way to join Nitram's Rust server | Powered by AMP?
To connect, start Rust, press F1, and type client.connect 68.107.148.131:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 uptime (A+); wipes are the one to work on (F).