🎀 ᯓ. . .deirix. .𐙚 выбирайте нас ⚡|Сукуна
custom 54697622873613629363custom 53683032627704049012custom 53416520629858064411custom 53440233273148341081
Signed tom DX

Channel
@deirixflood
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
119subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001953276639 |
|---|---|
| Type | Channel |
| Username | @deirixflood |
| Description | OWNER — @qllosw ANKETS — @deirixxx REST — @deirixw |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/deirixflood |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 04:17 | 119 | no change |
| 9 Aug 2026, 02:00 | 119 | first reading |
16 posts held, back to 15 August 2025 — the 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 16 posts for this entry, the most recent from 16 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
118 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 27.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5341652062985806441 | 32 | 27.1% | |
| custom 5368303262770404901 | 27 | 22.9% | |
| custom 5344023327314834108 | 17 | 14.4% | |
| custom 5469762287361362936 | 13 | 11.0% | |
| custom 5253483144677448861 | 12 | 10.2% | |
| custom 5201686496217678925 | 10 | 8.47% | |
| custom 5253541929894831856 | 7 | 5.93% |
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 15 of the 16 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 118reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 15 August 2025 to 16 February 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.
🎀 ᯓ. . .deirix. .𐙚 выбирайте нас ⚡|Сукуна
custom 54697622873613629363custom 53683032627704049012custom 53416520629858064411custom 53440233273148341081
Signed tom DX
🎀 ᯓ. . .deirix. .𐙚 хейтите эту херню ⚡|Сукуна
custom 53683032627704049013custom 52535419298948318561custom 54697622873613629361
Signed tom
🎀 ᯓ. . .deirix. .𐙚 были времена, а сейчас моменты ⚡|Сукуна
custom 52534831446774488615custom 53416520629858064413custom 53683032627704049011
Signed tom
🎀 ᯓ. . .deirix. .𐙚 по херне так ⚡|Сукуна
custom 52534831446774488617custom 53683032627704049011custom 54697622873613629361
Signed tom
💭 Как вступить в чат? внимательно ознакомьтесь с информацией в анкетнице (@deirixxx). заполните анкету полностью строго по шаблону. а после дождитесь ответа администрации. по поводу вступления напишите админам. рады каждому. ❤️
Signed tom
👻👻➖➖➖➖➖ ((✨)) 👻👻 👻👻: Перед тем как заключить 👻👻союз ознакомьтесь с условиями. по поводу сотрудничества: @kurowz
custom 54697622873613629363custom 53416520629858064412custom 53683032627704049012
Signed tom
👻👻➖➖➖➖➖➖➖➖ ((✨)) 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ : Инициалы обозначают, что вы находитесь или поддерживаете проект. 🥹 #DX
custom 53683032627704049015custom 54697622873613629362custom 53416520629858064411
Signed tom
👻👻➖➖➖➖➖➖ ((✨)) 🎤 - на должности, готов к работе. ⌨ - в ресте, не беспокоить. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🎤Сукуна/Том: (он/его) - Создатель проекта.Также занимается всеми основными моментами. Связаться лично: @kurowz 🎤Макима/Солл: (она/её) - Владелец проекта. Занимается всеми основными моментами флуда, вся ответственность на его плечах. Связаться лично: @fxwer1y
custom 53683032627704049013custom 53416520629858064412custom 54697622873613629362
Signed tom
👻👻➖➖➖➖➖➖➖➖➖(( ✨)) 🔍RULES 👤ADMINISTRATION 👥UNION 📎INITIALS 🔗TIK TOK 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 #DX
custom 53683032627704049014custom 53416520629858064412custom 54697622873613629361
Signed tom
🎀 ᯓ. . .deirix. .𐙚 ⚡автор: @Kw1rtyMi4x
custom 53416520629858064414custom 53440233273148341082custom 53683032627704049011
Signed tom
🎀 ᯓ. . .deirix. .𐙚 🎀Чипер
custom 53416520629858064416custom 52535419298948318562custom 53440233273148341082
Signed sskqwa
🎀 ᯓ. . .deirix. .𐙚 Возращаемся 🎀Чипер
custom 53416520629858064416custom 52016864962176789253custom 53683032627704049013
Signed sskqwa
Showing the 12 most recent of 16 posts we hold for @deirixflood. 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 — 660,078 of 1,478,351entries 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@deirixflood named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“|| - 𝙙𝙚𝙞𝙧𝙞𝙭𝙘𝙝𝙖𝙣𝙣𝙚𝙡” (@deirixflood), 119 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/deirixflood.
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.