Channel
@miericosplayy
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
97subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004439904412 |
|---|---|
| Type | Channel |
| Username | @miericosplayy |
| Created | Between 1 June 2026 and 21 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/miericosplayy |
@miericosplayy was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 13:16 | 97 | -2 |
| 15 Aug 2026, 20:07 | 99 | +2 |
| 9 Aug 2026, 12:02 | 97 | no change |
| 8 Aug 2026, 18:01 | 97 | first reading |
20 posts held, back to 21 July 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
136 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 12.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5188294019389624686 | 17 | 12.5% | |
| custom 5328043587957444980 | 17 | 12.5% | |
| custom 5325518881626805268 | 16 | 11.8% | |
| custom 5319274716437960293 | 15 | 11.0% | |
| custom 5278295123501803529 | 12 | 8.82% | |
| custom 5328200856774922090 | 12 | 8.82% | |
| custom 5348167816136646680 | 11 | 8.09% | |
| custom 5276332589735502438 | 10 | 7.35% | |
| custom 5319011512252126372 | 9 | 6.62% | |
| custom 5195151905340280995 | 8 | 5.88% | |
| custom 5220046725493828505 | 5 | 3.68% | |
| custom 5222108309795908493 | 2 | 1.47% | |
| custom 5345928768080868550 | 2 | 1.47% |
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 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 14 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 136 reactions 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 21 July 2026 to 5 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.
🌟🌟🌟🌟🌟🌟🌟🌟 ———🤍 🤩🔤nternet 🔤ngel...🤩 🌟🌄🌄🌄🌄🌄🤩🤩 🪽🔤nternet 🔤amero ! 🪽 ——— kaangel🤩
custom 518829401938962468611custom 51951519053402809957custom 53190115122521263726custom 53192747164379602932custom 53255188816268052682custom 52200467254938285051
Video message, posted without a caption
custom 52200467254938285053custom 53192747164379602933custom 53255188816268052683
💔 • Все еще сидим на кико !!
custom 53192747164379602937custom 51882940193896246861
На кико ! 💔
custom 51882940193896246863custom 53192747164379602932
🌟 … 🔤нонс ! 𓆩 ۪ ׄ⏜𓏸⃘⌣. 🌩🌩🌩🌩 —🤩🤩 」: уже завтра буду на кико в дарк кангел вместе со своей кангел !! 🤩 ————————— • #анонс
custom 53255188816268052685custom 53190115122521263723custom 51882940193896246862custom 51951519053402809951custom 52200467254938285051custom 53192747164379602931
✨ На кице !!
custom 53282008567749220907custom 53255188816268052684custom 53280435879574449802custom 53481678161366466801
`✦ ˑ ִֶ 𓂃⊹ⲙᥲᦔ𐔖h𐔖ⲙᥙ ೀ 🌟🌟🌟🌟🌟🌟🌟🌟 「🎀🎀」— 🤩𐔖ⲙᥙrᥲ-ᥴhᥲᥒ, ᥕh𐔤 ᥲrᥱ 𐔤𐔖ᥙ ᥲᥣᥕᥲ𐔤᥉ ᥉𐔖 ᦔι᥉tᥲᥒt? — 🤩ᥲ𐔤bᥱ ιt'᥉ bᥱᥴᥲᥙ᥉ᥱ ι'ⲙ ᥒ𐔖t hᥙⲙᥲᥒ ᥲᥒ𐔤ⲙ𐔖rᥱ ⋆.ೃ࿔*:･⋆˚𝜗𝜚˚⋆ ...ρⲧ 🌟🌟🌟🌟🌟🌟🌟
custom 52763325897355024385custom 53282008567749220903custom 53280435879574449802
Video, posted without a caption
custom 53280435879574449803
🌌🌌🌌🌌🌌🌌 🤩🤍🔤🔤🔤🔤🔤 𓆩 ۪ ׄ⏜𓏸⃘⌣۪🌩🌩🌩🌩🌩🌩 ☂️ ・ 🔤тот мир не стоит того, чтобы его спасать, его трагедии и печали никогда по-настоящему не исчезнут。 🌩🌩🌩🌩🌩🌩⏜ׄ۫𓏸⃘⌣۪ 𓆪 ph — рт, реакции??
custom 527829512350180352911custom 532804358795744498010custom 534816781613664668010custom 52763325897355024384custom 53255188816268052682custom 53282008567749220902
ошень люблю розочку манго в фд технолайка🤯 на счет косплееров не знаю, всех люблю
custom 52763325897355024381custom 52782951235018035291
💬 У тебя новое анонимное сообщение! Есть любимый эдитор/косплеер в любом фд? Если да то кто?(ㆁωㆁ) ⬅️ Свайпни для ответа.
буду на кице оба дня в новом косплейчике🌟 возможно во второй день буду в дарк кангел, ноо компании еще нету…
Showing the 12 most recent of 20 posts we hold for @miericosplayy. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“「🔮— 𐌺᧐ⲙ᧐ρκᥲ 𐌑ᥙëρᥙ 」” (@miericosplayy), 97 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/miericosplayy.
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.