Telegram RegisterThe public register of Telegram
Telegram profile photo for 0押金/南宫博彩洗资口令通道

Channel

0押金/南宫博彩洗资口令通道

@hhjnfdhjnnhh

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

19,960subscribers

+0 since we began measuring on 3 November 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004295822398
TypeChannel
Username@hhjnfdhjnnhh
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live3 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/hhjnfdhjnnhh

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 3 November 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

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.

Views per post sit far below this size band

4.8 average views per post against 19,960 subscribers — an engagement rate of 0.024%. Across the 1,997 registered channels in the same cohort — 10,003–31,612 subscribers, posting mainly in Chinese — the middle half sit between 1.80% and 11.5%, with a median of 4.93%.

What this was computed from
Window30 days (5 October 2026 – 4 November 2026)
Posts measured13 of 20 published in the window (13 exact, 0 rounded by Telegram)
Views totalled62
Mature posts only0.025% over 12 posts read at least 24h after publication
Subscribers19,960 measured 3 November 2026
Cohortb10000:zho · 1,997 channels · p10 0.52% · p25 1.80% · p50 4.93% · p75 11.5% · p90 25.4%
Position in cohort0.852th percentile · 1/200 the cohort median
Uncertainty±0% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_low, last confirmed 4 November 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.

Growth

19,9603 Nov 2026, 05:22 — 19,960 subscribers3 Nov 2026, 22:28 — 19,960 subscribers3 Nov 2026, 05:223 Nov 2026, 22:28
2 measurements taken within a single day. 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”. The vertical axis spans 19,940–19,980 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 22:2819,960no change
3 Nov 2026, 05:2219,960first reading

Engagement

20 posts held, back to 25 October 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 3 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.024%
avg views ÷ 19,960 subscribers
Avg views / post
4.8
13 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held20 (25 October 2026 – 3 November 2026)
Views total62
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 05:23 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.

What this channel posts

Photos
15
Videos
26
Links
27

Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
11m 50s
Average length
1m 05s

Measured directly from 11 videos 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 21:30 UTC2 viewsread 4 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @NG28P320 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@NG3329bot

2 Nov 2026, 18:29 UTC3 viewsread 4 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @NG28P320 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@NG3329bot

1 Nov 2026, 21:23 UTC5 viewsread 4 November 2026
Video

新人小白订阅加入频道看视频教程下单 支付宝小额洗口令红包 平台为24小时自助下单 支付宝小额洗纯BC盘口线上供料 今日口令库存已更新 欢迎自助下单! 做单口令网站:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ 在线客服问题:✈️@NG28P320 双向客服:✈️@NG3329bot

31 Oct 2026, 22:17 UTC5 viewsread 4 November 2026
Video

新人小白订阅加入频道看视频教程下单 支付宝小额洗口令红包 平台为24小时自助下单 支付宝小额洗纯BC盘口线上供料 今日口令库存已更新 欢迎自助下单! 做单口令网站:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ 在线客服问题:✈️@NG28P320 双向客服:✈️@NG3329bot

30 Oct 2026, 16:27 UTC6 viewsread 4 November 2026

用户反馈,关于支付宝风险问题 大家可以参考一下领取口令红包时间的间隔,每十分钟领取一次口令就非常的稳不会被频繁 ✅平台所有的支付方式都是各种生活缴费,游戏充值,合理规避大家的洗资风险,如遇到无法支付,风险提示,请根据指示操作或返回平台切换使用其他支付通道,所有通道都可正常来回切换使用,下发的都是支付宝口令 🥰🥰🥰

30 Oct 2026, 16:00 UTC5 viewsread 4 November 2026
Video

新人小白订阅加入频道看视频教程下单 支付宝小额洗口令红包 平台为24小时自助下单 支付宝小额洗纯BC盘口线上供料 今日口令库存已更新 欢迎自助下单! 做单口令网站:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ 在线客服问题:✈️@NG28P320 双向客服:✈️@NG3329bot

29 Oct 2026, 16:00 UTC8 viewsread 4 November 2026
Video

新人小白订阅加入频道看视频教程下单 支付宝小额洗口令红包 平台为24小时自助下单 支付宝小额洗纯BC盘口线上供料 今日口令库存已更新 欢迎自助下单! 做单口令网站:http://h5izy3659.top/ 24小时备用链接 : h5yy320.top/ 在线客服问题:✈️@NG28P320 双向客服:✈️@NG3329bot

28 Oct 2026, 16:45 UTC9 viewsread 4 November 2026
Photo

口令料子已加码,平台一切正常,稳定运营!临近年关,并发用户多,平台有时库存不足提交订单匹配不到或显示风险交易属于正常,这种请重新提交或使用其他支付通道,所有通道下发的都是支付宝口令,合理规避无风险📱🤑📱

Showing the 12 most recent of 20 posts we hold for @hhjnfdhjnnhh. 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

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.

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

“0押金/南宫博彩洗资口令通道” (@hhjnfdhjnnhh), 19,960 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/hhjnfdhjnnhh.

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.