Channel
@Chancy_flood
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
279subscribers
-55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003410542165 |
|---|---|
| Type | Channel |
| Username | @Chancy_flood |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/Chancy_flood |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 76% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 21:41 | 279 | -23 |
| 14 Sept 2026, 05:21 | 302 | -6 |
| 6 Sept 2026, 22:41 | 308 | -4 |
| 29 Aug 2026, 09:15 | 312 | -6 |
| 23 Aug 2026, 03:17 | 318 | -10 |
| 15 Aug 2026, 00:02 | 328 | -7 |
| 7 Aug 2026, 00:41 | 335 | +1 |
| 6 Aug 2026, 21:46 | 334 | no change |
| 6 Aug 2026, 19:15 | 334 | first reading |
17 posts held, back to 19 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
34 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249169459913991955 | 8 | 23.5% | |
| custom 5249193584745292710 | 8 | 23.5% | |
| custom 5251545702110108212 | 8 | 23.5% | |
| custom 5251404994686523185 | 6 | 17.6% | |
| custom 5249334996543512936 | 4 | 11.8% |
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 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 13 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 34 reactions 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 19 July 2026 to 6 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.
#Minji мои дорогие, есть один живодёр, который создал новый канал, где уже записал видео, как отрезал котёнку лапки, прошу кинуть жалобы на кнопку «жестокое обращение с животными»!! @cutecats20 @cutecats20 @cutecats20 буду благодарна вам!!
custom 52514049946865231851
Signed кимми мяу ᶜʰᵃᶰᶜʸ
рады союзу!
custom 52515457021101082121
Signed кимми мяу ᶜʰᵃᶰᶜʸ
@hailaid »»@Chancy_flood О4.О8 «« Надевай свой модный лук, и зови своих подруг) Пусть танцуют все вокруг, этот бит качает двух❕ »» Надеемся на долгое, и дружное сотрудничество!
custom 52491694599139919551
Signed кимми мяу ᶜʰᵃᶰᶜʸ
➖➖➖➖✍️ 🔤𝑒𝑤 𝑢𝑛𝑖𝑜𝑛 ˊˎ- 🥹🥹Сᴇᴦᴏдня ʍы ᴩᴀды ᴏбъяʙиᴛь ᴏ ɜᴀᴋᴧючᴇнии ᴄᴏюɜᴀ ʍᴇжду... ➖ @Chancy_flood и @midnightinfofld 🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹 Рады сотрудничеству, надеемся на долгий союз..🌈
custom 52491694599139919552
Signed кимми мяу ᶜʰᵃᶰᶜʸ
с последним месяцем лета вас..
custom 52493349965435129362
Signed кимми мяу ᶜʰᵃᶰᶜʸ
#chnrp напоминаю
custom 52491694599139919551
Signed кимми мяу ᶜʰᵃᶰᶜʸ
так, мы поменяли название с murmeow на chancy, и в связи с этим мы меняем ссылку на канал была - https://t.me/MurMeow_flood стала - https://t.me/Chancy_flood
custom 52491694599139919551custom 52491935847452927101custom 52515457021101082121
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
#chnrp + мнение 🐸
custom 52514049946865231851custom 52515457021101082121
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
Sticker, posted without a caption
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
Sticker, posted without a caption
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
➖➖ 🔤ы ᥙщеⲙ ᥴ᧐юзы! ➖➖ нᴀɯи ᴨᴩᴀʙиᴧᴀ 🤩 ➖ ʍᴀᴋᴄ ᴨᴏдᴨиᴄᴋᴀ 4:4🎤 ➖➖ ᴨᴏᴄᴛ ᴄ ʙᴀᴄ/ᴄ нᴀᴄ 🤩 ❤️ ⲡυⲥⲁⲧь🥹@reddie_sv
custom 52491694599139919551custom 52491935847452927101custom 52515457021101082121
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
➖➖➖ 🔤hancy ᥙщᥱт ➖ ᧐ᴛʙᥱᴛᥴᴛʙᥱнны᥊ ᥲдⲙᥙн᧐ʙ! ищᴇʍ: 🤎 ᴀдʍинᴀ ᴨᴏ нью ➖🤎ᴄᴛᴀᴩɯᴇᴦᴏ ᴀдʍинᴀ 🤎ᴀдʍинᴀ ᴨᴏ ᴀᴋᴛиʙу ➖🤎ʍᴏнᴛᴀжᴇᴩᴀ 📤ᴨᴩᴀʙиᴧᴀ дᴧя ᴛᴏᴦᴏ чᴛᴏбы ᴄᴛᴀᴛь ᴀдʍинᴏʍ: 🥹 быᴛь ʙᴏ ɸᴧудᴇ ʍиниʍуʍ нᴇдᴇᴧю 🥹 быᴛь ᴀᴋᴛиʙныʍ учᴀᴄᴛниᴋᴏʍ 🥹 ɜᴀᴨᴏᴧниᴛь ᴀнᴋᴇᴛу (ᴇᴇ ʍᴏжнᴏ ᴨᴏᴨᴩᴏᴄиᴛь у ʙᴧд иᴧи ᴄᴏʙᴧд) дᴧя ᴛᴏᴦᴏ чᴛᴏ бы ᴄᴛᴀᴛь ᴀдʍинᴏʍ ᴨиᴄᴀᴛь 🥹 @Nancy_murr
custom 52491935847452927101custom 52514049946865231851custom 52515457021101082121
Signed кимми мяу ᴹᵘʳᴹᵉᵒʷ
Showing the 12 most recent of 17 posts we hold for @Chancy_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.
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.
Named by 3 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.
@Chancy_flood 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“🍬 » ˖ ࣪ 𝐂hᥲꪦ𝖼y ִ ࣪ ˖ #инфо” (@Chancy_flood), 279 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Chancy_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.