Rust Server TrendsSeismic network · station log
Recording Stations11,743 Players57,957 Active3,448 Wipes · 3 h134 48 h

Station XX-9788 · recording

RedlineQc

Online 64.74.161.162:28015 checked 10m ago

moddedcarbon
Connect
Players now
0/ 30
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#9,788
top 44%
Last wipe
9d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-9788 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 30 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123400:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020000:0009:0018:0004:0013:0022:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 44% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
1.5 daysbetween real wipes
on rhythm
20%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
50%else halves by day 5

The first 48 hours of its last wipes

Sun 18 OctSun 18 OctSat 17 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 18 Oct, 15:10 UTC9d ago M0.0rising 1 – running 0
Sun 18 Oct, 03:19 UTC9d ago M0.0rising 1 – 0.5 days 0
Sat 17 Oct, 20:16 UTC10d ago M0.0rising 1 – 0.3 days 0
Sat 3 Oct, 01:20 UTC24d ago M0.0rising 1 held half 14.8 days 0
Sun 20 Sep, 15:55 UTC37d ago M0.0rising 1 halved by day 5 12.4 days 0
Sat 19 Sep, 02:55 UTC38d ago M0.0rising 1 – 1.5 days 0

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 163 on average
61/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average
126/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 113 on average
70/ 225
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average
64/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
15/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RedlineQc?

The procedural map on RedlineQc is size 3,500 with seed 1337, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page. The name of its map is Custom Map.

Which settings and rules apply on RedlineQc?

You will find no gather rate in the name of RedlineQc. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on RedlineQc?

A reading taken now shows 0 players on RedlineQc, which has 30 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does RedlineQc rank against other Rust servers?

Over the last seven days, RedlineQc recorded enough player hours to reach #9,788 worldwide, placing it in the top 44% of all ranked servers.

Server details

How reliably does RedlineQc stay online?

RedlineQc is up at the moment. The uptime it reports puts its last restart about 5 days ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does RedlineQc perform under load?

The 48-hour average is 91 server fps; 65 is the lowest observed. The world held up to 70,624 entities at its peak, buildings and deployables included. Its highest memory use was 3,933 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does RedlineQc run from?

A region is not published by RedlineQc. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 64.74.161.162:28015.

What build of Rust does RedlineQc use?

RedlineQc is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on RedlineQc?

1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe. Half that peak was held until the next wipe in 50% of its recent wipes. It fell under half by day 5 in the wipes where it didn't hold.

How often does RedlineQc wipe, and on which days?

There is no next wipe to predict at RedlineQc, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 9 days 8 hours is how long the current world has been running.

Lists and tags

What do the server tags on RedlineQc mean?

The game's server browser reads the tags RedlineQc publishes: gmrust (Game mode): Survival in standard Rust; mp30 (Max players): 30 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does RedlineQc appear?

You will find RedlineQc on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Connecting

How do you connect to RedlineQc?

You can connect by pressing F1 in Rust and typing client.connect 64.74.161.162:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://discord.com/invite/2HCunPdHSE is where its website lives.

Instrument codes

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp30
Max players 30 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

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.