The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
💎BINGO哈希官方频道💎
@Bingohash888
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
1,192subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001698447513 |
|---|---|
| Type | Channel |
| Username | @Bingohash888 |
| Created | Between 1 December 2021 and 12 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 11 October 2026 |
| On Telegram | t.me/Bingohash888 |
Topic
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 23:37 | 1,192 | -1 |
| 13 Aug 2026, 14:16 | 1,193 | -1 |
| 7 Aug 2026, 06:31 | 1,194 | no change |
| 7 Aug 2026, 06:26 | 1,194 | first reading |
Engagement
18 posts held, back to 12 September 2022 — 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 18 posts for this entry, the most recent from 4 July 2023. An engagement rate over an empty window would be a number about nothing.
Reaction mix
5 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5 | 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 18 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 12 September 2022 to 4 July 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.
🌍 BINGO哈希 🌍 💰无需充值资金无忧 转账既投注 派奖3秒到!派奖钱包资金雄厚 🎁 赔率全网最高! 玩法多样 ! 大小单双百家乐1.995倍 ☑️欢迎各位老板前来爆庄!!! 🔗BINGO哈希官网: hash9.net 注册邀请码 00WR 📞BINGO哈希客服 @BINGOkefu888 📞BINGO哈希客服 @BINGOkefu999 🏆哈希双龙投注地址:TXpg2xigm9iiPWHvKWh8HEiw5B3AafVnN1 🏆哈希牛牛投注地址:TLYSyULWYDCTw9LRA7dqHyijn9qb2bPGPX 🏆哈希庄闲投注地址:TRoT9zVJKe3FEpdCUHWJjoUVqKsKQ1XMhK 🏆幸运哈希投注地址:TLrCTYwvgnJbCCY9iAuEGhkpqMRwQQejnX
🎉🎉BINGO哈希综合平台余1点更新至3点,新增幸运飞艇,极速飞艇,极速时时彩彩票!新增视讯百家乐,电子,棋牌玩法,新老客户余3点以后可进行投注!如有疑问咨询客服 @BINGOkefu888
💎BINGO哈希官方频道💎 pinned Deleted message
🎉🎉世界杯来袭,平台4款体育供您选择,首存复存皆有彩金优惠,欢迎各位老板前来体验! 24小时在线客服 @BINGOkefu888 @BINGOkefu999
👍2
🎉🎉世界杯来袭,平台4款体育供您选择,首存复存皆有彩金优惠,欢迎各位老板前来体验! 24小时在线客服 @BINGOkefu888 @BINGOkefu999
本平台体育已上线,足球,篮球,各种球赛,世界杯应有尽有,欢迎新老客户前来体验!🎉🎉🎉24小时在线客服:@BINGOkefu888
安全警示|相同尾号地址骗局 骗子利用用户转账时复制交易记录中地址的习惯,生成相同尾号的地址作为伪装地址,并利用伪装地址向用户小额转账,使得骗子的地址出现在用户的交易记录中。 例如下图:用户经常转账的地址为「TZHNhq…Jr7bbb」,伪装地址为「TWxaae…Eh7bbb」,它们有相同的尾号「7bbb」。 若用户从交易记录中复制地址进行转账时,只核对了尾号,则很容易错误复制成骗子的伪装地址,不小心转账后就会造成资产损失。 在此提醒大家:由于区块链技术不可篡改的特性,链上转账一旦成功,则无法进行取消、撤回等操作,所以转账前请务必仔细核对地址!
🌍 BINGO哈希 🌍 💰无需充值资金无忧 转账既投注 派奖3秒到!派奖钱包资金雄厚 🎁 赔率全网最高! 玩法多样 ! 大小单双百家乐1.995倍 ☑️欢迎各位老板前来爆庄!!! 🔗BINGO哈希官网: hash9.net 注册邀请码 00WR 📞BINGO哈希客服 @BINGOkefu888 📞BINGO哈希客服 @BINGOkefu999 🏆哈希双龙投注地址:TXpg2xigm9iiPWHvKWh8HEiw5B3AafVnN1 🏆哈希牛牛投注地址:TLYSyULWYDCTw9LRA7dqHyijn9qb2bPGPX 🏆哈希庄闲投注地址:TRoT9zVJKe3FEpdCUHWJjoUVqKsKQ1XMhK 🏆幸运哈希投注地址:TLrCTYwvgnJbCCY9iAuEGhkpqMRwQQejnX (点击地址可直接复制)
👍1
🌍 BINGO哈希 🌍 💰无需充值资金无忧 转账既投注 派奖3秒到!派奖钱包资金雄厚 🎁 赔率全网最高! 玩法多样 ! 大小单双百家乐1.995倍 ☑️欢迎各位老板前来爆庄!!! 🔗BINGO哈希官网: hash9.net 注册邀请码 00WR 📞BINGO哈希客服 @BINGOkefu888 📞BINGO哈希客服 @BINGOkefu999 🏆哈希双龙投注地址:TXpg2xigm9iiPWHvKWh8HEiw5B3AafVnN1 🏆哈希牛牛投注地址:TLYSyULWYDCTw9LRA7dqHyijn9qb2bPGPX 🏆哈希庄闲投注地址:TRoT9zVJKe3FEpdCUHWJjoUVqKsKQ1XMhK 🏆幸运哈希投注地址:TLrCTYwvgnJbCCY9iAuEGhkpqMRwQQejnX
Showing the 12 most recent of 18 posts we hold for @Bingohash888. 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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@Bingohash888 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 8 posts, 8 August 2026 – 8 August 2026
named in 6 posts, 8 August 2026 – 8 August 2026
Cite this entry
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“💎BINGO哈希官方频道💎” (@Bingohash888), 1,192 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Bingohash888.
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.