Working its way up from the back of the class: #13,852 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,000 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in wipe hold (A+); 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.
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 64% of all ranked servers, and #356 of the duo servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
······W
·WWWW·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 gap1.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Tue 6 OctSun 4 OctFri 2 Oct
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
Tue 6 Oct, 14:35 UTC22d ago
1
–
running
1
Sun 4 Oct, 18:08 UTC24d ago
1
–
1.9 days
0
Fri 2 Oct, 17:17 UTC26d ago
1
✓ held half
2 days
1
Thu 1 Oct, 16:28 UTC27d ago
1
–
1 days
1
Wed 30 Sep, 22:10 UTC27d ago
1
–
0.8 days
1
Wed 30 Sep, 14:41 UTC28d ago
1
–
0.3 days
0
Tue 29 Sep, 16:58 UTC29d ago
1
–
0.9 days
1
Sun 27 Sep, 18:23 UTC31d ago
1
–
1.9 days
1
Thu 17 Sep, 18:32 UTC41d ago
1
–
10 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
Which region is Burn Rust OneGrid 2X solo/duo One Grid based in?
No region is published for Burn Rust OneGrid 2X solo/duo One Grid. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 46.148.179.40:28015 is the address to use.
How reliable is Burn Rust OneGrid 2X solo/duo One Grid, and is it up?
The server is down: Burn Rust OneGrid 2X solo/duo One Grid is offline now, with the last sighting 14 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 17 September 2026.
Which Rust version is Burn Rust OneGrid 2X solo/duo One Grid running?
Rust network protocol 2634 and build 166586 on Windows is what Burn Rust OneGrid 2X solo/duo One Grid runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Burn Rust OneGrid 2X solo/duo One Grid reset?
There is no next wipe to predict on Burn Rust OneGrid 2X solo/duo One Grid, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 22 days 5 hours.
What happens on Burn Rust OneGrid 2X solo/duo One Grid when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Player count
Where does Burn Rust OneGrid 2X solo/duo One Grid sit among Rust servers?
Over the last seven days, Burn Rust OneGrid 2X solo/duo One Grid has #13,852 for player hours, in the top 64% of all ranked servers. In the duo group, it ranks #356.
What does the population on Burn Rust OneGrid 2X solo/duo One Grid look like?
The last sighting of Burn Rust OneGrid 2X solo/duo One Grid was 14 days 3 hours ago, and it is offline right now.
Lists and filters
What do Burn Rust OneGrid 2X solo/duo One Grid's tags stand for?
The game's browser takes its cue from the tags Burn Rust OneGrid 2X solo/duo One Grid has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp25 (Max players): 25 slots are available; ts2 (Group limit): Teams cap out at 2; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): The game build is 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Burn Rust OneGrid 2X solo/duo One Grid?
These Rust Server Score lists count Burn Rust OneGrid 2X solo/duo One Grid among them: 2x Rust servers, graded, Duo servers, marked like a report and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Duo; Gather rate: 2x.
Map and rules
How is Burn Rust OneGrid 2X solo/duo One Grid set up, and what rules does it keep?
Burn Rust OneGrid 2X solo/duo One Grid sets gather at 2x, as its name suggests. The cap on group size is 2 players (duo). It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Getting in
How should you connect to Burn Rust OneGrid 2X solo/duo One Grid?
Enter client.connect 46.148.179.40: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 asmp25,ptrak,$r?,v2634,gmrust,cs166586,ts2,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp25
Max players25 slots are available.
ts2
Group limitTeams cap out at 2.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: 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 fair term, with more to come. Strongest in wipe hold (A+); standing is the one to work on (F).