Telegram RegisterThe public register of Telegram
Telegram profile photo for ‘‘ 𝗦ᴀᴛɪɴ ⸝⸝.ᐟ⋆ ♯𝘪𝘯𝘧𝘰

Channel

‘‘ 𝗦ᴀᴛɪɴ ⸝⸝.ᐟ⋆ ♯𝘪𝘯𝘧𝘰

@satin_flood

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

38subscribers

-1 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003889657364
TypeChannel
Username@satin_flood
Created14 June 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/satin_flood

Growth

383938.513 Aug 2026, 19:03 — 39 subscribers15 Aug 2026, 00:58 — 38 subscribers13 Aug 2026, 19:0315 Aug 2026, 00:58
2 measurements spanning 1 day, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 38–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:5838-1
13 Aug 2026, 19:0339first reading

Engagement

17 posts held, back to 14 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
172.6%
avg views ÷ 38 subscribers
Avg views / post
65.6
12 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
12
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held17 (14 June 20264 August 2026)
Views total787
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 19:03 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

8 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🆒450.0%
337.5%
💘112.5%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 14 June 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 03:17 UTC49 viewsread 13 August 2026

☺️едется набор в администрацию..🙂 Мне нужны люди,которые в действительности готовы работать,а не просто сидеть и прохлаждаться на админке. Мне нужны: Старший администратор: Вливает нью в чат Следит за чатом Поднимает неактивов Поднимает актив в чате Также я проведу проверку на знание правил Кастомер: Проводить 2 кастомки в месяц Организовывать касты против других флудов Вообщем проводить касты Еще один монтажер не

29 Jul 2026, 08:51 UTC79 viewsread 13 August 2026
Photo

—🔤dministration.. 🪄 𝑂𝗐𝗇𝖾𝗋- @sly1ncense 🗡&💎 𝑆𝖾𝗇𝗂𝗈𝗋—𝑎𝖽𝗆𝗂𝗇 @Di_vis & @shouganai69 💫 𝐽𝗎𝗇𝗂𝗈𝗋-𝑎𝖽𝗆𝗂𝗇- @toyota_che ⚔ 𝐸𝖽𝗂𝗍𝗈𝗋 - ??? 🗡 𝐶𝗎𝗌𝗍𝗈𝗆 - @depresionkida

28 Jul 2026, 08:22 UTC81 viewsread 13 August 2026

—🔤ругие Крип— Черепаха— Лорд— Синий бафф—🦴 Красный бафф— Голем— Вазон— Краб— Жук— Барбиэль-🦴

28 Jul 2026, 08:22 UTC78 viewsread 13 August 2026

—🔤ойцы Арлотт — Алдос — Альфа — Алукард — Аргус —🦴 Аулус — Баданг — Бальмонд — Бейн — Бенедетта — Чу —🦴 Чичи —🦴 Дариус — Фрейя — Гвиневра —🦴 Хильда — Кусака — Джулиан — Халид — Лапу-Лапу —🦴 Леоморд — Лукас — Мартис — Маша — Минситтар — Пакито — Фовиус — Руби —🦴 Сильвана — Сан —🦴 Теризла — Тамуз — Иксборг — Инь — Чонг — Зилонг — Эсмеральда — Уранус — Сора —

28 Jul 2026, 08:22 UTC65 viewsread 13 August 2026

—🔤анки: Франко— Джонсон— Минотавр— Грок— Белерик— Гатоткача— Хильда— Тигрил— Чип— Акай— Глу— Хилос— Уранус— Баский— Хуфра—🦴 Атлас— Эдит— Бартс— Фредрин— Марсель—

28 Jul 2026, 08:21 UTC70 viewsread 13 August 2026

—🔤аги Цзэтянь —🦴 Люнокс —🦴 Сесилион — Аврора — 🦴 Валентина —🦴 Вексана —🦴 Селена —🦴 Ксавьер — Горд — Циклоп — Эйдора — Кадита —🦴 Чжусинь — 🦴 Нана — Одетта — Заск — Фаша — Валир —🦴 Чан — Вейл — Лилия — Ло Йи — Ив — Новария — Харит — Кимми — Кагура 🦴 Алиса—

28 Jul 2026, 08:21 UTC62 viewsread 13 August 2026

—🔤оддержка Флорин — 🦴 Ангела — 🦴 Рафаэль — Кайя — Эстес — Кармилла —🦴 Дигги — Калеа — Матильда — Фарамис — Лолита —

28 Jul 2026, 08:21 UTC63 viewsread 13 August 2026

—🔤трелки: Лейла— Лесли— Обсидия— Бруно— Броуди— Ханаби— Натан— Клауд— Кэрри— Клинт— Москов— Иритель— Роджер— Беатрис— Мелисса— Ван Ван— Гренка—🦴 Пополь— Иксия— Мия—

28 Jul 2026, 08:21 UTC64 views0 reactionsread 13 August 2026

Занято: 🦴 Свободно: Бронь: 🧷 —🔤бийцы: Ланселотт—🦴 Нолан—🦴 Фанни—🦴 Госсен—🦴 Эймон—🦴 Джуллиан— Джой—🦴 Бенедетта— Харли— Ханзо— Карина— Хаябуса—🦴 Су Ё— Хэлкарт— Сабер— Наталья— Алукард— Линг—🦴 Лсс— Хирара—

28 Jul 2026, 08:21 UTC64 viewsread 13 August 2026
Photo

—🔤писок ролей. 👤 —Убийцы. —Бойцы. —Маги. —Поддержка. —Стрелки. —Танки. —Другое.

28 Jul 2026, 04:08 UTC55 viewsread 13 August 2026
Forwarded from @lunar_whisperrrPhoto

СОЮЗ Дорогие участники! Спешим сообщить вам о том что был заключен союз между двумя прекрасными проектами!! —美丽🏮 𝑆𝑎𝑡𝑖𝑛: 🪄Владелец Кагура — @sly1ncense 🍒Совладелец Ло Йи — @Meow2ik 🦋 инфо ʟᴜɴᴀʀ ᴡʜɪsᴘᴇʀ ᴄʜᴀᴛ: 🪄Владелец Чжусинь — @astee1 🍒Совладелец Кармилла — @toyota_che 🦋 инфо

28 Jul 2026, 04:08 UTC57 viewsread 13 August 2026

—🔤оюз между: —美丽🏮 𝑆𝑎𝑡𝑖𝑛 и 𝐆𝐨𝐬𝐬𝐚𝐦𝐞𝐫 𝐟𝐥𝐨𝐨𝐝 *при нажатии вы переходите на инфо каналы данных флудов,также вся доп.информация будет указана в данных каналах Рады сообщить,что наши проекты теперь связаны союзом,который будет открывать новые возможности,знакомства и веселые моменты для наших участников! Надеемся на долгий и дружный союз ,который поможет в продвижении обоих проектов 🫶🏻. —美丽🏮 𝑆𝑎𝑡𝑖𝑛 —Владелец: @sly1n

Showing the 12 most recent of 17 posts we hold for @satin_flood. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 244,774 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 August 2026 — this entry's latest reading, not the date you are reading this.

“‘‘ 𝗦ᴀᴛɪɴ ⸝⸝.ᐟ⋆ ♯𝘪𝘯𝘧𝘰” (@satin_flood), 38 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/satin_flood.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.