Channel
@cherishflood1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
484subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002738944752 |
|---|---|
| Type | Channel |
| Username | @cherishflood1 |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/cherishflood1 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 |
|---|---|---|
| 16 Sept 2026, 18:58 | 484 | -1 |
| 8 Sept 2026, 19:42 | 485 | -8 |
| 30 Aug 2026, 15:07 | 493 | -4 |
| 22 Aug 2026, 20:23 | 497 | +10 |
| 15 Aug 2026, 19:38 | 487 | +7 |
| 9 Aug 2026, 07:51 | 480 | -3 |
| 8 Aug 2026, 11:50 | 483 | no change |
| 8 Aug 2026, 11:49 | 483 | first reading |
18 posts held, back to 3 August 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
20 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5316547682787929527 | 7 | 35.0% | |
| custom 5317024192229552480 | 6 | 30.0% | |
| custom 5422767798885587954 | 4 | 20.0% | |
| custom 5348258036219683166 | 2 | 10.0% | |
| custom 5314580093845131813 | 1 | 5.00% |
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 3 of the 18 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 3 August 2026 to 7 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.
ники ненавидит японцев поэтому довел бедную девочку до такого изверг Япония самая умная раса гребаный расист
custom 53165476827879295273custom 54227677988855879543custom 53170241922295524802
Signed Caramel York
Вы бы не могли подписать мою петицию https://www.change.org/p/protect-ni-ki-and-his-family?redirect_reason=guest_user
Signed Caramel York
Sticker, posted without a caption
Signed Caramel York
#cherirp
Signed Caramel York
݁🍚𝖳ⲓ𝗄ׅ𝖳ᨷׅ𝗄 ᚐ 🤩 ݁ ׅ𝗎𝗉ׅ𝖽ɑ𝗍𝖾 ݁ 꿈 달빛 : 𝗒𝗎𝗇𝖺𝗁 ! ! 빛 🤍 𝖨𝖣 : 𝗇݁ᨷׅ𝗍 𝗈ׅ𝗎𝗋ຣ; 𝗍𝗁ᧉ݁ 𝖺݁𝗎𝗍𝗁ׅ𑄜𝗋 𝗁݁𝖺ຣ ხׅ𝖾𝖾𝗇 𝖼𝗋ׅ𝖾𝖽݁Ꭵ𝗍ׅ𝖾𝖽
custom 53145800938451318131custom 53165476827879295271custom 53170241922295524801
Signed Caramel York
Sticker, posted without a caption
Signed Caramel York
Отдыхайте😢😢
Signed Caramel York
❌ 𝗆𝖺ᧁׁ𝗂𝖼𝖺𝗅﹙ 마법✨﹚𝗌𝖺𝗄𝗎𝗐ɑׁׅ 𝗆ꫀׁׅ𝗌𝗌𝖺𝗀𝖾 : аяша тепепь хаым......... ✨ 𝖬𝖵 𝖿𝗈𝗋 Haum 유형
Signed Caramel York
家 Nꫀׁw Video ׅ ꒰ 🤍ᛝ ٔ꒱ ּ 🎐 Mαde by Mokαׅ ⋮⋮ ֹ ⋮⋮ ֹ Beauty ⎯⎯ Heart .
Signed Caramel York
Sticker, posted without a caption
Signed Mistake
Оба списка исправлены, если кого-то не добавили, то напишите под этим сообщением
Signed Mistake
Sticker, posted without a caption
Signed Mistake
Showing the 12 most recent of 18 posts we hold for @cherishflood1. 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 8 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“『他』ׅ 𝑪h𝗲𝗿𝗶𝘀𝗵 ۫” (@cherishflood1), 484 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/cherishflood1.
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.