Channel
@mstrd
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002203137746 |
|---|---|
| Type | Channel |
| Username | @mstrd |
| Description | Homophobic dni! new art galery @vangaft |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mstrd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 02:16 | 2 | no change |
| 7 Aug 2026, 19:07 | 2 | first reading |
15 posts held, back to 4 October 2025 — 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 15 posts for this entry, the most recent from 26 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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 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.
120 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 30 | 25.0% | |
| custom 6192527608794583180 | 19 | 15.8% | |
| custom 6318735952931984579 | 16 | 13.3% | |
| custom 6077731327770101602 | 12 | 10.0% | |
| 💯 | 11 | 9.17% | |
| 🤮 | 8 | 6.67% | |
| 😭 | 7 | 5.83% | |
| custom 6111447160346118586 | 3 | 2.50% | |
| custom 6120584007483656243 | 3 | 2.50% | |
| ❤ | 3 | 2.50% | |
| custom 6274062056761068194 | 2 | 1.67% | |
| 👎 | 2 | 1.67% | |
| custom 6075365930366404710 | 1 | 0.833% | |
| custom 6320996523068889461 | 1 | 0.833% | |
| 👏 | 1 | 0.833% | |
| 😁 | 1 | 0.833% |
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 9 of the 15 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 120reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 4 October 2025 to 26 May 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.
my wife gua waifu gadis gua kalau gua adalah futaro gua akan straight forward melamar wanita stundere kawai kirei my waifu watashi nino nakano🥰😍😘❤❤🔥 #waifuwatashi #ninonakano #animeh
🤮2
Sticker, posted without a caption
Jumint : "pas kecil kamu pernah nelen magnet ya? June: nggak kenapa emang nya? Jumint: soalnya menarik banget dimata ku
👎1
Sticker, posted without a caption
*moment ketika ngeprenk kedua istri pake lagu dangdut 🤭🤭 jumint:/bernyanyiSambilberdendang senang nya dalam hati ber istri dua Larent (istri tua) : /ngambek June (istri muda): /ngambek Mint : untuk istri muda kakanda sayang bunda Larent : /saltink Mint : untuk istri kedua aku bilang i love u June : /senyum tipis
🤮6👎1😭1
cr : bang ael
❤1
File, posted without a caption
but i also want to be the person you call "sayang".
❤2
june : bbyyhhh..🥺🥺 mint: apa byhhh.. /suara ngebas rawr june : byhh boleh minta foto kamu ga? /Cute mint : buat apa byhh? /Senyum ganteng beut june : buat taruh di tukang galon🥺😎 xixi /ketawa gemas anak kucing Mint: bibiyhh mah!😡 /Marah kokuet
😭6👏1😁1
Fotbar terkeren, @Brainlrot ft. @IowIIy @Apocalypsir @edavane @opswise
📱
Sticker, posted without a caption
Showing the 12 most recent of 15 posts we hold for @mstrd. 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,231,782 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“anomali chen💥” (@mstrd), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mstrd.
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.