Telegram RegisterThe public register of Telegram
Telegram profile photo for 新世界哈希频道

Channel

新世界哈希频道

@fhdddb0

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

777subscribers

-6,467 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004387944253
TypeChannel
Username@fhdddb0
Created1 July 2026 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live2 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/fhdddb0

Topic

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.

Growth

7777,2454,0119 August 2026 — 7,244 subscribers9 August 2026 — 7,244 subscribers9 August 2026 — 7,245 subscribers12 August 2026 — 7,221 subscribers16 August 2026 — 6,922 subscribers19 August 2026 — 6,664 subscribers22 August 2026 — 6,059 subscribers25 August 2026 — 5,505 subscribers28 August 2026 — 5,081 subscribers31 August 2026 — 4,745 subscribers4 September 2026 — 4,372 subscribers9 September 2026 — 3,845 subscribers12 September 2026 — 3,403 subscribers16 September 2026 — 2,945 subscribers24 September 2026 — 2,247 subscribers4 October 2026 — 2,061 subscribers10 October 2026 — 1,918 subscribers14 October 2026 — 1,769 subscribers17 October 2026 — 1,663 subscribers21 October 2026 — 1,607 subscribers24 October 2026 — 1,007 subscribers26 October 2026 — 928 subscribers2 November 2026 — 777 subscribers9 August 20262 November 2026
23 measurements spanning 85 days, net -6,467. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
2 Nov 2026, 11:58777-151
26 Oct 2026, 18:20928-79
24 Oct 2026, 04:201,007-600
21 Oct 2026, 03:061,607-56
17 Oct 2026, 17:121,663-106
14 Oct 2026, 11:061,769-149
10 Oct 2026, 13:361,918-143
4 Oct 2026, 18:572,061-186
24 Sept 2026, 20:202,247-698
16 Sept 2026, 23:172,945-458
12 Sept 2026, 20:203,403-442
9 Sept 2026, 06:393,845-527
4 Sept 2026, 01:174,372-373
31 Aug 2026, 16:254,745-336
28 Aug 2026, 15:125,081-424
25 Aug 2026, 22:555,505-554
22 Aug 2026, 23:356,059-605
19 Aug 2026, 17:226,664-258
16 Aug 2026, 17:536,922-299
12 Aug 2026, 17:387,221first reading

Engagement

8 posts held, back to 1 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 pages 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 8 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.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 3 of the 8 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 1 July 2026 to 11 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.

Recent posts

29 Jul 2026, 06:35 UTCviews —

风花代打担保频道 pinned «所有交易认准 担保 谨防代码 交易前用机器人进行验证 @FHXYyzdb_bot 发送 验证+用户名 进行验证 风花代打担保频道 @ntbbb00 风花代打担保验证 :@FHXYyzdb_bot 风花代打担保频道:@fhdddb0 负责人:男童 @ntnt @ffhh 安稳:@FHXY00 风花电子PG:【RMB版】 @fhxypg_bot 青菜:@ck138800 《枪手担保3000u》 泡芙:@paou3 《枪手担保15000u》 青砚:@ss3333330《枪手担保10000u》 两难 @FHXY_LN…»

28 Jul 2026, 02:53 UTC≈1,980 views0 reactionsread 20 August 2026

风花代打大群:@ffhh 风花代打担保频道 @fhdddb0 风花代打成功图频道:@ntbbb00 担保频道:@fhdddb0 风花pg:@fhxypg_bot 纠纷/投诉/建议/上押/中介 任何事宜 皆可联系 董事长:@ntnt @FHXY00 没有本群担保 在群内发广告和接单 会被踢 被踢大群永久拉黑 不予解除!

28 Jul 2026, 02:53 UTC≈1,910 views1 reactionsread 20 August 2026

所有交易认准 担保 谨防代码 交易前用机器人进行验证 @FHXYyzdb_bot 发送 验证+用户名 进行验证 风花代打担保频道 @ntbbb00 风花代打担保验证 :@FHXYyzdb_bot 风花代打担保频道:@fhdddb0 负责人:男童 @ntnt @ffhh 安稳:@FHXY00 风花电子PG:【RMB版】 @fhxypg_bot 青菜:@ck138800 《枪手担保3000u》 泡芙:@paou3 《枪手担保15000u》 青砚:@ss3333330《枪手担保10000u》 两难 @FHXY_LN 《抢手担保9000U 》 杀手乐:@FHXY_Le 《枪手担保8888u》 兽: @ovoshou 《枪手担保7000u》 七安:@FHXY015 《枪手担保7000u》 仙:@WUX8888 《枪手担保5000u》 小天宝宝:@xtbb8 《枪手担保5000u》 uu: @U6676i 《枪手担保3000u》 …

❤1

28 Jul 2026, 02:09 UTC≈1,480 views2 reactionsread 20 August 2026
Photo

所有交易认准 担保 谨防代码 交易前用机器人进行验证 @FHXYyzdb_bot 发送 验证+用户名 进行验证 风花代打交易规则 1️⃣:进款之前协商好规则比如货到就货到结算货不到=0 2️⃣:进算默认进就算退款冻结等各种因素与客户无关我方担保自行承担责任 3️⃣:数字苹果等渠道进款自行提供解绑视频如没提供解绑视频后续出现资金流失等情况则为xk方责任 4️⃣:礼品卡默认核销结算 其他方式结算请提前协商 5️⃣:进款点位问题进款之前与我方担保人员提前了解清楚点位后在进行进款如没说点位进款出现纠纷以市场点位结算 6️⃣:操作需要删除的渠道,操作之前规则说清楚,要删除什么 录制什么视频,必须说的明明白白的,如若只发了善后或者删除两个字,默认=删除短信。如客户忘记录制删除后的视频,但是有证据能证明操作的的确是这个手机,一律按已删除算。需要下发,具体是否是同个手机或证据如自己不能判断可拉纠纷让管理员分辨。 7️⃣:进算渠道进款秒退3分…

❤2

Showing the 8 most recent of 8 posts we hold for @fhdddb0. 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.

Mentions

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.

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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“新世界哈希频道” (@fhdddb0), 777 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/fhdddb0.

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.