Rexhunter99 Co-op
Offline 179.65.161.176:28015 checked 5d 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 72% 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
- 352/ 375
- 590/ 600
- 397/ 475
- 120/ 200
- 607/ 625
- 243/ 250
Quick answers
Tags and listings
Where does Rexhunter99 Co-op appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Rexhunter99 Co-op are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Rexhunter99 Co-op?
gmrust (Game mode): This is the standard Rust survival experience; mp16 (Max players): The slot count is 16; ts8 (Group limit): Teams cap at 8, which is the game default; v2631 (Protocol): The protocol is 2631; a different version won't get you in; cs157450 (Build): The build number is 157450; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set — that is the tag list Rexhunter99 Co-op 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 details
What location is Rexhunter99 Co-op in?
There is no published region for Rexhunter99 Co-op. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 179.65.161.176:28015.
What's the uptime like for Rexhunter99 Co-op?
The server Rexhunter99 Co-op is not reachable at the moment; the last sighting was 5 days 17 hours ago. In the last full 5 days, 0 of 120 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 12 October 2026.
What Rust version is Rexhunter99 Co-op on?
On Linux, Rexhunter99 Co-op runs Rust network protocol 2631 and build 157450. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
What schedule does Rexhunter99 Co-op follow for wipes?
Rexhunter99 Co-op'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 85 days 7 hours ago.
Map and rules
Which rules and settings is Rexhunter99 Co-op running?
Its name does not state a gather rate for Rexhunter99 Co-op. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser lists it under Community, making it a community server. VAC, Valve's anti-cheat, is disabled.
What's the map on Rexhunter99 Co-op?
A procedural map, generated by the game, is in play on Rexhunter99 Co-op.
Player stats
How many players are on Rexhunter99 Co-op?
Rexhunter99 Co-op was last seen 5 days 17 hours ago and is offline as you read this. The seven-day average for players here is 0.
What's Rexhunter99 Co-op's rank among Rust servers?
For player hours in the last seven days, Rexhunter99 Co-op ranks #15,826, within the top 72% of ranked servers.
Join info
How do you get into Rexhunter99 Co-op?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 179.65.161.176:28015.