RUST METRICSFlight deck · live data
Data live Servers11,738 Players62,312 Populated3,391 Fresh wipes 3 h192 Scan5 min
‹ All servers66.206.27.162:50505
Online Full Queue Fresh wipe Wipe due No query

iftes test server co

Online 66.206.27.162:50505 checked 13m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 10:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 240 SERVER FPS

Server fps

48 h low 217 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 48,969 ×1000

Entities

48 h range 45,011–50,707 · memory 2,677 MB
1239 ET SINCE RESTART 2D 17H

Uptime

2 days 17 hours since its last restart, at the last reading
7-day average0peak 2
Rank#5,968top 27%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Memory2,677MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75112:0021:0006:0015:0001:0010:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040012:0021:0006:0015:0001:0010: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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 gap3.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 6

The first 48 hours of its last wipes

Mon 26 OctThu 22 OctWed 21 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, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 16:56 UTC2d ago 1 – running 0
Thu 22 Oct, 07:44 UTC7d ago 1 held half 4.4 days 0
Wed 21 Oct, 12:55 UTC7d ago 1 – 0.8 days 0
Mon 19 Oct, 18:21 UTC9d ago 2 – 1.8 days 0
Sun 18 Oct, 18:04 UTC10d ago 2 – 1 days 0
Wed 7 Oct, 18:08 UTC21d ago 1 halved by day 6 11 days 0
Thu 1 Oct, 17:45 UTC FW27d ago 1 halved by day 1 6 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.

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 schedule

What happens on iftes test server co when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 2 hours. Above half that peak the crowd stayed until the next wipe in 50% of recent wipes. It fell below half by day 6 when it didn't.

What wipe timing does iftes test server co follow?

No next wipe can be predicted for iftes test server co, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 2 days 18 hours ago.

Tags

How should you read the tags on iftes test server co?

These are the tags iftes test server co publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 iftes test server co?

These Rust Metrics lists carry iftes test server co: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Player count

What position does iftes test server co hold among Rust servers?

Player hours over seven days put iftes test server co at #5,968, in the top 27% of all ranked servers.

What is the population on iftes test server co?

0 of 10 slots are filled on iftes test server co right now. Seven-day check: 0 players on average. Peak reading: 2. Check: 48-hour peak. 17:00 UTC, 1 players on average.

Server details

Which location does iftes test server co run from?

Reading: location. iftes test server co gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 66.206.27.162:50505.

What Rust version is iftes test server co on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by iftes test server co. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for iftes test server co?

Check: fps. Average 236 server fps over the last 48 hours, low of 217. Within range. Reading: 50,707 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 2,754 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is iftes test server co, and is it online now?

iftes test server co reports online. Status: normal. By its reported uptime, the last restart was roughly 2 days 17 hours ago. Reading: 99% uptime over the last 7 full days. It was up 166 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

How is iftes test server co configured, and what rules are in force?

No gather rate appears in the name: iftes test server co. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on iftes test server co?

From seed 13123, the game generates the procedural map on iftes test server co. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to iftes test server co?

Check: join. Open Rust, press F1, then enter client.connect 66.206.27.162:50505. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://www.yourmother.com/.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.