~ 🥊 :: " 𝗣𝗥𝗢𝗙𝗜𝗟𝗘 Ñ•9 " 🫦 🅰️𝗜𝗔𝗦𝗛 (( 📍 )) #GROUP :: // @🎁 𝗩𝗥𝗢𝗢𝗠 𝗩𝗥𝗢𝗢𝗠 👍 <⭐> 𝗣𝗥𝗢𝗧Ø𝗧𝗬𝗣𝗘 :: 𝗞 "❣️" 𝟮𝟴.𝟬𝟭.𝟬𝟳 &., 1️⃣9️⃣ 𝗘𝗡𝗧𝗣 @Kaze_oi ➿➿ ➿➿ #MIASH #PROFILE
custom 54632507089187110445custom 53350047936413877163custom 52264397284793579352

Channel
@miash_m
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
28subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003424213147 |
|---|---|
| Type | Channel |
| Username | @miash_m |
| Description | @miash_anonbot — анон!! Пишите по любым вопросам🫶🏻 |
| Created | Between 1 November 2025 and 3 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/miash_m |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 06:17 | 28 | no change |
| 7 Aug 2026, 18:48 | 28 | first reading |
19 posts held, back to 3 March 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 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 8 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 1 video 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.
225 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 22.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463250708918711044 | 50 | 22.2% | |
| custom 5458800216561967331 | 39 | 17.3% | |
| custom 5335004793641387716 | 35 | 15.6% | |
| custom 5318785764476071327 | 34 | 15.1% | |
| custom 5271477799222287655 | 33 | 14.7% | |
| custom 5283225148957141988 | 25 | 11.1% | |
| custom 5418230384980681655 | 5 | 2.22% | |
| custom 5226439728479357935 | 4 | 1.78% |
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 13 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 225reactions 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 3 March 2026 to 8 April 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.
~ 🥊 :: " 𝗣𝗥𝗢𝗙𝗜𝗟𝗘 Ñ•9 " 🫦 🅰️𝗜𝗔𝗦𝗛 (( 📍 )) #GROUP :: // @🎁 𝗩𝗥𝗢𝗢𝗠 𝗩𝗥𝗢𝗢𝗠 👍 <⭐> 𝗣𝗥𝗢𝗧Ø𝗧𝗬𝗣𝗘 :: 𝗞 "❣️" 𝟮𝟴.𝟬𝟭.𝟬𝟳 &., 1️⃣9️⃣ 𝗘𝗡𝗧𝗣 @Kaze_oi ➿➿ ➿➿ #MIASH #PROFILE
custom 54632507089187110445custom 53350047936413877163custom 52264397284793579352
всем привет ребятаааа у меня в последнее время большие проблемы с интернетом, потому буду активить по возможности💔💔 групп это тоже касается, но я стараюсь забегать иногда эхэх а пока я готовлю контент, можете подписаться на мой лайв тгк!!
custom 54182303849806816555
Можно я закину сюда липсинг под эксджи, а вы скажете, что я их главная фанатка
custom 53350047936413877168custom 54588002165619673315custom 54632507089187110445custom 52714777992222876553custom 52264397284793579352
File, posted without a caption
custom 54588002165619673314custom 53187857644760713273custom 52714777992222876552
·. 🥹🎀 WჩαեsY𝕠υ𝗿Alibi🎀 ׄ 🤍. ׄ* 🎀. #ℕe𝘄𝕄𝗲mb𝗲r - 𐌑IA𐍃𐋏 🎀.· ·🤍·➿ ·➿🥹 ⟡ 🥹➿· ➿·🤍· 🥹 Trᥙᥱ 🤩ᥲᥒ уᴦᴀдᴀй, цᴇᴧьᴄя, ᴄᴛᴩᴇᴧяй ·🤍·➿ ·➿🥹 ⟡ 🥹➿· ➿·🤍· :🥹🥹 ✦ . ׄ @criminaloi🎀· . * 🔤α𝗱 . ☠️T𝗿υeAեeez ☠️. ׄ ֶָ֢·
custom 52832251489571419885custom 54632507089187110443custom 52714777992222876552
Sticker, posted without a caption
⌗ . 🫀Profꪱle 002 / D⃨ꪱ𝕝α𝕣α🤲🏻ׄ . 🎀💼 @miash_m ⬫ . 🤩🎀 ׄ . ᥒ𑄜t shყ ᥒꭤt ოe
custom 54632507089187110445custom 53187857644760713273custom 53350047936413877163
. ·. 🥹🎀 WჩαեsY𝕠υ𝗿Alibi🎀 ׄ 🤍. ׄ* 🎀. #𝗡𝕖𝕨𝗣𝕠st🎀.· ·🤍·➿ ·➿🥹 ⟡ 🥹➿· ➿·🤍· Рᥱᥰ᧐ᥴᴛ, ᥱᥴ᧘ᥙ ᧘юδᥙɯь κρᥙⲙᥙнᥲ᧘! ·🤍·➿ ·➿🥹 ⟡ 🥹➿· ➿·🤍· :🥹🥹 ✦ . ׄ @criminaloi🎀· . * 🔤α𝗱 . ☠️T𝗿υeAեeez ☠️. ׄ ֶָ֢·
custom 54632507089187110446custom 52832251489571419885custom 53187857644760713274
🥹🥹🎀 ⲙsɦ の ⲥσνⲉʀ ❤️ 🤩 𝖡𝖠𝖡𝖸𝖬𝖮𝖭 — 𝖫𝗈𝗏𝖾, 𝖬𝖺𝗒𝖻𝖾 🎀🎀 🥹 ➿ - ➿🥹➿ - ➿ 🤩 ‧˚꒰❤️꒱ @miash_m 🥹₊˚❤️⋆
custom 52714777992222876557custom 53187857644760713276custom 54632507089187110446custom 53350047936413877162
Sticker, posted without a caption
подала!
custom 54588002165619673314custom 53350047936413877163custom 54632507089187110442
🥹🥹🎀 ⲙsɦ の ⲥσνⲉʀ ❤️ 🤩 𝖷𝖦 — 𝖳𝖠𝖪𝖤 𝖬𝖸 𝖡𝖱𝖤𝖠𝖳𝖧 🎀🎀 🥹 ➿ - ➿🥹➿ - ➿ 🤩 ‧˚꒰❤️꒱ @miash_m 🥹₊˚❤️⋆
custom 531878576447607132710custom 545880021656196733110custom 546325070891871104410custom 52714777992222876556
Showing the 12 most recent of 19 posts we hold for @miash_m. 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 — 1,123,550 of 1,189,255entries 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.
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.
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.
@miash_m named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“♯miash” (@miash_m), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/miash_m.
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.