On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average0peak 1
Rank#11,022top 50%
Last wipe1d agoweekly schedule
Next wipe5d 20hTue 3 Nov, 17:09 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 150 on average. Plenty of space to grow.
Standingrank on player hours
50/ 100
D
Working its way up from the back of the class: #11,022 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
100/ 100
A+
Runs smoothly: 136 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
47/ 100
D
Slipped a little: down 709 places this week. Nothing a good wipe can't fix.
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
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 50% of all ranked servers, and #465 of the trio servers (top 74%). Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·W·····
·W·····
·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 Tuesday 3 November, 17:09 UTC, in 5d 20h.
Every Tuesday at 17:09 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
5d 20hTue 3 Nov, 17:09 UTC
7d 22hThu 5 Nov, 19:00 UTCFW
12d 20hTue 10 Nov, 17:09 UTC
19d 20hTue 17 Nov, 17:09 UTC
26d 20hTue 24 Nov, 17:09 UTC
33d 20hTue 1 Dec, 17:09 UTC
35d 22hThu 3 Dec, 19:00 UTCFW
40d 20hTue 8 Dec, 17:09 UTC
The first 48 hours of its last wipes
Tue 20 OctTue 13 OctTue 6 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 28 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 17:09 UTC1d ago
–
–
running
0
Tue 20 Oct, 17:08 UTC8d ago
1
halved by day 2
7 days
0
Tue 13 Oct, 17:07 UTC15d ago
1
halved by day 2
7 days
0
Tue 6 Oct, 15:45 UTC22d ago
1
halved by day 1
7.1 days
0
Tue 29 Sep, 17:13 UTC29d ago
1
halved by day 1
6.9 days
0
Tue 22 Sep, 17:08 UTC36d ago
1
halved by day 1
7 days
0
Tue 15 Sep, 17:07 UTC43d ago
1
halved by day 1
7 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
In what location does 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly sit?
You'll find no region listed by 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 91.99.37.118:27033.
How dependable is 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly, and is it online at the moment?
You can join now: 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly is online. According to its reported uptime, the last restart was about 23 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly perform well?
It never fell below 86 server fps in the last 48 hours, averaging 136. Buildings, deployables and everything else in the world added up to as many as 146,015 entities. Up to 5,777 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly running?
Rust network protocol 2635 and build 168909 on Linux is what 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly reset?
The wipe rhythm on 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly is every Tuesday at 17:09 UTC. It is due to wipe next on Tuesday 3 November at 17:09 UTC. It has been running its current world for 27 hours. The tags carry a weekly wipe schedule.
What happens on 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 28 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. In the other wipes it slipped under half by day 1.
Population
Where does 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly place in the wider field of Rust servers?
Over the last seven days, 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly has #11,022 for player hours, in the top 50% of all ranked servers. In the trio group, it ranks #465.
Is 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly a busy server?
With 150 slots available, 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly currently has 0 players. It peaked at 1 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 18:00 UTC, with an average of 0 players.
Lists and filters
What is meant by the tags on 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly?
The game's browser takes its cue from the tags 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly has set: gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): The server holds 150 slots; ts3 (Group limit): Teams cap out at 3; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 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; ^w (Weekly): Wipes come once a week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Rust Server Score filters and lists feature 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly?
These Rust Server Score lists count 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.
Server rules
How is 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly set up, and what rules does it keep?
The name of 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly points to a 2x gather rate. The cap on group size is 3 players (trio). survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly runs which map?
A procedural map of size 5,000 and seed 77462768, generated by the game, is what 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to 24HG No Mans Land 2x | Solo/Duo/Trio | No-BP | Weekly?
To connect, start Rust, press F1, and type client.connect 91.99.37.118:27033. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://alpha.24hgaming.com/games/rust/servers/no-mans-land/map.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2635,^w,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp150
Max playersThe server holds 150 slots.
ts3
Group limitTeams cap out at 3.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 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.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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).