Telegram RegisterThe public register of Telegram

Channel

𝐌𝐈𝐂𝐇𝐈’𝐆𝐎

@michigocdt

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

158subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001574257817
TypeChannel
Username@michigocdt
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/michigocdt

Growth

1588 Aug 2026, 19:30 — 158 subscribers9 Aug 2026, 01:13 — 158 subscribers8 Aug 2026, 19:309 Aug 2026, 01:13
2 measurements taken within a single day. 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”. The vertical axis spans 157–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 01:13158no change
8 Aug 2026, 19:30158first reading

Engagement

20 posts held, back to 30 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 26 September 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

615 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 30.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘18630.2%
custom 527388674329936874718229.6%
😈12420.2%
👾6811.1%
🦄558.94%

Custom emoji. One 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 count beside it isTelegram’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 18 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 615reactions 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 30 August 2025 to 26 September 2025, 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

26 Sept 2025, 15:03 UTC776 views43 reactionsread 8 August 2026
Photo

⭐ ••🤩🤩🤩🤩🤩🤩🤩•• 🤩HINee’s in the house 🤍ONEW — MIN 🤍KEY — YOUNGMI 🤍MINHO — RAFUL 🤍JONGHYUN — VIKS 🤍TAEMIN — KISS Оператор: HAEYEON 🤍 Это наш последний кавер на этом канале, спасибо, что были с нами! С любовью, Ваши MICHI’GO.

custom 527388674329936874721🦄10👾9💘3

25 Sept 2025, 16:20 UTC651 views26 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩 🤩HINee — 🤩herlock TAEMIN → KISS 🎤 너의 떨린 숨결 하나까지 놓치지 않아 은밀하게 노린 심장의 보석.

💘9😈8custom 52738867432993687477👾1🦄1

24 Sept 2025, 17:00 UTC481 views28 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩 🤩HINee — 🤩herlock JONGHYUN → VIKS 🎤 지금부터 all stop 어느 누구라 해도 이 현장을 벗어나선 안 돼 명백한 이 사건 속에 긴장하지 마.

😈11💘9custom 52738867432993687477👾1

24 Sept 2025, 15:00 UTC416 views30 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩 🤩HINee — 🤩herlock MINHO → RAFUL 🎤 하루에도 수백 번씩 널 떠올리다 떨쳐내다 내 머릿속을 채운 의문 네가 원한 것이 뭔가.

💘12😈7🦄5custom 52738867432993687475👾1

23 Sept 2025, 18:00 UTC376 views36 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩 🤩HINee — 🤩herlock KEY → YOUNGMI 🎤 너의 불안한 그 시선까지 꿰뚫었어 난 용의선상의 널 찾아냈어 난 freeze.

🦄12😈9💘7👾4custom 52738867432993687474

23 Sept 2025, 16:00 UTC396 views37 reactionsread 8 August 2026
Photo

🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩 🤩HINee — 🤩herlock ONEW → MIN 🎤 지금 내 앞에 너는 실재 하지 않아 분명 알지만 너를 심문하겠어 내가 원한 대답 너는 알고 있어.

💘16😈9custom 52738867432993687478👾2🦄2

4 Sept 2025, 10:54 UTC620 views67 reactionsread 8 August 2026
Photo

доброго всем дня, на связи Мичиго! возможно для кого то эта новость покажется странной, кто то будет грустить, а может кто то и вовсе будет рад, но наша команда решила поставить точку в общей танцевальной деятельности. Мичиго - это большая история длинною в 12 лет. бывает так, что цели и взгляд на деятельность начинают разниться, но мы все еще любим друг друга и благодарны каждому за поддержку все это долгое время.

custom 527388674329936874732💘21👾14

3 Sept 2025, 07:58 UTC573 views36 reactionsread 8 August 2026
Photo

✨😉🙃😂😆😌😀😄😊🥸🥹😇✨ Сегодня уже 3️⃣ сентября, а значит мы поздравляем нашего лидера С Днем Рождения! ◾️От всей команды хотим пожелать тебе вылечить колени на столько хорошо, на сколько ты отыгрываешь партии Сана!! Успехов тебе в любых твоих начинаниях, чтобы в твоей жизни было меньше преград на пути к свершению твоих мечт ◾️Обязательно люби себя, потому что наша любовь и благодарность тебе останется навечно!

custom 527388674329936874715💘10😈10👾1

1 Sept 2025, 17:02 UTC≈2,230 views23 reactionsread 8 August 2026
Photo

🌟 🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ Вышел в свет долгожданный и элегантный кавер на: 🩹🩹🩹🩹🩹🩹🩹🩹🩹🩹🩹🩹 🩹 🩹🩹🩹🩹🩹🩹 Поэтому предлагаем его посмотреть по этой ссылке 🤩🤩🤩🤩🤩🤩🤩🤩 🌟Хореограф, обработка фото - Youngmi 🌟Оператор - Satori Также в кавере приняли участие участники DQ, STVixi, Timeless и MAV ➿➿➿➿➿➿➿➿➿➿➿➿➿ Приятного просмотра🌟

💘12😈6custom 52738867432993687475

1 Sept 2025, 15:01 UTC737 views20 reactionsread 8 August 2026
Photo

🅰️🅰️🅰️🅰️🅰️🅰️ 🅰️🅰️🅰️🅰️🅰️ 🤩🤩🤩🤩🤩🤩🤩🤩 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ 🔠🔠🔠🔠🔠🔠 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ 🩹🩹🩹🩹🩹🩹🩹🩹🩹🩹🩹 🌧️Mew(DQ)🌧️ 🌧️Rumy(Timeless)🌧️

💘12😈4custom 52738867432993687474

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

Citation-graph rank

Citation-graph rank — 1,080,912 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 1 registered channel — 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“𝐌𝐈𝐂𝐇𝐈’𝐆𝐎” (@michigocdt), 158 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/michigocdt.

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.