Rust Server TrendsSeismic network · station log
Recording Stations11,631 Players45,053 Active3,098 Wipes · 3 h93 48 h

Station XX-13852 · no signal

Burn Rust OneGrid 2X solo/duo One Grid

Offline 46.148.179.40:28015 checked 13d ago

2x duo moddedoxide
Connect
Players now
1/ 25
4% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,852
top 64%
Last wipe
21d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-13852 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 25 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep4 Oct9 Oct15 Oct21 Oct

Top 64% of all ranked servers, and #356 of the duo servers (top 84%). Ranked on player hours over the last seven days.

Expected events

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 gap
1.4 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 6 OctSun 4 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 6 Oct, 14:35 UTC21d ago M0.0steady 1 – running 1
Sun 4 Oct, 18:08 UTC23d ago M0.0rising 1 – 1.9 days 0
Fri 2 Oct, 17:17 UTC25d ago M0.0steady 1 held half 2 days 1
Thu 1 Oct, 16:28 UTC26d ago M0.0steady 1 – 1 days 1
Wed 30 Sep, 22:10 UTC27d ago M0.0steady 1 – 0.8 days 1
Wed 30 Sep, 14:41 UTC27d ago M0.0rising 1 – 0.3 days 0
Tue 29 Sep, 16:58 UTC28d ago M0.0steady 1 – 0.9 days 1
Sun 27 Sep, 18:23 UTC30d ago M0.0steady 1 – 1.9 days 1
Thu 17 Sep, 18:32 UTC40d ago M0.0steady 1 – – 10 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
WARBANDITS.GG EU 2X |Solo/Duo|X2 JUST WIPED EU · duo · 2x · weekly · 211 on average
16/ 200
SURVIVORS.GG [ 2x Solo/Duo ] WIPED 27.10 duo · 2x · biweekly · 161 on average
99/ 200
WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED NA · duo · 2x · weekly · 148 on average
25/ 200
Magic Rust #5 — Modded 2x (Solo/Duo) | Pyccкий EU · duo · 2x · weekly · 116 on average
45/ 100
Magic Rust #26 — Vanilla 2x (Solo/Duo) | Pyccкий EU · duo · 2x · weekly · 97 on average
17/ 200
EU RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP Wipe | EU · duo · 2x · monthly · 92 on average
31/ 150
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on Burn Rust OneGrid 2X solo/duo One Grid?

Going by its name, Burn Rust OneGrid 2X solo/duo One Grid runs 2x gather. You can have up to 2 players in a group (duo). In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Burn Rust OneGrid 2X solo/duo One Grid?

Burn Rust OneGrid 2X solo/duo One Grid is not responding at this moment and is offline, last seen 13 days 15 hours ago.

How does Burn Rust OneGrid 2X solo/duo One Grid rank against other Rust servers?

The last seven days of player hours place Burn Rust OneGrid 2X solo/duo One Grid at #13,852, in the top 64% of all ranked servers. The ranking for duo puts it at #356.

Server facts

How reliably does Burn Rust OneGrid 2X solo/duo One Grid stay online?

As recorded now, Burn Rust OneGrid 2X solo/duo One Grid is not reachable, the last contact having been 13 days 15 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 17 September 2026 is when Rust Server Trends first recorded it.

Which region does Burn Rust OneGrid 2X solo/duo One Grid run from?

Nothing about a region comes from Burn Rust OneGrid 2X solo/duo One Grid. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 46.148.179.40:28015 is the address it uses.

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. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on Burn Rust OneGrid 2X solo/duo One Grid?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

How often does Burn Rust OneGrid 2X solo/duo One Grid wipe, and on which days?

No next wipe can be predicted for Burn Rust OneGrid 2X solo/duo One Grid, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 21 days 17 hours.

Lists and tags

What do the server tags on Burn Rust OneGrid 2X solo/duo One Grid mean?

Tags published by Burn Rust OneGrid 2X solo/duo One Grid and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp25 (Max players): Slots: 25; ts2 (Group limit): Each team can hold up to 2; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166586 (Build): The game build is 166586; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Burn Rust OneGrid 2X solo/duo One Grid appear?

The Rust Server Trends lists that take in Burn Rust OneGrid 2X solo/duo One Grid are: 2x Rust servers, listed live, Duo Rust servers, group limit 2 and Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Duo; Gather rate: 2x.

Join the server

What steps get you onto Burn Rust OneGrid 2X solo/duo One Grid?

You can connect by pressing F1 in Rust and typing client.connect 46.148.179.40:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp25,ptrak,$r?,v2634,gmrust,cs166586,ts2,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp25
Max players Slots: 25.
ts2
Group limit Each team can hold up to 2.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166586
Build The game build is 166586.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.