Codeman3434$
Online NA 66.51.96.61:28010 checked 7m ago
Server instruments
last reading Thu 15:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 5 · below 20 is lag, below 10 is badEntities
48 h range 106,597–118,074 · memory 3,133 MBUptime
9 h 20 min since its last restart, at the last readingPlayers
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 49% of all ranked servers, top 71% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 2hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 2hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 17:04 UTC26d ago | 1 | – | running | 0 |
| Tue 29 Sep, 19:13 UTC29d ago | 1 | held half | 2.9 days | 0 |
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- 13/200
- 5/100
- 0/200
- 83/999
- 17/150
- 3/125
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Codeman3434$?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 4 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.
What wipe timing does Codeman3434$ follow?
The only wipe for Codeman3434$ is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 26 days 23 hours ago. Its tags carry a monthly wipe schedule.
Lists and filters
How should you read the tags on Codeman3434$?
Tags published by Codeman3434$, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^c (Creative): Check: mode. Creative, where you build what you like and gather nothing; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): The server browser files it under North America. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Codeman3434$ appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Codeman3434$: Modded Rust servers, checked live, Build and creative servers, Rust creative servers and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Creative ^c, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Occupancy
What position does Codeman3434$ hold among Rust servers?
Ranked by seven-day player hours, Codeman3434$ sits at #11,027 and #1,318 in North America, inside the top 49%.
What is the population on Codeman3434$?
Current headcount on Codeman3434$: 0 players, 50 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 19:00 UTC, 1 players on average.
Operator and location
Where does Codeman3434$ sit?
Codeman3434$ gives North America as its location, with the NA tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 66.51.96.61:28010.
What Rust version is Codeman3434$ on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Codeman3434$. To get in, your game needs the same protocol; Steam applies the update.
Is performance on Codeman3434$ within range?
Reading: 6 server fps on average across the last 48 hours. It never dropped below 5. Reading: 118,074 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,762 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on Codeman3434$, and is it online?
Reading: online. Codeman3434$ answers right now. By its reported uptime, the last restart was roughly 9 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What settings and rules apply on Codeman3434$?
No gather rate appears in the name: Codeman3434$. No limit is set beyond the default. Groups take up to 8 players. Mode check gives build & creative; no gathering; sandbox building instead. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on Codeman3434$?
Check: map. Procedural, size 4,500, seed 1, generated by the game on Codeman3434$. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
What do you do to join Codeman3434$?
Press F1 in Rust and enter client.connect 66.51.96.61:28010. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.