One Grid Solo Only 2X
Online 104.129.132.45:28119 checked 11m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 11:49 UTC14d ago | 1 | – | running | 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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 833 on average | 818 / 900 |
| Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 613 on average | 428 / 425 |
| Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 376 on average | 145 / 200 |
| EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 355 on average | 193 / 220 |
| Magic Rust #18 — Vanilla 2x | Baйп 28.10 | EU · groups of 150+ · 2x · weekly · 333 on average | 932 / 1060 |
| MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 316 on average | 161 / 1000 |
Quick answers
from the figures on this pageWipe cycle
When does One Grid Solo Only 2X wipe?
With too few of its wipes on record, One Grid Solo Only 2X's rhythm is not yet clear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. The world now in play was created 14 days 3 hours ago.
On One Grid Solo Only 2X, what happens on wipe day?
The average busiest count over recent wipes is 1 players. The highest player count on the latest wipe arrived 3 hours in.
Server details
Which location hosts One Grid Solo Only 2X?
No region appears in what One Grid Solo Only 2X publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 104.129.132.45:28119.
What Rust build does One Grid Solo Only 2X run?
The platform is Linux, with Rust network protocol 2635 and build 168909 running on One Grid Solo Only 2X. The protocol has to match before you can join; Steam updates it automatically.
How reliable is One Grid Solo Only 2X, and is it online now?
As of the latest refresh, One Grid Solo Only 2X is online. About 45 hours ago is when it last restarted, judged by its reported uptime. 98% uptime over the last 7 full days, equal to 164 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
Does One Grid Solo Only 2X perform well?
Over 48 hours the average held at 5 server fps, and the minimum was 5. At its highest the entity count was 8,500, including buildings, deployables and all else. At its highest, memory use was 1,201 MB. Lag, for players, means low fps alongside a growing entity count.
Tags
Which meanings do the tags on One Grid Solo Only 2X carry?
Tags from One Grid Solo Only 2X, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Modded listing, where plugins or settings change the game. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does One Grid Solo Only 2X appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include One Grid Solo Only 2X: Rust servers with a 2x gather rate and Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Player numbers
Against other Rust servers, how does One Grid Solo Only 2X compare?
Player hours for the last seven days place One Grid Solo Only 2X at #15,179, in the top 68% of the ranked field.
At what level does One Grid Solo Only 2X run its population?
One Grid Solo Only 2X holds 0 players of its 100 slots as of the latest update. Seven-day figures: an average of 0 players and a peak of 1. Across the last 48 hours, 22:00 UTC shows the highest average: 0 players.
Settings
What are the settings on One Grid Solo Only 2X, and its rules?
2x gathering is what One Grid Solo Only 2X states in its name. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.
What is the map for One Grid Solo Only 2X?
The game generates a procedural map of size 1,500 with seed 1337 for One Grid Solo Only 2X. Because size and seed determine the map, it can be viewed on RustMaps via this page. The map is called Custom Map.
Connection
What is the way onto One Grid Solo Only 2X?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 104.129.132.45:28119.