Channel
@chaesdiaries
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
551subscribers
+97 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003155631178 |
|---|---|
| Type | Channel |
| Username | @chaesdiaries |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/chaesdiaries |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 11:59 | 551 | +13 |
| 8 Sept 2026, 03:41 | 538 | +16 |
| 30 Aug 2026, 16:26 | 522 | +11 |
| 24 Aug 2026, 03:54 | 511 | +9 |
| 17 Aug 2026, 12:05 | 502 | +46 |
| 9 Aug 2026, 08:31 | 456 | +2 |
| 8 Aug 2026, 19:00 | 454 | no change |
| 8 Aug 2026, 18:53 | 454 | first reading |
14 posts held, back to 7 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 14 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
225 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 37.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350594382464591042 | 85 | 37.8% | |
| custom 5310114139606111665 | 73 | 32.4% | |
| custom 5348333382830954930 | 67 | 29.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 7 of the 14 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 225 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 7 August 2026 to 8 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 531011413960611166513custom 534833338283095493010custom 53505943824645910429
Sticker, posted without a caption
▫️ suddenly & bad boy
custom 531011413960611166511custom 53505943824645910428custom 53483333828309549307
Sticker, posted without a caption
▫️ 🤩 :: а также иччи представили новые сольники!! черён исполнила кавер на песню «full moon» от sunmi. а рэп партию в этой песне за черён исполнила рюджин 🥺 my precious ryuryeong !! ▫️
custom 535059438246459104213custom 53101141396061116659custom 53483333828309549307
Sticker, posted without a caption
▫️ # 🌟🌸 сегодня проходит первый из двух фанмитингов итзи, на котором девочки finally исполнили легенду cheshire !! — мы ждали долгих 4 года, чтобы услышать её вновь… посмотрите на замечательные наряды девочек и самую крутую хореографию <3 ▫️
custom 535059438246459104212custom 53101141396061116659custom 53483333828309549309
Sticker, posted without a caption
& it’s time for some new notes!! 🎀 chaery writes on #instagram : кофе очень вкусный… какой это сорт зерен? спасибооо, я хорошо поем и буду набираться сил ❤️ ⠀ 👻 wrote a diary entry on 08.08 ➡️ by chae’s diaries
custom 535059438246459104218custom 534833338283095493010custom 53101141396061116659
Sticker, posted without a caption
& it’s time for some new notes!! 🎀 chaery writes on #youtube : tour-log ep. 01 | tokyo — ссылка ⠀ 👻 wrote a diary entry on 07.08 ➡️ by chae’s diaries
custom 534833338283095493013custom 535059438246459104211custom 531011413960611166510
Sticker, posted without a caption
Showing the 12 most recent of 14 posts we hold for @chaesdiaries. 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.
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 7 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“۶ৎ chae’s diaries” (@chaesdiaries), 551 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/chaesdiaries.
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.