Channel
@mugmodd
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
164subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001520286224 |
|---|---|
| Type | Channel |
| Username | @mugmodd |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 4 September 2026 |
| On Telegram | t.me/mugmodd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 01:28 | 164 | +1 |
| 8 Aug 2026, 16:45 | 163 | no change |
| 7 Aug 2026, 16:51 | 163 | first reading |
11 posts held, back to 25 May 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 11 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
149 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5416079375164528616 | 57 | 38.3% | |
| custom 5424972470023104089 | 40 | 26.8% | |
| custom 5298535122524459955 | 23 | 15.4% | |
| custom 5341498088408234504 | 18 | 12.1% | |
| custom 5458738403392633936 | 5 | 3.36% | |
| custom 5206447385860912373 | 3 | 2.01% | |
| custom 5233600671617408774 | 3 | 2.01% |
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 11 of the 11 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 149 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 25 May 2026 to 24 July 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.
Привет Я пока в жестком ворке, но в планах начать выкладывать контент за эти ТРИ, Три месяца, Карл Контента много, я один, поэтому накидайте реакций, если ждёте и уже завтра стартуем марафон постов 💪🏻
custom 542497247002310408918custom 529853512252445995511custom 54587384033926339365custom 52064473858609123732
Входим в летний прайм 📸 Надо вашу активность в инсте. Первый рилс как-никак https://www.instagram.com/reel/DaH-ANyNJx8/?igsh=ZTFjcjRtMndvaXJm
custom 541607937516452861613custom 52985351225244599556
Video message, posted without a caption
custom 54160793751645286166custom 54249724700231040892
Video message, posted without a caption
custom 54160793751645286166
Первый мой командный проект съёмки и монтажа клипа. Время ушло на него много, для первого вводного мне нравится че получилось Оцениваем реакциями на этом посте https://youtu.be/5bRYRamIf5U
custom 54160793751645286168custom 53414980884082345045custom 52985351225244599554custom 52336006716174087741
UZI FLAME - Мечта (Official Music Video) 🕊 Смотреть на YouTube 🔥 DIRECTED BY: UZI FLAME DOP BY: KELLY KREIN + Mugmod Cлушать везде 🔉 SHADOW GANG 2026 🐍
custom 54160793751645286164custom 52336006716174087742custom 52985351225244599552custom 53414980884082345041
UZI FLAME - Мечта 🕊️ prod by vanetty & tsukuyomi mix & master by nion & colrain cover by vönted distribution WAM Cлушать
custom 54160793751645286164custom 54249724700231040892custom 52064473858609123731
Мечта, которую мы снимали с марта и монтажили по май, уже в этом месяце @prettyflamee
custom 541607937516452861611
Video message, posted without a caption
custom 54249724700231040896
Video message, posted without a caption
custom 54249724700231040898
В отпуске 🥂🌠⛳️
custom 534149808840823450412custom 54160793751645286165custom 54249724700231040894
Showing the 11 most recent of 11 posts we hold for @mugmodd. 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.
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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Mugmod” (@mugmodd), 164 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/mugmodd.
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.