Local Debug (no EAC)
Offline 178.90.175.122:28015 checked 21d 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
- 308/ 300
- 592/ 600
- 458/ 500
- 128/ 200
- 536/ 525
- 214/ 250
Quick answers
Tags and search
Where does Local Debug (no EAC) appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Local Debug (no EAC): Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Local Debug (no EAC)?
gmrust (Game mode): This is the standard Rust survival experience; mp8 (Max players): It holds 8 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163207 (Build): It's on build 163207; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code — that is the tag list Local Debug (no EAC) puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is Local Debug (no EAC) in?
No region comes from Local Debug (no EAC). Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 178.90.175.122:28015.
How reliable is Local Debug (no EAC)?
Local Debug (no EAC) is down at the moment; it was last up 21 days 23 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 26 September 2026.
What Rust version is Local Debug (no EAC) on?
The version on Local Debug (no EAC) is Rust network protocol 2633 and build 163207, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
How often does Local Debug (no EAC) wipe?
Local Debug (no EAC)'s rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 42 days 3 hours ago.
Map and rules
What settings are in place on Local Debug (no EAC)?
No gather rate appears in the name of Local Debug (no EAC). The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. It sits under Community in the server browser: a community server. The server does not run Valve's anti-cheat, VAC.
What's the map on Local Debug (no EAC)?
Local Debug (no EAC) uses a game-generated procedural map.
Player stats
Is Local Debug (no EAC) busy?
The last sighting of Local Debug (no EAC) was 21 days 23 hours ago; it is offline right now.
What position does Local Debug (no EAC) hold in the server rankings?
For player hours in the last seven days, Local Debug (no EAC) ranks #14,211, within the top 61% of ranked servers.
Getting in
What's the way to join Local Debug (no EAC)?
To join, open Rust, hit F1, and enter client.connect 178.90.175.122:28015. Or click Launch Rust on this page to open the game through Steam and connect.