Telegram RegisterThe public register of Telegram
Telegram profile photo for •。˚𝑴𝒊𝒕𝒔𝒖𝒌𝒐!!𐙚

Channel

•。˚𝑴𝒊𝒕𝒔𝒖𝒌𝒐!!𐙚

@mitsukchu

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

120subscribers

+7 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-1002192425074
TypeChannel
Username@mitsukchu
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live25 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/mitsukchu

Topic

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Growth

113120116.58 August 2026 — 113 subscribers9 August 2026 — 113 subscribers10 September 2026 — 114 subscribers25 September 2026 — 120 subscribers8 August 202625 September 2026
4 measurements spanning 48 days, net +7. 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 112–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 03:42120+6
10 Sept 2026, 16:00114+1
9 Aug 2026, 06:18113no change
8 Aug 2026, 08:02113first reading

Engagement

14 posts held, back to 20 May 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 17s
Average length
15s

Measured directly from 5 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.

Reaction mix

161 reactions across 12 posts, in 17 distinct kinds. The most used accounts for 18.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52873662361648754092918.0%
🍓2515.5%
custom 5400262990593290686148.70%
💘127.45%
custom 5253893640471722908116.83%
custom 5289822519371524079116.83%
custom 5363848539870880922116.83%
custom 526256272701603737795.59%
custom 526521788438835656995.59%
custom 544089982366441156084.97%
custom 519497350957867282674.35%
custom 523337348932228151663.73%
custom 523583269740165488431.86%
custom 546963029872137951931.86%
custom 519495705126399321610.621%
custom 525384180021646150110.621%
custom 547430634987562157410.621%

Custom emoji. 15 of the rows above are 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 12 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 161 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 20 May 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.

Recent posts

7 Aug 2026, 07:05 UTC48 views3 reactionsread 9 August 2026

рт пж

🍓1custom 51949735095786728261custom 52538936404717229081

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

7 Aug 2026, 06:53 UTC213 views19 reactionsread 9 August 2026
Photo

0️⃣0️⃣☕️ ᴋᴇyᴏn!! 🍓 👻👻👻👻👻👻👻👻👻👻 昼に夜に朝にsinging so loud 好きなことしてるだけだよ Girls Go Maniac Ritsu😏 Yui🙏 Mio😰 Azusa😓 Tsumugi😂 ph🎵 #cosplay

custom 52538936404717229087custom 52333734893222815166custom 51949735095786728265custom 51949570512639932161

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

6 Aug 2026, 20:34 UTC61 views22 reactionsread 9 August 2026
Photo

АФ АФ ГАФ ГАФ ГАФ #cosplay

💘7🍓6custom 54002629905932906866custom 53638485398708809223

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

6 Aug 2026, 19:16 UTC60 views25 reactionsread 9 August 2026
Video

допустим превет эта клиника и до меня добралас #cosplay

custom 53638485398708809228custom 54002629905932906868custom 54408998236644115608custom 52538936404717229081

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

4 Aug 2026, 23:51 UTC299 views18 reactionsread 9 August 2026
Video

спойлер к будущему посту😏 пока што просто бэки с фотоса!! (я начинаю чучуть возвращаться) #cosplay

🍓6💘4custom 52358326974016548843custom 54696302987213795193custom 52538418002164615011custom 54743063498756215741

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

26 Jul 2026, 21:31 UTC97 views2 reactionsread 9 August 2026
Forwarded from @Kuroyami_Wu

Posted without readable text

custom 51949735095786728261custom 52873662361648754091

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

18 Jul 2026, 19:58 UTC109 views8 reactionsread 9 August 2026

Ребято привет… косплеи скоро будут, честно..

custom 52873662361648754095custom 52652178843883565692🍓1

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

25 May 2026, 19:03 UTC178 views18 reactionsread 9 August 2026
Video

🌟🌟🌟 #cosplay

custom 52873662361648754096custom 52898225193715240796🍓4custom 52625627270160373772

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

24 May 2026, 21:56 UTC156 views12 reactionsread 9 August 2026
Video

ну и все хватит #cosplay

custom 52625627270160373775🍓3custom 52873662361648754093custom 52652178843883565691

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

24 May 2026, 18:34 UTC166 views17 reactionsread 9 August 2026
Photo

не ну #cosplay

custom 52873662361648754097custom 52898225193715240795custom 52652178843883565693🍓2

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

23 May 2026, 19:45 UTC156 views8 reactionsread 9 August 2026

отмена

custom 52873662361648754096🍓1💘1

Signed 𐙚°.𝒎𝒊𝒕𝒔𝒖𝒌𝒐˚⋆

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

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.

Mentions

Named by 5 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.

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

“•。˚𝑴𝒊𝒕𝒔𝒖𝒌𝒐!!𐙚” (@mitsukchu), 120 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/mitsukchu.

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.