⚽️ Спасибо за щедрый июльский урожай! ⚽️ Друзья, вы невероятные! Общими усилиями мы собрали целых 🎟 1633 июльских купонов! Не дайте урожаю пропасть - забирайте скорее 👉 ЗДЕСЬ.
👍12🔥1

Channel
@MinigameHub
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,303subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003636006650 |
|---|---|
| Type | Channel |
| Username | @MinigameHub |
| Created | Between 1 December 2025 and 28 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/MinigameHub |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 2 other registered channels. They sit inside a group of 5 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @MinigameHub/47 · this entry10 Jun 2026, 13:01 UTC | @GameHall_new/7410 Jun 2026, 13:01 UTC | 1.00 | under a minute |
| @MinigameHub/48 · this entry15 Jul 2026, 15:01 UTC | @GameHall_new/7915 Jul 2026, 15:01 UTC | 1.00 | under a minute |
| @MinigameHub/49 · this entry18 Jul 2026, 11:01 UTC | @GameHall_new/8118 Jul 2026, 11:01 UTC | 1.00 | under a minute |
| @MinigameHub/50 · this entry20 Jul 2026, 15:01 UTC | @GameHall_new/8220 Jul 2026, 15:01 UTC | 1.00 | under a minute |
| @MinigameHub/51 · this entry4 Aug 2026, 12:01 UTC | @GameHall_new/874 Aug 2026, 12:01 UTC | 1.00 | under a minute |
| @MinigameHub/52 · this entry5 Aug 2026, 12:01 UTC | @GameHall_new/895 Aug 2026, 12:01 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @GameHall_new | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | @GameHall_new (7–0) |
| @GGWRUS | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 7 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 3 May 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 5, the earliest publisher we hold is @MinigameHub — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:18 | 2,303 | -3 |
| 8 Aug 2026, 07:20 | 2,306 | +1 |
| 7 Aug 2026, 14:03 | 2,305 | no change |
| 7 Aug 2026, 13:01 | 2,305 | first reading |
20 posts held, back to 28 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (28 April 2026 – 6 August 2026) |
| Views total | 9,029 |
| Reactions total | 389 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 14:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
2,576 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,393 | 92.9% | |
| 🔥 | 130 | 5.05% | |
| 😭 | 16 | 0.621% | |
| 👍 | 15 | 0.582% | |
| 🥰 | 13 | 0.505% | |
| 👎 | 9 | 0.349% |
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 18 of the 20 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 2,576reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 28 April 2026 to 6 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.
⚽️ Спасибо за щедрый июльский урожай! ⚽️ Друзья, вы невероятные! Общими усилиями мы собрали целых 🎟 1633 июльских купонов! Не дайте урожаю пропасть - забирайте скорее 👉 ЗДЕСЬ.
👍12🔥1
🐸 Халявная среда - лови свою порцию подарков! 🐸 Каждую среду мы раздаём купоны просто так - потому что среда должна быть лёгкой! 🐸 Что делать? Дождись купон в нашем чате в Telegram. 🐸 Количество ограничено, поэтому правило простое: успел - твой! Долго думать некогда - халява ждать не будет.
❤29🔥5👎1
⭐️ Ловите «Звездопад купонов»! ⭐️ В этом августе мы запускаем акцию, где все зависит только от вас, наше любимое комьюнити! Чем нас больше - тем круче подарки. Мы объединяемся с тысячами геймеров, чтобы вскрыть секретные призовые фонды для ваших любимых игр. Готовьтесь к охоте за бонусами! Ваш квест на этот месяц: 🔠 Подпишитесь на сообщества, которые вам интересны на странице акции. 🔠 Следите за ростом участников…
🔥52❤1
🔥 Июльский зной - купоны в огне! 🔥 🌞 Чувствуете этот жар? Наши купоны AppGallery раскалились добела под июльским цифровым солнцем, и каждая ваша реакция ❤️ - приближает к подаркам! Как остудить зной сияющими призами? 💨 Подпишитесь на наши Telegram-каналы и ставьте реакцию на этот пост ❤️: ☀ Game Hall: RPG, Strategy, Sim games ☀ Game Hall: Action games ☀ Game Hall: New Releases ☀ MiniGame Hub ☀ Standoff 2 - Ga…
❤257🔥3
🆕🆕🆕🆕 Две новые игры уже доступны в GameCenter! Разные настроения - одно удовольствие от игры! 💐 Уютная флористика 💐 Спокойный симулятор цветочного магазина для отдыха души. Выращивайте сотни сортов цветов, составляйте авторские букеты, обустраивайте сад и магазин по своему вкусу. Без спешки и стресса - мягкая музыка, тёплые истории жителей городка и творчество без ограничений. Идеально для тихих вечеров, когда хоче…
🔥6❤2
🌺Спасибо за щедрый июньский урожай!🌺 Друзья, вы невероятные! Общими усилиями мы посадили и вырастили целых 🎟 2677 купонов! Не дайте урожаю пропасть - забирайте скорее 👉ЗДЕСЬ.
🔥14❤4👎2
🤩 Напоминание о щедром июньском урожае купонов! 🤩 Друзья, майские купоны уже вовсю распускаются! Если вы ещё не с нами - скорее включайтесь: 🤩 Подпишитесь на наши Telegram-каналы. 🤩 Поставьте реакцию ❤️ под 👉 этим постом 👈! Чем больше сердечек, тем больше купонов мы раздадим. Считаются только ❤️! 🤩 Не тяните до последнего - время идёт. Пусть ваш «купоный урожай» будет самым щедрым! 🤩 Подробности на странице акци
❤331
☀️ Солнечный июнь - купоны засияли! ☀️ ☀️ Знаете, почему наши купоны AppGallery такие яркие и горячие? Они впитали в себя лучи цифрового летнего солнца, и каждая реакция ❤️ - как солнечный зайчик, делающий подарки ещё щедрее! Самое время поймать свой купонный свет! Как наполнить лето сияющими сюрпризами? ☀️ Подпишитесь на наши Telegram-каналы и ставьте реакцию на этот пост ❤️: ☀️ Game Hall: RPG, Strategy, Sim g…
❤444🔥2
🌺 Спасибо за щедрый майский урожай! 🌺 Друзья, вы невероятные! Общими усилиями мы посадили и вырастили целых 🎟 5230 купонов! Не дайте урожаю пропасть - забирайте скорее 👉 ЗДЕСЬ. 🌞 Ваша коллективная забота дала такие щедрые всходы - гордитесь собой, это только начало большого плодородного сезона!
❤41👍3👎1🔥1
🌸 Напоминание о майском урожае купонов! 🌸 Друзья, майские купоны уже вовсю распускаются! Если вы ещё не с нами - скорее включайтесь: ✅ Подпишитесь на наши Telegram-каналы. ✅ Поставьте реакцию ❤️ под 👉 этим постом 👈! Чем больше сердечек, тем больше купонов мы раздадим. Считаются только ❤️! ⭐️ Не тяните до последнего - времени осталось немного. Пусть ваш «купоный урожай» будет самым щедрым! ☀️ Подробности на стран…
❤217
❤️ 2000 человек - это уже не просто канал, а целая армия игроков! Спасибо, что вы с нами. ❤️ Держите 🎟 купон на 100₽ в любимую игру. Просто так, за то, что мы стали больше. ❔ Как получить? 1. Хватай купон 👉 ЗДЕСЬ. 2. Заходи в игру трать с удовольствием! Успей, пока не разобрали! ⭐️ Mini Games Везде: 💬 Telegram-канал 💙 Сообщество ВКонтакте 💬 Telegram чат
❤16😭16🥰13👎4
🌸 Напоминание о майском урожае купонов! 🌸 Друзья, майские купоны уже вовсю распускаются! Если вы ещё не с нами - скорее включайтесь: ✅ Подпишитесь на наши Telegram-каналы. ✅ Поставьте реакцию ❤️ под 👉 этим постом 👈! Чем больше сердечек, тем больше купонов мы раздадим. Считаются только ❤️! ⭐️ Не тяните до последнего - время идёт. Пусть ваш «купоный урожай» будет самым щедрым! ☀️ Подробности на странице акции.
❤220
Showing the 12 most recent of 20 posts we hold for @MinigameHub. 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 — 131,964 of 1,183,361entries 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.
Named by 6 registered channels — 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“MiniGame Hub” (@MinigameHub), 2,303 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/MinigameHub.
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.