福利来公群编号2222/856/6699快三扫雷硬碰硬不抽水 刁哈哈扫雷 🔗:https://t.me/+U6hPQ2xY3LA3Mjlk 刁哈哈快三 🔗:https://t.me/+fmlj36JQV6tjMjBk 500流水包 300u 60包 (856公群刁哈哈快三)https://t.me/c/2612588424/622470
❤1
Signed 九州娱乐-飞鱼

Channel
@hahadashi92773
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,394subscribers
-27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002296104224 |
|---|---|
| Type | Channel |
| Username | @hahadashi92773 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/hahadashi92773 |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:41 | 1,394 | -16 |
| 14 Sept 2026, 18:37 | 1,410 | -13 |
| 11 Sept 2026, 12:56 | 1,423 | +1 |
| 27 Aug 2026, 15:45 | 1,422 | +2 |
| 24 Aug 2026, 07:04 | 1,420 | -1 |
| 20 Aug 2026, 19:59 | 1,421 | -1 |
| 11 Aug 2026, 06:08 | 1,422 | +1 |
| 7 Aug 2026, 22:03 | 1,421 | no change |
| 7 Aug 2026, 16:06 | 1,421 | first reading |
20 posts held, back to 27 July 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 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 20 posts for this entry, the most recent from 13 September 2025. An engagement rate over an empty window would be a number about nothing.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 4 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 reactions 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 27 July 2025 to 13 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
福利来公群编号2222/856/6699快三扫雷硬碰硬不抽水 刁哈哈扫雷 🔗:https://t.me/+U6hPQ2xY3LA3Mjlk 刁哈哈快三 🔗:https://t.me/+fmlj36JQV6tjMjBk 500流水包 300u 60包 (856公群刁哈哈快三)https://t.me/c/2612588424/622470
❤1
Signed 九州娱乐-飞鱼
其实挺感激这群人的 有些人 思想不端正 有的人品德端正 哎 加油少年
Signed 刁哈哈(福利来担保@FLL8)
Photo, posted without a caption
Signed 刁哈哈(福利来担保@FLL8)
各位老板,游戏停一下,重启一下,麻烦了,谢谢。 一下在赢钱。
Signed 刁哈哈(福利来担保@FLL8)
这种傻逼 你妈死了 气死我了
Signed 刁哈哈(福利来担保@FLL8)
挂逼的兄弟们 找我做承兑 10个点
Signed 刁哈哈(福利来担保@FLL8)
刁哈哈pc28 https://t.me/+rmIgKKMLHmU0Nzdl 刁哈哈扫雷 https://t.me/+E-y16ANrYqs1NDBk 刁哈哈快3 https://t.me/+F03yxmSTQS82MTc0 刁哈哈牛牛 https://t.me/+L0xED1OhmCk5MTU9 500流水包 300u 60包 (234公群刁哈哈扫雷) https://t.me/c/2068659757/4029979
❤1
Signed 刁哈哈(福利来担保@FLL8)
公群990起点快三,VIP晋级奖励+VIP周流水奖励,流水5000进VIP福利群,每日合计发送999U红包,流水1000以上更可参与摇骰子游戏,最高可获得1200U奖励,详情查看公群规则! 🔥快三公群链接: https://t.me/+iUIbxqrEOX45MTQ0 🔥红包链接: https://t.me/c/2451773099/2887736
Signed 刁哈哈(福利来担保@FLL8)
😃 叼哈哈 😃😀😃 🔖福利红包🧧 https://t.me/c/2357267970/3963763 😃😀😃😀 😃https://t.me/+e4Pot_QlaPMwNWI1😃 📣📣小门槛,大惊喜📣📣 😀😃😀😃
Signed 刁哈哈(福利来担保@FLL8)
200流水 688u红包 https://t.me/c/2882662634/55849 群链接 https://t.me/+G7C4vflK9yY0Njk0 豹子顺子最大最小都有奖励
Signed 刁哈哈(福利来担保@FLL8)
👑金宝娱乐👑叼哈哈满赔扫雷1:1/加拿大pc/快3/网盘/扫雷纯流水反2.3% ★实力金宝上押超100000U 每天VIP群/公群红包不断,隐藏各种丰厚大奖! 游戏下注赔率及格式⤵⤵ ✔大/小/单/双2.0(格式:大xx) ✔大单/小双5.75(格式:大单xx) ✔小单/大双2.9(格式:小单xx) ✔单压数字5.75(格式:6y100) 🔥无任何通杀和抽水,实力硬碰硬🤜告别抽水!赔率拉满!拼的就是运气!!! ——👑金宝娱乐👑旗下火爆公群列表—— 😃公群992 👍金宝叼哈哈满赔扫雷已押38888U 😃公群334 👍 金宝叼哈哈扫雷已押31000U 😃公群025 👍 金宝刁哈哈快3押金28888U 😃公群558 🇨🇦 金宝2.8倍加拿大pc28已押28888U 😃公群198 🇨🇦 金宝刁哈哈网盘PC28已押30001U 🧧公群红包🧧 扫雷🧧:https://t.me/c/2628101716/900099 快三🧧:ht…
Signed 刁哈哈(福利来担保@FLL8)
😃飞天扫雷纯流水模式 —————————————— 🎮 游戏限红:1 - 20000U 💰 游戏返水:实时反水 2.3% 既10000流水反230. 📜 游戏规则: 本群为全网最硬扫雷群,纯流水实时返水,无任何亏损模式! ✅ 发送【反水】即可领取! ✅ 纯流水玩法,流水越多,返得越多! 不为赚钱,只为交朋友 ➡️飞天每日🧧福利群: 当天满足100U游戏流水联系客服💁♀️:@feitian889 进群!多少人达标发多少U多少包! 🧧抢到2.22奖励😀😀😀u 🧧抢到1.11奖励😀😀u 🧧抢到1.23奖励😀😀u 🧧抢到尾数8奖励😀u 🧧抢到最高奖励😀😀u 🧧抢到最低奖励😀😀u 即日起,抽中尾数8奖励发放8U,请知悉! 抽中奖励只选择最高派送,不叠加; 除了8尾奖励不平分,其余抽中相同金额平分! 🥈👍飞天每日🧧内部群:👍 永远不清退 每日00:15左右VIP内部群发放🧧555U/55包!8月份累计满足10000U流水可以申请…
Signed 刁哈哈(福利来担保@FLL8)
Showing the 12 most recent of 20 posts we hold for @hahadashi92773. 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.
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.
@hahadashi92773 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“刁哈哈红包🧧 (关注不要错过)” (@hahadashi92773), 1,394 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/hahadashi92773.
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.