Channel
@mixmen1
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
79subscribers
+36 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003917259734 |
|---|---|
| Type | Channel |
| Username | @mixmen1 |
| Created | Between 1 April 2026 and 5 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/mixmen1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 07:20 | 79 | -3 |
| 3 Sept 2026, 17:18 | 82 | -4 |
| 27 Aug 2026, 10:46 | 86 | +19 |
| 20 Aug 2026, 10:15 | 67 | +24 |
| 19 Aug 2026, 19:30 | 43 | first reading |
16 posts held, back to 5 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 16 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
173 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 24.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5370713808870318222 | 43 | 24.9% | |
| custom 5370716660728601467 | 42 | 24.3% | |
| custom 5370997525819956741 | 34 | 19.7% | |
| custom 5370972181217943252 | 28 | 16.2% | |
| custom 5371027573411159825 | 26 | 15.0% |
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 16 of the 16 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 173 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 5 June 2026 to 19 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.
кароче прикол, вчера проебывал деньги в казике, а сегодня меня попросили выйти на подмену, с челом который сразу начал лудить в машине (по дороге на роботу) и прикол то что я попал на склад, где переносил ящики с пивом, с моего родного города🌆
custom 53707166607286014674custom 53710275734111598253custom 53709975258199567412
10 челам после стрима, кто скинет скрин, что были на стриме, получат по подарку, а ласт 2-3 чела, кто останется до конца, смогут получить нфт https://www.twitch.tv/mixmen4ik
custom 53707166607286014674custom 53710275734111598254custom 53707138088703182223
fog🌫️
custom 53707166607286014677custom 53709975258199567415custom 53710275734111598254
Запустил стрим,( гуляем в сша ) 5 чел кто скинет скрин под постом, отправим мишек, + самому активному на стриме скинем нфт https://www.twitch.tv/mixmen4ik
custom 53709975258199567413custom 53707138088703182222custom 53710275734111598252
я в столице нью-йорка
custom 53707138088703182227custom 53709721812179432523custom 53709975258199567413
Video message, posted without a caption
custom 53707138088703182226custom 53707166607286014674custom 53709721812179432523custom 53710275734111598252
https://www.twitch.tv/mixmen4ik ирл с бостона
custom 53707138088703182223custom 53709721812179432523
стрим начался, на рандом выберем 5 людей которые скинут скрин со стрима, https://www.twitch.tv/mixmen4ik
custom 53707166607286014675
https://www.twitch.tv/mixmen4ik перезапуск
custom 53707138088703182225custom 53707166607286014673custom 53709721812179432523
Подписчик залутал сразу 2 NFT! 🎉 ✅Первое — за создание концептов будущих скинов на NFT - их можно увидеть на первом фото)) ⚔️Второе — за победу в PvP-турнире. Участников было не так много, поэтому шанс был у каждого!!! Поздравляем с двойной победой! 🔥🫴
custom 53707138088703182226custom 53709721812179432523custom 53709975258199567413
первый подписчик получает нфт, за эти прекрасные постройки
custom 53709721812179432524custom 53709975258199567411
https://www.twitch.tv/mixmen4ik запустил, играем с подписчиками
custom 53707166607286014673
Showing the 12 most recent of 16 posts we hold for @mixmen1. 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“MIXMEN” (@mixmen1), 79 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/mixmen1.
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.