Sticker, posted without a caption

Channel
🔒 || м郃у ƒℓσσ∂ `ʍ⁰⁶ | ιηƒσ ᥫ᭡
@miffyfloodinfo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
46subscribers
+4 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003811942045 |
|---|---|
| Type | Channel |
| Username | @miffyfloodinfo |
| Created | Between 1 February 2026 and 17 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/miffyfloodinfo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 05:56 | 46 | -6 |
| 4 Sept 2026, 14:16 | 52 | -2 |
| 27 Aug 2026, 15:43 | 54 | +9 |
| 20 Aug 2026, 05:26 | 45 | +3 |
| 12 Aug 2026, 08:30 | 42 | no change |
| 12 Aug 2026, 08:16 | 42 | first reading |
Engagement
20 posts held, back to 17 July 2026 — 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 page of 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 23s
- Average length
- 8s
Measured directly from 3 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.
Reaction mix
7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 42.9% | |
| custom 5221940758826743186 | 2 | 28.6% | |
| custom 5229083018857038563 | 2 | 28.6% |
Custom emoji. 2 of the rows above are 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 are Telegram’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 3 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 7 reactions 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 17 July 2026 to 1 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
— the end?.. — yes.. #феликс:: здравствуйте,на связи владелец.я пришёл к выводу,что рест нам не помог и желание дальше вести флуд не появилось,хотя я искренне надеялся,что мы вернёмся с новыми силами.увы,не всё так просто.миффи закрывается.временно или нет,я пока не решил.может быть,когда-нибудь в будущем я открою его снова и он расцветёт новыми красками,с нью эрой,но врядли это случится в ближа…
custom 52290830188570385631
Sticker, posted without a caption
рады сотрудничеству!!
⭐⭐⚫️ᴇᴡ ⚫️ɴɪᴏɴ. 🌟🌟🌟🌟 🤩ы @miffyfloodinfo ᴛᴀнцуᴇɯь ᴋᴀᴋ будᴛᴏ ᴏднᴀ 🤩ᴏ я @solofloodinf дᴇᴧᴀю ʙид, чᴛᴏ уʍᴇю быᴛь ᴄᴋᴩᴏʍныʍ. 🤩ы нᴇ ᴄᴋᴩᴏᴇʍᴄя ᴛᴏчнᴏ ᴄᴋᴏᴧьᴋᴏ нᴇ ᴨᴏʍᴇняᴧи бы ᴋᴏʍнᴀᴛ. 🤩 @solofloodinf ᴄʍᴏᴛᴩю нᴀ ᴛᴇбя и жᴀᴧᴇю, чᴛᴏ ʍы ϶ᴛᴏ дᴀжᴇ нᴇ ʙᴄᴨᴏʍниʍ. 🤩ᴏ, уʙы, ϶ᴛᴏ дᴀжᴇ нᴇ ᴄᴨᴏйᴧᴇᴩ 🤩 ᴄнᴏʙᴀ уᴄᴧыɯу… ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ 🤩ы @miffyfloodinfo хᴏᴧᴏдный ᴄнᴇжный ᴨᴩинц. 🤩нуᴛᴩи @miffyfloodinfo ᴛʙᴏᴇй ᴦᴩуди ᴋᴩᴀᴄныᴇ яɜыᴋи. 🤩… 🤩 ᴏᴛбиʙɯиᴄ…
Sticker, posted without a caption
#феликс зайкии!!вы мне тоже нравитесь,люблю💓
ƇɾuʂԊ ℓISΤ люблю всех своих союзов, но этих чуть больше 💕 1.@poffoosfld не знаю почему, но их люблю особенно, у них такой классный вайб, и влд очень нравится 2.@Love_and_Desert их люблю без причины, тоже очень комфортный, приятный владелец 3.@aeris_flood тоже люблю без причины, у них такая классная атмосфера 4.@miffyfloodinfo владелец нравится 5.@splflood не сдержалась и добавила их, даже если закрыты, они мои…
Sticker, posted without a caption
рады союзу!!
заключили замечательный союз 🇺🇸🇺🇸 @miffyfloodinfo, очень очень любим вас и надеемся на долгое сотрудничество ❤️🔥❤️🔥
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @miffyfloodinfo. 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.
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
Names
Channels on the register whose handles appear in this channel's posts.
@young_lixxie · 52 posts🪷•Aeris flood•~ info
@aeris_flood · 1011 post៹ ' あ ‶ cher͛r͛y ` ruşhh . .ᐟ
@chrrsh · 5641 postРест рп|𝐋𝐀𝐃⁀➴ᴸᵒᵛᵉ ᴬⁿᵈ ᴰᵉˢᵉʳᵗ|info
@Love_and_Desert · 531 post𝑴𝒂𝒇𝒊𝒂 𝒊𝒏 𝒍𝒂𝒘 ⁱⁿᶠᵒ
@mafiainf0 · 2281 postⓘ poffoos flood . .
@poffoosfld · 2481 postЧИСТКА СЗ / sᴏʟᴏ ꜰʟᴏᴏᴅ | ɪɴꜰᴏ ⊹ ࣪ ˖
@solofloodinf · 2861 post𝘴𝘱𝘢𝘳𝘬𝘭𝘦
@splflood · 1301 post
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“🔒 || м郃у ƒℓσσ∂ `ʍ⁰⁶ | ιηƒσ ᥫ᭡” (@miffyfloodinfo), 46 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/miffyfloodinfo.
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.