Rust Data

rustdata.spaceservers64.40.9.39:28086.ipynb

Run all rust-data · live

‹ All servers

Online 64.40.9.39:28089 checked 12m ago

tumutu test server

moddedoxide

Connect

srv = rust.server("64.40.9.39:28086")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,400 # top 69%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
0246822:0007:0016:0001:0010:0019: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap16.9 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Thu 1 OctMon 14 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:12 UTC FW26d ago 0 NaN running 0
1 Mon 14 Sep, 20:47 UTC43d ago 1 halved by day 3 16.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.

display(srv.map, srv.info())

Map

4000 · seed 2026680033
Map of tumutu test server
map
Procedural Map
size
4000
seed
2026680033
Open on RustMaps

Server

srv.info()
address
64.40.9.39:28089
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 18:12 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Welcome to a Rust Dedicated Server Currently used for testing purposes by tumutu Powered by Gameserverkings.com

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average153/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average134/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average28/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average147/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average45/1000

Quick answers

From the figures on this page.

Population data

How does tumutu test server compare in the rankings?

Over the last seven days tumutu test server sits at #15,400 on player hours, in the top 69% of ranked servers.

What population does tumutu test server carry?

The sample now reads 0 players for tumutu test server, out of 100 slots. Over the last seven days it averaged 0 players.

Server data

How smoothly does tumutu test server run?

The 48-hour average is 5 server fps, with a low of 5. Entity numbers reached 93,912, and that includes buildings, deployables and the rest. Memory peaked at 5,148 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does tumutu test server run?

Version Rust network protocol 2634 and build 166494 on Linux is reported by tumutu test server. Steam updates your game for you, but the protocol must match to join.

How reliable is tumutu test server, and is it online now?

Online is the state at the latest refresh for tumutu test server. The uptime it reports puts the last restart about 26 days 1 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.

Where does tumutu test server sit?

For tumutu test server, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 64.40.9.39:28089 is its address.

Rules, settings, map

What rules and settings are recorded for tumutu test server?

You will not find a gather rate in the string tumutu test server. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has tumutu test server loaded?

The game generates the map on tumutu test server: procedural, size 4,000, seed 2026680033. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does tumutu test server wipe?

The record for tumutu test server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 26 days 2 hours ago.

What is wipe day on tumutu test server like?

The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 3.

Lists and tags

Which Rust Data filters and lists contain tumutu test server?

The Rust Data lists that tumutu test server fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on tumutu test server hold?

Read by the game's server browser, the tags tumutu test server publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to tumutu test server?

In Rust, F1 opens the console: type client.connect 64.40.9.39:28089. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs166494
Build Build number: 166494.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 79,225 players 11,834 servers online