Station XX-15358 · recording
RektoServer
Online 65.108.77.9:28015 checked 11m ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,358
- top 69%
- Last wipe
- 34d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% 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
- 7.6 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 25 Sep, 02:11 UTC34d ago | M0.0■steady | 0 | – | running | 0 | |
| Thu 17 Sep, 11:42 UTC41d ago | M0.0▲rising | 2 | halved by day 1 | 7.6 days | 1 |
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 pageServer rules
Which map is running on RektoServer?
The procedural map on RektoServer is size 4,000 with seed 1563008540, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on RektoServer?
You will find no gather rate in the name of RektoServer. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on RektoServer?
0 of the 10 slots on RektoServer are filled right now. Averaged across the last seven days, the population was 0 players.
How does RektoServer rank against other Rust servers?
On player hours for the past week, RektoServer sits at #15,358, which puts it inside the top 69% of every ranked server.
Operator and location
How reliably does RektoServer stay online?
Right now, you can reach RektoServer. Going by the uptime figure it reports, it restarted about 21 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 16 September 2026.
Does RektoServer hold a steady tick rate?
Its average server fps over the last 48 hours was 223, and it never dropped below 206. At its highest, it carried 91,000 entities: buildings, deployables and the world's other contents. It reached a ceiling of 2,707 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is RektoServer hosted?
A region is not published by RektoServer. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 65.108.77.9:28015.
What build of Rust does RektoServer use?
Rust network protocol 2635 and build 169456 on Linux is what RektoServer runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on RektoServer?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
On what timetable does RektoServer run its wipes?
On record so far are too few of RektoServer's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 34 days.
Server tags
What do the server tags on RektoServer mean?
These are the tags RektoServer publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs169456 (Build): Game build: 169456; ptrak (Networking): The network layer is RakNet, the game's standard; $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): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does RektoServer appear?
You will find RektoServer on the following Rust Server Trends lists: 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.
Join the server
How do you connect to RektoServer?
To join, enter client.connect 65.108.77.9:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.