Telegram RegisterThe public register of Telegram
Telegram profile photo for MIKA

Channel

MIKA

@mika14881

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

79subscribers

+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-1002294196301
TypeChannel
Username@mika14881
DescriptionКосплееры из набережных Челнов (⁠≧⁠▽⁠≦⁠) Анон: https://t.me/letsqbot?start=rrmdi
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/mika14881

Growth

798 Aug 2026, 09:31 — 79 subscribers9 Aug 2026, 19:32 — 79 subscribers8 Aug 2026, 09:319 Aug 2026, 19:32
2 measurements spanning 1 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 78–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 19:3279no change
8 Aug 2026, 09:3179first reading

Engagement

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

What this channel posts

Photos
323
Videos
51
Links
25

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
45s
Average length
15s

Measured directly from 3 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

146 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 18.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54721863325434878652718.5%
custom 53035065471695902731812.3%
custom 53278976535586738591611.0%
custom 5247120580125165853149.59%
custom 5235471074040237203117.53%
custom 5235915667579880290117.53%
custom 5253672874857757824117.53%
custom 523570650267257102196.16%
custom 525365593550674341485.48%
custom 535289687148229945885.48%
custom 544764381137735298074.79%
custom 523551980473917667532.05%
custom 525395830549934793821.37%
custom 524695235914108627510.685%

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 areTelegram’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 8 of the 8 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 146reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 20 May 2026 to 27 June 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

27 Jun 2026, 17:49 UTC68 views15 reactionsread 9 August 2026
Photo

Очень мало фоток с микуворлд. Сори. Жалко мидзуки с видео - ❤️ Не жалко - 😐

custom 52357065026725710219custom 52355198047391766753custom 54721863325434878653

25 Jun 2026, 08:26 UTC80 views18 reactionsread 9 August 2026
Photo

🖤🖤🖤🖤🖤 Будем на микуворлд в Мизуки и закосе на Кураму 🪦 По немногу оживаем 😥

custom 53528968714822994587custom 54476438113773529805custom 54721863325434878655custom 53035065471695902731

31 May 2026, 21:06 UTC121 views14 reactionsread 9 August 2026
Photo

УРА ЛЕТО. Ещё скоро экзамены, так что мы возьмём рест на неопределённый срок 😊

custom 54721863325434878658custom 53035065471695902736

29 May 2026, 08:39 UTC102 views2 reactionsread 9 August 2026
Forwarded from @aruuka_LolPhoto

𝗖𝗼𝘀𝗽𝗹𝗮𝘆 :: . . . ⏤ [ 𝙵𝚛𝚎𝚒 ] ¡¡ ⃝📓⊹ . Ходячим мертвецом я прибываю уже долгое время, лишь ты поддерживала во мне жизнь не могу я покинуть тебя и никогда не покину. ٭𝚌𝚘𝚜𝚙𝚕𝚊𝚢 𝚋𝚢 𝙰𝚛𝚞𝚞𝚔𝚊 𖤐⭒๋࣭ ⭑ #косплейфрей #косплей #косплейпост рт/рк?

custom 53035065471695902732

27 May 2026, 15:00 UTC130 views30 reactionsread 9 August 2026
Photo

🌸🌸🌸🌸 🌸🌸🌸🌸🔠🔡🔠🔡🔠🔡🔡 🌸🌸🌸🌸🪦🌟🌟🪦🌟🌟🪦 🌸🌸🌸🌸 Unrivaled in the past, incomparable in the present... #Rohyww #Jingliu

custom 525367287485775782411custom 52536559355067434148custom 53278976535586738598custom 52539583054993479381custom 53528968714822994581custom 54476438113773529801

27 May 2026, 12:34 UTC91 views1 reactionsread 9 August 2026

Давайте ещё немного реакций 🌸

custom 52539583054993479381

23 May 2026, 19:22 UTC110 views41 reactionsread 9 August 2026
Photo

🤩🤩🤩 ⬜⬜🕷🕷🕷🕷🕷🕷 💙💙💙💙💙💙💙💙💙💙 Onna no ko hajimemashita Tameiki wa vioron no shirabe ni nite Akai mi hajikechatta

custom 524712058012516585314custom 523547107404023720311custom 523591566757988029011custom 54721863325434878652custom 52469523591410862751custom 53035065471695902731custom 54476438113773529801

20 May 2026, 17:42 UTC129 views25 reactionsread 9 August 2026
Photo

🌟🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟 💕💕💕💕💕 🌟🌟🌟🌟

custom 54721863325434878659custom 53035065471695902738custom 53278976535586738598

Showing the 8 most recent of 8 posts we hold for @mika14881. 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 — 806,885 of 1,481,217entries 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

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 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

“MIKA” (@mika14881), 79 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/mika14881.

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.