Station EU-2688 · recording
GALO | PT/EU | SOLO | Vanilla | Biweekly
Online EU 168.100.161.130:28015 checked 6m ago
- Players now
- 3/ 100
- 3% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 9
- Rank
- #2,688
- top 12% · #1011 in EU
- Last wipe
- 3d ago
- biweekly schedule
- Next wipe
- 8d 23h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 3of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +3into Mon 09:00 UTC
- Peak · 48 h
- 6most players in any hour
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
daily · 1 is bestTop 12% of all ranked servers, top 35% in EU, and #120 of the solo servers (top 55%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 8d 23h. The force wipe · high confidence
- usual gap
- 7.5 daysbetween real wipes
- on rhythm
- 50%of its recent wipes
- wipe-day peak
- 13players, last three wipes
- crowd held
- 0%else halves by day 3
Coming wipes
- 8d 23hThu 5 Nov, 19:00 UTCFW
- 10d 21hSat 7 Nov, 16:36 UTC
- 24d 21hSat 21 Nov, 16:36 UTC
- 36d 23hThu 3 Dec, 19:00 UTCFW
- 38d 21hSat 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 24 Oct, 16:36 UTC3d ago | M0.9▲rising | 9 | – | running | 1 | |
| Thu 15 Oct, 16:52 UTC12d ago | M0.7▲rising | 7 | halved by day 1 | 9 days | 2 | |
| Wed 7 Oct, 15:57 UTC20d ago | M1.4▲rising | 24 | halved by day 2 | 8 days | 1 | |
| Thu 1 Oct, 17:59 UTC FW26d ago | M1.6▲rising | 45 | halved by day 4 | 5.9 days | 2 | |
| Thu 24 Sep, 18:01 UTC33d ago | M1.7▲rising | 60 | halved by day 5 | 7 days | 4 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on GALO | PT/EU | SOLO | Vanilla | Biweekly?
GALO | PT/EU | SOLO | Vanilla | Biweekly runs a procedural map of size 3,000 with seed 1627336182, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on GALO | PT/EU | SOLO | Vanilla | Biweekly?
You will find no gather rate in the name of GALO | PT/EU | SOLO | Vanilla | Biweekly. Teams are not allowed here; it is solo only. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. Carbon is the plugin framework it runs. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on GALO | PT/EU | SOLO | Vanilla | Biweekly right now?
A reading taken now shows 3 players on GALO | PT/EU | SOLO | Vanilla | Biweekly, which has 100 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 9. The last 48 hours show their highest activity at 14:00 UTC, averaging 5 players.
How does GALO | PT/EU | SOLO | Vanilla | Biweekly rank against other Rust servers?
For player hours across the last seven days, GALO | PT/EU | SOLO | Vanilla | Biweekly takes #2,688 overall and #1,011 in Europe, inside the top 12% of all ranked servers. Within solo, it places #120.
Server details
How reliably does GALO | PT/EU | SOLO | Vanilla | Biweekly stay online?
Right now, you can reach GALO | PT/EU | SOLO | Vanilla | Biweekly. Going by the uptime figure it reports, it restarted about 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 14 September 2026.
Does GALO | PT/EU | SOLO | Vanilla | Biweekly hold a steady tick rate?
The 48-hour average is 27 server fps; 5 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 49,918. It reached a ceiling of 2,385 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does GALO | PT/EU | SOLO | Vanilla | Biweekly run from?
With its EU tag, GALO | PT/EU | SOLO | Vanilla | Biweekly lists itself in Europe. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 168.100.161.130:28015.
What build of Rust does GALO | PT/EU | SOLO | Vanilla | Biweekly use?
GALO | PT/EU | SOLO | Vanilla | Biweekly is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on GALO | PT/EU | SOLO | Vanilla | Biweekly?
The recent wipes averaged a busiest count of 13 players. The peak on the most recent wipe came 1 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 3.
How often does GALO | PT/EU | SOLO | Vanilla | Biweekly wipe, and on which days?
The prediction is taken from its tag, since GALO | PT/EU | SOLO | Vanilla | Biweekly has too few wipes on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 3 days 2 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Tags
What do the server tags on GALO | PT/EU | SOLO | Vanilla | Biweekly mean?
Tags published by GALO | PT/EU | SOLO | Vanilla | Biweekly and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts1 (Group limit): Teams are capped at 1 players; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^y (Carbon): A plugin framework, Carbon, runs here; EU (Europe): In the server browser it appears under Europe. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does GALO | PT/EU | SOLO | Vanilla | Biweekly appear?
These Rust Server Trends lists include GALO | PT/EU | SOLO | Vanilla | Biweekly: EU Rust servers, Rust community servers without the side modes, Solo Rust servers and Vanilla Rust servers, recorded live. You will find it under 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.
Connecting
How do you connect to GALO | PT/EU | SOLO | Vanilla | Biweekly?
You can connect by pressing F1 in Rust and typing client.connect 168.100.161.130: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. You can find its website at https://galo.lol/.
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.