Telegram RegisterThe public register of Telegram

Channel

𝙃𝙚𝙚𝙡 𝙛𝙡𝙤𝙤𝙙 - 𝙄𝙉𝙁𝙊 (𝟏𝟒+)

@heelflood

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

88subscribers

+0 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-1003854954191
TypeChannel
Username@heelflood
CreatedBetween 1 February 2026 and 27 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/heelflood

Growth

8813 Aug 2026, 19:47 — 88 subscribers14 Aug 2026, 11:26 — 88 subscribers13 Aug 2026, 19:4714 Aug 2026, 11:26
2 measurements taken within a single day. 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 87–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 11:2688no change
13 Aug 2026, 19:4788first reading

Engagement

20 posts held, back to 27 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

95 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 15.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52152244392931171261515.8%
custom 52715559074975252361212.6%
custom 52155245716077584311010.5%
custom 52157065536670567161010.5%
custom 52695686862592057541010.5%
custom 530769383534049386188.42%
custom 532829291939893038488.42%
custom 544280472326453013288.42%
custom 544302064415540334277.37%
custom 541132190861023664544.21%
custom 522877805470419598933.16%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 10 of the 20 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 95reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 27 June 2026 to 27 June 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

27 Jun 2026, 17:58 UTC114 views9 reactionsread 13 August 2026
Video

🔠🔠🔠 🔠🔠🔠🔠🔠 Сегодня два прекрасных флуда заключили союз: 27 июня 2026 года ➿➖➿➖➿➖➿➖➿➖➿➖➿ 🤍Heel Flood & Cherish Flood🤍 🔣Owner Heel Flood - Пак Гю Ён 🔣Owner Cherish Flood - Роха

custom 53076938353404938612custom 52152244392931171261custom 52155245716077584311custom 52157065536670567161custom 52695686862592057541custom 52715559074975252361custom 53282929193989303841custom 54428047232645301321

27 Jun 2026, 15:46 UTC141 views12 reactionsread 13 August 2026

очень надеюсь, что вам нравится🥺 если это так - рк!! #сзрп #hlrp

custom 52152244392931171262custom 52155245716077584312custom 53282929193989303842custom 54428047232645301322custom 52157065536670567161custom 52695686862592057541custom 52715559074975252361custom 53076938353404938611

27 Jun 2026, 15:43 UTC111 views11 reactionsread 13 August 2026

список союзов папка союзов • glimmer • richril • sayоmi • Salty • onion • helmmis • chaconne • moonlight • salted candies • moon life • black flower • youngs • viwies • nebula • vellore • ridless • cute • подслушано кмдф • evening • cherish

custom 52715559074975252363custom 54113219086102366453custom 52152244392931171262custom 52155245716077584311custom 53282929193989303841custom 54428047232645301321

27 Jun 2026, 15:43 UTC136 views13 reactionsread 13 August 2026

ㅤ ㅤ 🔣🔠🔠🔠🔠🔠🔠🔣 🤍Правила для союза: 🔣Обязательна подписка на тгк союзника. 🔣Делаем союзы от 30+ подписчиков в инфо. 🔣Доступна подписка 1:1 - 4:4. 🔣Репосты публикаций, под которыми указан хештег #сзрп, #hlrp. 🔣Мы не принимаем участие в чистках и сами их не проводим. ✖️ Разрыв: 🔣При закрытии одного из флудов. 🔣При отписки следящего/допов. 🔣При неактиве в инфо или при его засорении. 🔤аши союзы - тык 💤💤💤💤💤💤💤💤💤💤💤 По

custom 52695686862592057543custom 54430206441554033423custom 52152244392931171262custom 53282929193989303842custom 52155245716077584311custom 52715559074975252361custom 54428047232645301321

27 Jun 2026, 15:42 UTC82 views10 reactionsread 13 August 2026

ㅤ ㅤ➡️🔠🔡🔡🔡🔡🔡🔡🔡⬅️ 𝄃ࣼ Чистка проходит каждое воскресенье. 𝄃ࣼ Норма - 210 сообщений в неделю. 𝄃ࣼ Дневная норма на чистке не учитывается, но за полное её отсутствие (пред) 𝄃ࣼ Во время чистки запрещается писать, если кто-то написал / отправил стикер во время чистки (пред) 🔣НОРМА ДЛЯ НЬЮ🔣 Если вы находитесь во флуде менее 3 дней, ваша норма никак не будет учитываться при чистке. Если же вы находитесь во флу

custom 53076938353404938613custom 52157065536670567162custom 54430206441554033422custom 52155245716077584311custom 52287780547041959891custom 52715559074975252361

27 Jun 2026, 15:39 UTC95 views10 reactionsread 13 August 2026
Photo

ㅤ ㅤㅤ 🔠🔠🔠🔠🔠🔠 Со дня открытия флуда мы официально устанавливаем патент на название ( 𝙃𝙚𝙚𝙡 𝙛𝙡𝙤𝙤𝙙 ) Если мы узнаем о существовании флуда в кмдф с таким же названием, будем вынуждены потребовать его изменения Патент действителен с 25.02.2026г.

custom 52715559074975252363custom 52152244392931171262custom 54428047232645301322custom 52155245716077584311custom 52695686862592057541custom 53282929193989303841

Showing the 12 most recent of 20 posts we hold for @heelflood. 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 — 443,230 of 1,350,102entries 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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“𝙃𝙚𝙚𝙡 𝙛𝙡𝙤𝙤𝙙 - 𝙄𝙉𝙁𝙊 (𝟏𝟒+)” (@heelflood), 88 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/heelflood.

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.