kukumber6767
Offline 31.40.121.176:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 510/575
- 340/400
- 39/250
- 36/250
- 109/150
- 125/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does kukumber6767 follow?
To tell the rhythm of kukumber6767, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 41 days 4 hours ago.
Tags
Which tags does kukumber6767 carry, and what do they mean?
These are the tags kukumber6767 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show kukumber6767?
Rust Metrics lists featuring kukumber6767: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does kukumber6767 sit in the rankings?
Ranking for kukumber6767: #13,266 on seven-day player hours, top – of all ranked servers.
What is the population on kukumber6767?
Reading for kukumber6767: offline at this moment; last seen 41 days 3 hours ago.
Operator and location
What location is kukumber6767 hosted in?
No region comes from kukumber6767. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 31.40.121.176:28015.
What Rust version is kukumber6767 on?
Rust network protocol 2633 and build 164530 on Windows is the build kukumber6767 runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on kukumber6767, and is it online?
kukumber6767 reports offline. The last reading came 41 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.
Rules and settings
How is kukumber6767 configured, and what rules are in force?
Reading the name gives no gather rate for kukumber6767. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on kukumber6767?
Procedural map on kukumber6767, made by the game's generator.
Join
How can you get onto kukumber6767?
Press F1 in Rust and enter client.connect 31.40.121.176:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.