DWG RG-S2377Server sheetchecked 13m ago
GALO | PT/EU | SOLO | Vanilla | Biweekly
Online EU 168.100.161.130:28015 checked 13m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 11% of all ranked servers, top 31% in EU, and #111 of the solo servers (top 50%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence
Coming wipes
- 7d 4hThu 5 Nov, 19:00 UTCFW
- 9d 2hSat 7 Nov, 16:36 UTC
- 23d 2hSat 21 Nov, 16:36 UTC
- 35d 4hThu 3 Dec, 19:00 UTCFW
- 37d 2hSat 5 Dec, 16:36 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 9, 1 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 16:36 UTC4d ago | 9 | – | running | 1 |
| Thu 15 Oct, 16:52 UTC13d ago | 7 | halved by day 1 | 9 days | 2 |
| Wed 7 Oct, 15:57 UTC21d ago | 24 | halved by day 2 | 8 days | 1 |
| Thu 1 Oct, 17:59 UTC FW27d ago | 45 | halved by day 4 | 5.9 days | 2 |
| Thu 24 Sep, 18:01 UTC34d ago | 60 | halved by day 5 | 7 days | 4 |
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
Quick answers
Server data
What uptime is recorded for GALO | PT/EU | SOLO | Vanilla | Biweekly, and is it up?
GALO | PT/EU | SOLO | Vanilla | Biweekly is up at this moment. Counted from its reported uptime, the last restart was about 7 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 14 September 2026.
What does the recorded performance of GALO | PT/EU | SOLO | Vanilla | Biweekly show?
Average server fps over the last 48 hours is 24; the lowest was 5. Counted at its highest: 51,223 entities, buildings, deployables and the rest of the world included. Memory use peaked at 2,632 MB. A climbing entity count and low fps are the source of what players feel as lag.
What location is recorded for GALO | PT/EU | SOLO | Vanilla | Biweekly?
In Europe GALO | PT/EU | SOLO | Vanilla | Biweekly lists itself, tagged EU. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 168.100.161.130:28015 is its address.
What Rust version is recorded for GALO | PT/EU | SOLO | Vanilla | Biweekly?
On Linux, GALO | PT/EU | SOLO | Vanilla | Biweekly runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.
Population
What does the population history show for GALO | PT/EU | SOLO | Vanilla | Biweekly?
At the last refresh, GALO | PT/EU | SOLO | Vanilla | Biweekly recorded 1 players across 100 slots. The seven-day mean is 2 players; the peak over the same period is 9. The 48-hour peak falls at 10:00 UTC, averaging 5 players.
Against other Rust servers, where is GALO | PT/EU | SOLO | Vanilla | Biweekly placed?
GALO | PT/EU | SOLO | Vanilla | Biweekly also measures #915 in Europe on the same seven-day player-hour count, at #2,377 globally and in the top 11% of ranked servers. Within the solo group it places #111.
Wipe data
What happens on GALO | PT/EU | SOLO | Vanilla | Biweekly on the day of a wipe?
The recent wipes averaged a busiest count of 13 players. 1 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 3.
On GALO | PT/EU | SOLO | Vanilla | Biweekly, when do wipes occur?
Too few of GALO | PT/EU | SOLO | Vanilla | Biweekly's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 4 days 21 hours ago. The tags state a wipe schedule at two-week intervals.
Rules and settings
Which rules and settings are recorded for GALO | PT/EU | SOLO | Vanilla | Biweekly?
No gather rate is stated in the name of GALO | PT/EU | SOLO | Vanilla | Biweekly. Teams are not permitted; solo only. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Community is its tab in the server browser. Carbon plugins are run on it. It describes itself as vanilla, by which it means no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.
On which map is GALO | PT/EU | SOLO | Vanilla | Biweekly played?
Size 3,000 with seed 1627336182: that is the procedural map GALO | PT/EU | SOLO | Vanilla | Biweekly runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Lists and filters
Where does GALO | PT/EU | SOLO | Vanilla | Biweekly appear among the Rust Graphs lists and filters?
These Rust Graphs lists include GALO | PT/EU | SOLO | Vanilla | Biweekly: Europe servers, plotted, Rust community servers, plotted, Solo Rust servers: group limit 1 and Vanilla Rust servers. It is returned by these filters on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Carbon ^y; Group limit: Solo; Wipe schedule: Every two weeks; Last wipe: In the last week.
Which meaning is attached to each tag on GALO | PT/EU | SOLO | Vanilla | Biweekly?
The game's server browser reads these tags from GALO | PT/EU | SOLO | Vanilla | Biweekly: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): The slot count is 100; ts1 (Group limit): Teams hold no more than 1; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^y (Carbon): The plugin framework is Carbon; EU (Europe): The server browser lists it under Europe. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
What is the way to connect to GALO | PT/EU | SOLO | Vanilla | Biweekly?
Connect with client.connect 168.100.161.130:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://galo.lol/ is its website.
Server tags
Published as mp100,ptrak,$r?,v2635,^y,^b,^v,EU,gmrust,cs168909,ts1
Game
gmrust
mp100
ts1
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Difficulty
^v
Mods and access
^y
Region
EU
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.