Channel
@xmlmfgl
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
46subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003913650620 |
|---|---|
| Type | Channel |
| Username | @xmlmfgl |
| Description | Без объяснения причин |
| Created | 8 June 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xmlmfgl |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:16 | 46 | no change |
| 7 Aug 2026, 10:47 | 46 | first reading |
11 posts held, back to 8 June 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
112 reactions across 7 posts, in 14 distinct kinds. The most used accounts for 19.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 22 | 19.6% | |
| 🦄 | 17 | 15.2% | |
| ❤ | 14 | 12.5% | |
| 👍 | 13 | 11.6% | |
| 🎉 | 8 | 7.14% | |
| 😭 | 8 | 7.14% | |
| 🆒 | 7 | 6.25% | |
| 😁 | 6 | 5.36% | |
| 👌 | 3 | 2.68% | |
| 💯 | 3 | 2.68% | |
| 😍 | 3 | 2.68% | |
| 😱 | 3 | 2.68% | |
| 🫡 | 3 | 2.68% | |
| ❤🔥 | 2 | 1.79% |
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 7 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 112 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 8 June 2026 to 4 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.
ку-ку, пока лето, август, новые даты тупрова не выбраны, а впереди в конце августа Питерский фестиваль, от нас есть вам предложение. вы уже посмотрели Одиссею? или собираетесь? если один из ответов - да, то точно появится желание ее с кем-то обсудить. рекомендуем сделать это сразу по hard level, вместе с кинокритиком Егором Москвитиным и комиками Лешей Сапром, Сашей Бурдашевым и нашей Оксаной Мафагел. 15 августа в …
❤4💯3😍3🦄2
ребятушки, все кто хотел прийти к нам на концерт, увы, придется отменить это мероприятие. в наше пространство вторглись обстоятельства, которые выше нас. будут новые даты! будет еще и Питер в конце августа
😭8👌3🫡3😱3🦄2
а мы напоминаем, что уже 27ого июля в 19.00 сможем с вами увидеться, подхихикать билеты - https://impro-shou.timepad.ru/event/4089817/
❤3🦄1
если вы только что сюда зашли, то знайте — примерно так здесь всё и будет. местами смешно. местами странно. иногда даже неожиданно трогательно. такой же микс, как и на наших выступлениях. в общем, располагайтесь! 🙌
🔥5🎉4😁3❤2🦄2
Video, posted without a caption
🔥7🎉4🦄4😁3❤🔥2
ХмельМафагел pinned a photo
как и обещали, ловите нашу афишу с выступлением! 27 июля в 19.00 в Comedy 34 сделаем вместе с вами импровизацию БИЛЕТЫ ПО ССЫЛКЕ - https://impro-shou.timepad.ru/event/4089817/ приходите, будет точно летнее хихикание!
👍6❤5🔥5🦄3
ХмельМафагел pinned «ку ку! мы тут поразмышляли и поняли, что все-таки нам нужен свой тг канал, чтоб выкладывать все наши анонсы шоу, какие-то активности и просто забавный контент. итак, знакомимся мы комедийный дуэт «Хмель и Мафагел». играем длинную форму импровизации (ее сходу…»
ку ку! мы тут поразмышляли и поняли, что все-таки нам нужен свой тг канал, чтоб выкладывать все наши анонсы шоу, какие-то активности и просто забавный контент. итак, знакомимся мы комедийный дуэт «Хмель и Мафагел». играем длинную форму импровизации (ее сходу непросто объяснить, проще увидеть наглядно). по сути это комедийный спектакль, но полностью придуманный на ходу (ну в целом не прям сложно оказалось объяснить)…
👍7🆒7🔥5🦄3
Photo, posted without a caption
Channel created
Showing the 11 most recent of 11 posts we hold for @xmlmfgl. 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“ХмельМафагел” (@xmlmfgl), 46 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/xmlmfgl.
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.