Station XX-11013 · no signal
=(eGO)= | Dev | Edgegamers.com
Offline 66.118.246.78:28015 checked 1d ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #11,013
- top 50%
- Last wipe
- 8d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 slots
- Motion · 24 h
- M0.0■steady+0 players
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 50% 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.
- usual gap
- 0.7 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 34 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 20 Oct, 12:40 UTC8d ago | M0.0▲rising | 1 | – | running | 0 | |
| Mon 19 Oct, 19:58 UTC9d ago | M0.0▲rising | 1 | – | 0.7 days | 0 |
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 settings and rules apply on =(eGO)= | Dev | Edgegamers.com?
You will find no gather rate in the name of =(eGO)= | Dev | Edgegamers.com. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on =(eGO)= | Dev | Edgegamers.com right now?
=(eGO)= | Dev | Edgegamers.com is not responding at this moment and is offline, last seen 32 hours ago. The seven-day average is 0 players, with a peak of 1.
How does =(eGO)= | Dev | Edgegamers.com rank against other Rust servers?
On player hours for the past week, =(eGO)= | Dev | Edgegamers.com sits at #11,013, which puts it inside the top 50% of every ranked server.
Operator and location
How reliably does =(eGO)= | Dev | Edgegamers.com stay online?
No contact with =(eGO)= | Dev | Edgegamers.com right now, and the last recorded contact was 32 hours ago. Of the 168 hours in the last 7 full days, it was up for 13, or 8% of the time. 19 October 2026 is when Rust Server Trends first recorded it.
Where in the world is =(eGO)= | Dev | Edgegamers.com hosted?
A region is not published by =(eGO)= | Dev | Edgegamers.com. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 66.118.246.78:28015.
Which Rust version is =(eGO)= | Dev | Edgegamers.com running?
=(eGO)= | Dev | Edgegamers.com 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 pattern
What does wipe day look like on =(eGO)= | Dev | Edgegamers.com?
1 players, on average, was the busiest crowd at its recent wipes. 34 hours after the latest wipe, the crowd peaked.
On what timetable does =(eGO)= | Dev | Edgegamers.com run its wipes?
The rhythm of =(eGO)= | Dev | Edgegamers.com cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 8 days 21 hours.
Tags
What do the server tags on =(eGO)= | Dev | Edgegamers.com mean?
These are the tags =(eGO)= | Dev | Edgegamers.com publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp500 (Max players): The server has 500 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; 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; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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 =(eGO)= | Dev | Edgegamers.com appear?
The Rust Server Trends lists that take in =(eGO)= | Dev | Edgegamers.com are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to join
What steps get you onto =(eGO)= | Dev | Edgegamers.com?
You can connect by pressing F1 in Rust and typing client.connect 66.118.246.78: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.
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.