Working its way up from the back of the class: #16,269 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 485 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll find no region listed by nmg-cycle. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 100.61.123.117:28015.
How reliable is nmg-cycle, and is it up?
The server is down: nmg-cycle is offline now, with the last sighting 34 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 25 September 2026, Rust Server Score saw it for the first time.
Which Rust version is nmg-cycle running?
Rust network protocol 2634 and build 165651 on Linux is what nmg-cycle runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does nmg-cycle reset?
There are too few wipes on record for nmg-cycle to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 34 days 12 hours have passed since this world was made.
Player count
Where does nmg-cycle place in the wider field of Rust servers?
In the top 71% of all ranked servers, nmg-cycle sits at #16,269 for player hours over the last seven days.
How many players does nmg-cycle usually have?
nmg-cycle is offline at the moment; the last time it was seen was 34 days 12 hours ago.
Tags
What is meant by the tags on nmg-cycle?
You'll see nmg-cycle tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs165651 (Build): This runs on build 165651; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show nmg-cycle?
These Rust Server Score lists count nmg-cycle among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is nmg-cycle set up, and what rules does it keep?
The name of nmg-cycle gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map nmg-cycle uses?
A procedural map, generated by the game, is what nmg-cycle runs.
How to join
How should you connect to nmg-cycle?
Enter client.connect 100.61.123.117:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs165651,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs165651
BuildThis runs on build 165651.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 momentum (D); standing is the one to work on (F).