RUST METRICSFlight deck · live data
Data live Servers11,748 Players63,000 Populated3,404 Fresh wipes 3 h200 Scan5 min
‹ All servers126.8.121.24:28015
Offline Full Queue Fresh wipe Wipe due No query

tutorial_tokuo_server

Offline 126.8.121.24:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,903top 70%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 05:12 UTC27d ago 1 – running 1

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on tutorial_tokuo_server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does tutorial_tokuo_server follow?

Its rhythm cannot be told from the wipes of tutorial_tokuo_server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 27 days 6 hours ago the current world was made.

Lists and filters

Which tags does tutorial_tokuo_server carry, and what do they mean?

Tags published by tutorial_tokuo_server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts16 (Group limit): You may team up with at most 16; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Build 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does tutorial_tokuo_server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry tutorial_tokuo_server: Rust tutorial servers and Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does tutorial_tokuo_server sit in the rankings?

Ranking for tutorial_tokuo_server: #15,903 on seven-day player hours, top 70% of all ranked servers.

What is the population on tutorial_tokuo_server?

tutorial_tokuo_server is not responding; status offline, last seen 26 days 22 hours ago.

Server

Which location does tutorial_tokuo_server run from?

No region comes from tutorial_tokuo_server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 126.8.121.24:28015.

What Rust version is tutorial_tokuo_server on?

Reading: tutorial_tokuo_server, Rust network protocol 2634 and build 166494, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on tutorial_tokuo_server, and is it online?

Reading: offline. tutorial_tokuo_server last answered 26 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Rules and settings

What settings and rules apply on tutorial_tokuo_server?

Reading the name gives no gather rate for tutorial_tokuo_server. Group size, maximum: 16 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is tutorial_tokuo_server on?

The game generates a procedural map for tutorial_tokuo_server.

Connection

What do you do to join tutorial_tokuo_server?

Check: join. Open Rust, press F1, then enter client.connect 126.8.121.24:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166494,ts16

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts16
Group limit You may team up with at most 16.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Build 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.