Telegram RegisterThe public register of Telegram
Telegram profile photo for ಣ𓈒ֵ۫ ˚ ̣𝑶𝐧𝐞𝐢𝐫𝐢𝐜 𝓐𝐧𝐠𝐞𝐥, 𝐂𝐡𝐨𝒊 𝐉𝒊𝐬𝐮.

Channel

ಣ𓈒ֵ۫ ˚ ̣𝑶𝐧𝐞𝐢𝐫𝐢𝐜 𝓐𝐧𝐠𝐞𝐥, 𝐂𝐡𝐨𝒊 𝐉𝒊𝐬𝐮.

@cchoijisu

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

107subscribers

+103 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002435158425
TypeChannel
Username@cchoijisu
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live1 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/cchoijisu

Topic

Music — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 the other topics.

Growth

41105714 August 2026 — 4 subscribers22 August 2026 — 45 subscribers29 August 2026 — 74 subscribers5 September 2026 — 88 subscribers13 September 2026 — 103 subscribers13 September 2026 — 103 subscribers2 October 2026 — 109 subscribers12 October 2026 — 110 subscribers18 October 2026 — 109 subscribers24 October 2026 — 108 subscribers1 November 2026 — 107 subscribers10714 August 20261 November 2026
11 measurements spanning 79 days, net +103. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Nov 2026, 07:15107-1
24 Oct 2026, 23:06108-1
18 Oct 2026, 22:10109-1
12 Oct 2026, 01:41110+1
2 Oct 2026, 07:57109+6
13 Sept 2026, 05:22103no change
13 Sept 2026, 04:15103+15
5 Sept 2026, 06:5888+14
29 Aug 2026, 10:3774+29
22 Aug 2026, 16:5345+41
14 Aug 2026, 04:314first reading

Engagement

12 posts held, back to 8 September 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 12 posts for this entry, the most recent from 13 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
21s
Average length
11s

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.

Recent posts

13 Sept 2026, 04:16 UTC5 viewsread 13 September 2026
Photo

ㅤ ㅤㅤㅤㅤㅤ ゚⃝ ۪♪ㅤㅤㅤ ˚⠀ㅤㅤㅤ⋅.˳˳.ᩘ♡ ㅤㅤㅤ 𝐈𝐓𝐙𝐘 𝟑𝐑𝐃 𝐖𝐎𝐑𝐋𝐃 𝐓𝐎𝐔𝐑 ㅤㅤㅤㅤㅤ <𝐓𝐔𝐍𝐍𝐄𝐋 𝐕𝐈𝐒𝐈𝐎𝐍> ㅤㅤㅤㅤ ⢎⣈⠤⡠⠒⠒⠦⣄ ♥︎ 。゚♡⃞゙𑈴𖹭ׄᰍ ㅤ ㅤ

13 Sept 2026, 04:16 UTC5 viewsread 13 September 2026
Photo

ㅤ ▩ ུ۪۪ ❁ 𝐈𝐓𝐙𝐘𝐨𝐟𝐟𝐢𝐜𝐢𝐚𝐥.⠀ ๑ ྀི˚ what a night, London! 💕 you were absolutely brilliant from beginning to end, and we could feel your love in every corner of the venue. thank you for singing your hearts out, cheering as loudly as you could, and making every moment on stage feel so special. seeing all of your lights shining back at us and hearing your voices fill the venue was a sight and sound we’ll never forget. pr…

13 Sept 2026, 04:10 UTC9 viewsread 13 September 2026

ㅤ ㅤㅤㅤ ㅤ ゚⃝ ۪♪ㅤㅤㅤ ˚⠀ㅤㅤㅤ⋅.˳˳.ᩘ♡ ㅤㅤㅤ 𝐈𝐓𝐙𝐘 𝟑𝐑𝐃 𝐖𝐎𝐑𝐋𝐃 𝐓𝐎𝐔𝐑 ㅤㅤㅤㅤ𝐓𝐔𝐍𝐍𝐄𝐋 𝐕𝐈𝐒𝐈𝐎𝐍 𝐢𝐧 𝐓𝐀𝐈𝐏𝐄𝐈 ㅤㅤㅤㅤ ⢎⣈⠤⡠⠒⠒⠦⣄ ♥︎ 。゚♡⃞゙𑈴𖹭ׄᰍ ㅤㅤㅤㅤㅤㅤㅤ 𝐈𝐓𝐙𝐘 “𝐃𝐘𝐓” ㅤ 𝐅𝐈𝐗 𝐂𝐀𝐌 𝐕𝐄𝐑 & 𝐂𝐎𝐍𝐂𝐄𝐑𝐓 𝐂𝐀𝐌 𝐕𝐄𝐑 ㅤ

10 Sept 2026, 13:16 UTC30 viewsread 13 September 2026
Photo

ㅤㅤ ⠀𝐄𝐏. 𝟎𝟑 𝐑𝐄𝐕𝐈𝐄𝐖: 𝐈𝐓’𝐒 𝐒𝐎𝐎𝐎 𝐎𝐍𝐄 𝐓𝐄𝐀𝐌! ㅤㅤ𓐇𓈒   .   𑁍ུ ࣪ 𓈒 ㅤㅤ

10 Sept 2026, 13:16 UTC30 viewsread 13 September 2026

ㅤㅤ ⠀ ㅤ 𖹭𖹭𓈒˳˳𓈒ㅤㅤ 𝐃𝐚𝐃𝐚𝐈𝐓𝐙𝐘ㅤㅤ ࿁ ˚ ೀ⠀ ㅤ<다다있지> 𝐄𝐏. 𝟎𝟑 | 우리 화내지 않기로 해용~ ㅤㅤㅤ 비난과 야유로 얼룩진 의리 게임 🔥 ⠀. ⠀⚇ꥈ⠀ ㅤ ݁ ㅤׅ⠀ ˚⠀⠀๑ㅤׅㅤㅤ.ㅤ ݁ ⠀ ‧ ˚ㅤ ♡ in today’s episode of 다다있지, we wore matching outfits because 𝐈𝐓𝐙𝐘 is one! >___< from the very beginning, i was so curious about what was hiding underneath the black cloth. when i finally opened it, it turned out to be lemon juice! 🍋 today’s theme was loyalty, and we had to …

10 Sept 2026, 13:16 UTC21 viewsread 13 September 2026
Photo

ㅤㅤ ㅤㅤㅤ𖹭𖹭𓈒˳˳𓈒ㅤ #𝐃𝐚𝐃𝐚𝐈𝐓𝐙𝐘ㅤㅤ࿁ ˚ ೀ⠀ ㅤㅤㅤㅤ 𓈒 ࣭ ⑅ 𝐄𝐏. 𝟎𝟑 𝐏𝐑𝐄𝐕𝐈𝐄𝐖 𓂅𓈒 ˖ ㅤㅤㅤㅤ. ⠀⚇ㅤׅ⠀ ˚⠀⠀๑ㅤׅㅤ ⠀ ‧ ˚ㅤ ♡ 믿지가 있지와 의리 지키는 법 💪 ➡️ 𝟔시가 되면 다다있지 보러 가기 ㅤㅤ

8 Sept 2026, 14:21 UTC28 viewsread 13 September 2026
Video

ㅤ ㅤㅤ𝑙𝑖𝑡𝑡𝑙𝑒 𝑑𝑎𝑖𝑙𝑦 𝑠𝑛𝑖𝑝𝑝𝑒𝑡𝑠 𝑜𝑓 𝑚𝑒 𝑎𝑛𝑑 𝐵𝑒𝑙𝑙𝑎 ₊˚ ᨦ ᨩ ݁ •̩̩͙ ᮬׁ ๋❈  ֗  ۪ ᅠᅠ ּㅤ . ㅤ

8 Sept 2026, 14:21 UTC27 viewsread 13 September 2026
Photo

ㅤ (𝚕𝚒𝚊_𝚕𝚘𝚟𝚎𝚜___) .ʚ⚉:͜͡:♡͙̣ here are some photo dumps i took from the days that have already passed. looking back, there have been so many little moments, sweet memories, and beautiful things along the way, so i thought it was finally time to gather some of them and share them with you too, 𝐌𝐈𝐃𝐙𝐘𝐬! i hope you enjoy taking a little peek into these moments with me. ♥️ one of the photos is from a cafe visit, where i go…

Showing the 12 most recent of 12 posts we hold for @cchoijisu. 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

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

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.

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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“ಣ𓈒ֵ۫ ˚ ̣𝑶𝐧𝐞𝐢𝐫𝐢𝐜 𝓐𝐧𝐠𝐞𝐥, 𝐂𝐡𝐨𝒊 𝐉𝒊𝐬𝐮.” (@cchoijisu), 107 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/cchoijisu.

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.