Sticker, posted without a caption

Channel
殒命 ᥫ᭡ YNM
@ynmfml
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
130subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003990719900 |
|---|---|
| Type | Channel |
| Username | @ynmfml |
| Created | 16 April 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/ynmfml |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 15:08 | 130 | +2 |
| 2 Oct 2026, 15:01 | 128 | +25 |
| 18 Sept 2026, 17:59 | 103 | +34 |
| 10 Sept 2026, 02:58 | 69 | -4 |
| 31 Aug 2026, 00:26 | 73 | -10 |
| 24 Aug 2026, 05:25 | 83 | -12 |
| 16 Aug 2026, 14:56 | 95 | -23 |
| 9 Aug 2026, 04:47 | 118 | no change |
| 8 Aug 2026, 09:16 | 118 | +4 |
| 7 Aug 2026, 19:30 | 114 | first reading |
Engagement
9 posts held, back to 16 April 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 9 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
295 reactions across 3 posts, in 17 distinct kinds. The most used accounts for 22.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5413356456093195934 | 67 | 22.7% | |
| custom 5398093022791496852 | 51 | 17.3% | |
| custom 5395533170743473448 | 27 | 9.15% | |
| custom 5411313537718982618 | 26 | 8.81% | |
| custom 5395844263814657196 | 25 | 8.47% | |
| custom 5395690654309317794 | 18 | 6.10% | |
| custom 5397837884554246638 | 18 | 6.10% | |
| custom 5411346737816183754 | 18 | 6.10% | |
| custom 5395379067316895832 | 16 | 5.42% | |
| custom 5397945804197491505 | 14 | 4.75% | |
| custom 5395794158726182400 | 9 | 3.05% | |
| custom 5375338079898851371 | 1 | 0.339% | |
| custom 5397686559971505717 | 1 | 0.339% | |
| custom 5397834817947594948 | 1 | 0.339% | |
| custom 5803112080936542106 | 1 | 0.339% | |
| custom 5803320210756738018 | 1 | 0.339% | |
| custom 5803435002347660061 | 1 | 0.339% |
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 4 of the 9 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 295 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 16 April 2026 to 9 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.
Telegram Stars
- Stars received
- 200
- across the posts below
- Posts paid on
- 2
- of 8 we hold a reading for · 25%
- Most on one post
- 100
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ynmfml. 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 9 most recent posts we hold for this entry, published 16 April 2026 to 9 August 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
бырдене истикш
Sticker, posted without a caption
Открыты, кеттік
custom 53753380798988513711custom 53958442638146571961custom 53976865599715057171custom 53978348179475949481custom 58031120809365421061custom 58033202107567380181custom 58034350023476600611
Sticker, posted without a caption
🔠unming ✨🔠nm 🔠e can be a home for you 🔠nfo 💙🔠nitial 💙 🔠rchv 💙 🤩hop
custom 539809302279149685246custom 541335645609319593437custom 539553317074347344827custom 539569065430931779413custom 539783788455424663813custom 541131353771898261813custom 541134673781618375412custom 539537906731689583210
Sticker, posted without a caption
🤩🤩🤩🤩🤩🤩 🔤 сегодняшнего дня названия «YUNMING», «YNM» и «ЮНЬМИНЬ», «ЮНМ» принадлежат только нам. При их использовании (или схожих вариантов) другими пользователями мы попросим изменить название. data patent : 18.04.2026 если в любом случае мы закроемся, патент остается за нами 📌
custom 541335645609319593430custom 539584426381465719614custom 541131353771898261813custom 53957941587261824009custom 53953790673168958326custom 54113467378161837546custom 53956906543093177945custom 53978378845542466385
Channel created
Showing the 9 most recent of 9 posts we hold for @ynmfml. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“殒命 ᥫ᭡ YNM” (@ynmfml), 130 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/ynmfml.
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.