Telegram RegisterThe public register of Telegram

Channel

mio

@miotaya

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

219subscribers

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

Register entry

Telegram ID-1001975497483
TypeChannel
Username@miotaya
Descriptionvsp тт : d1noonx приват : https://t.me/+WnSZ4NFV6DMxZGMy анон : t.me/anonaskbot?start=55Pv7TOLKeE5v2w
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held1
On Telegramt.me/miotaya

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:17219first reading

Engagement

19 posts held, back to 28 December 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 19 posts for this entry, the most recent from 23 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
249
Videos
481
Links
28

Lifetime counters from Telegram’s own channel header, read 12 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
3m 17s
Average length
14s

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

318 reactions across 18 posts, in 15 distinct kinds. The most used accounts for 14.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥4614.5%
🍓3711.6%
custom 53057151610871107793410.7%
3310.4%
custom 5359682434478666852309.43%
custom 5247149334931209142237.23%
🕊216.60%
🥰216.60%
custom 5224384891570914624154.72%
custom 5395816900578016962134.09%
💘123.77%
custom 5370850375945451575113.46%
custom 5233549402592802076103.14%
custom 523334599723663222892.83%
💔30.943%

Custom emoji. 8 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 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 18 of the 19 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 318reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 28 December 2025 to 23 February 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @miotaya. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 28 December 2025 to 23 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

23 Feb 2026, 09:34 UTC383 views18 reactionsread 12 August 2026
Video

🤩

custom 535968243447866685214🥰2custom 53708503759454515752

Signed тая

14 Feb 2026, 09:28 UTC468 views32 reactionsread 12 August 2026
Video

Video, posted without a caption

🕊15custom 53708503759454515759🥰6🍓1custom 53596824344786668521

Signed тая

31 Jan 2026, 09:56 UTC352 views28 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 5359682434478666852157custom 52333459972366322286

Signed тая

24 Jan 2026, 14:57 UTC472 views33 reactionsread 12 August 2026
Video

Video, posted without a caption

❤‍🔥12custom 5233549402592802076105custom 52333459972366322283🕊2🍓1

Signed тая

13 Jan 2026, 19:57 UTC197 views2 reactionsread 12 August 2026
Forwarded from @asfalt222Photo

asf

🍓2

Signed тая

8 Jan 2026, 13:17 UTC195 views3 reactionsread 12 August 2026
Forwarded from @pard1xVideo

🤍🔠🔠🔠🔠✖️🔠🔠🔠🔠🤍 ˙ ₊ 🌟. — baby, how you doing? 🌟🌟 — i know you not doing the best but I'm here, I'll always be her🌟

❤‍🔥3

Signed тая

7 Jan 2026, 17:04 UTC324 views24 reactionsread 12 August 2026
Video

Video, posted without a caption

🥰8custom 52471493349312091426❤‍🔥4🍓32💘1

Signed тая

6 Jan 2026, 11:21 UTC192 views29 reactionsread 12 August 2026
Video

Video, posted without a caption

❤‍🔥9custom 53057151610871107799custom 52471493349312091426🥰21🍓1🕊1

Signed тая

4 Jan 2026, 13:53 UTC173 views8 reactionsread 12 August 2026
Forwarded from @INFANTILISMFAMPhoto

шортоми сторис и пост

🍓4custom 53057151610871107794

Signed тая

4 Jan 2026, 11:02 UTC161 viewsread 12 August 2026

лан я не люблю свои эдиты с 24 года😞

Signed тая

4 Jan 2026, 10:59 UTC235 views21 reactionsread 12 August 2026
Video

тоже не выкладывала

💘9custom 52471493349312091424custom 530571516108711077941🍓1🕊1🥰1

Signed тая

4 Jan 2026, 09:41 UTC138 views19 reactionsread 12 August 2026
Video

scp madevix

custom 53057151610871107798custom 52471493349312091426🍓31🥰1

Signed тая

Showing the 12 most recent of 19 posts we hold for @miotaya. 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 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“mio” (@miotaya), 219 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/miotaya.

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.