🎰 静安困困 200优惠券 📮 参与条件: 🪪 必须设置用户名 🎫 加入-上海【哈夫克】报告反馈 🎫 加入-上海【哈夫克】福利优惠 🎫 加入-困了就睡觉 🎫 加入-上海【哈夫克】导航 🎫 加入-上海【哈夫克】出击大队 └ 🔑 发送口令﹝上海哈夫克﹞ 🎫 加入-上海【哈夫克】甄选 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 200优惠券 × 3 📅 开奖日期:(北京时间) 2026年11月14日 17时00分00秒
Signed LotteryBest Bot

Channel
@HFKnb86
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,155subscribers
+8,831 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003930519732 |
|---|---|
| Type | Channel |
| Username | @HFKnb86 |
| Description | 哈夫克福利频道,会在日常随机抽取部分股东进行发放出击计划的优惠券。其他福利活动(白嫖、半价定制券、竞拍)都在本频道进行通知 |
| Created | 19 May 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/HFKnb86 |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 |
|---|---|---|---|
| @HFKnb86/172 · this entry2 Nov 2026, 12:00 UTC | @HFKnb555/1452 Nov 2026, 12:00 UTC | 1.00 | under a minute |
| @HFKnb86/174 · this entry3 Nov 2026, 05:07 UTC | @HFKnb555/1473 Nov 2026, 05:07 UTC | 1.00 | under a minute |
| @HFKnb86/176 · this entry3 Nov 2026, 07:36 UTC | @HFKnb555/1493 Nov 2026, 07:36 UTC | 1.00 | under a minute |
| @HFKnb86/178 · this entry3 Nov 2026, 12:00 UTC | @HFKnb555/1513 Nov 2026, 12:00 UTC | 1.00 | under a minute |
| @HFKnb86/180 · this entry5 Nov 2026, 08:00 UTC | @HFKnb555/1535 Nov 2026, 08:00 UTC | 1.00 | under a minute |
| @HFKnb86/188 · this entry7 Nov 2026, 08:11 UTC | @HFKnb555/1617 Nov 2026, 08:11 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HFKnb555 | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @HFKnb555 (7–1) |
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. 7 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 31 comparable posts for this entry, running 27 May 2026 to 10 November 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @HFKnb86 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 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.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 8 Nov 2026, 09:39 | 9,155 | +12 |
| 5 Nov 2026, 00:39 | 9,143 | +26 |
| 1 Nov 2026, 21:16 | 9,117 | +18 |
| 29 Oct 2026, 11:56 | 9,099 | +608 |
| 26 Oct 2026, 03:16 | 8,491 | +37 |
| 22 Oct 2026, 23:59 | 8,454 | -18 |
| 20 Oct 2026, 02:56 | 8,472 | -8 |
| 17 Oct 2026, 07:41 | 8,480 | +8,147 |
| 10 Oct 2026, 05:21 | 333 | -24 |
| 30 Sept 2026, 08:55 | 357 | -15 |
| 15 Sept 2026, 07:38 | 372 | -14 |
| 8 Sept 2026, 17:00 | 386 | -1,373 |
| 3 Sept 2026, 06:37 | 1,759 | -4 |
| 30 Aug 2026, 22:35 | 1,763 | -14 |
| 27 Aug 2026, 12:33 | 1,777 | -8 |
| 24 Aug 2026, 05:56 | 1,785 | +1 |
| 20 Aug 2026, 18:36 | 1,784 | -3,521 |
| 17 Aug 2026, 18:14 | 5,305 | -8 |
| 14 Aug 2026, 14:05 | 5,313 | +4,989 |
| 6 Aug 2026, 22:16 | 324 | first reading |
51 posts held, back to 19 May 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 18 pages of 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. It is computed over the 1 of 28 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 51 (19 May 2026 – 11 November 2026) |
| Views total | 2,902 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 12: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.
Lifetime counters from Telegram’s own channel header, read 11 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.
7 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 7 of the 51 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 51 most recent posts we hold, published 19 May 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 1 of 42 posts held from the last 30 days (2.38%) 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).
🎰 静安困困 200优惠券 📮 参与条件: 🪪 必须设置用户名 🎫 加入-上海【哈夫克】报告反馈 🎫 加入-上海【哈夫克】福利优惠 🎫 加入-困了就睡觉 🎫 加入-上海【哈夫克】导航 🎫 加入-上海【哈夫克】出击大队 └ 🔑 发送口令﹝上海哈夫克﹞ 🎫 加入-上海【哈夫克】甄选 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 200优惠券 × 3 📅 开奖日期:(北京时间) 2026年11月14日 17时00分00秒
Signed LotteryBest Bot
🎰 浦东沐澜 200优惠券 📮 参与条件: 🪪 必须设置用户名 🎫 加入-ML 沐澜🥀——浦东 🎫 加入-上海【哈夫克】报告反馈 🎫 加入-上海【哈夫克】福利优惠 🎫 加入-上海【哈夫克】导航 🎫 加入-上海【哈夫克】出击大队 └ 🔑 发送口令﹝上海哈夫克﹞ 🎫 加入-上海【哈夫克】甄选 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 200优惠劵 × 3 ⚠️ 抽奖说明: 本次抽奖由 @mulangsiqi 浦东沐澜 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证 📅 开奖日期:(北京时间) 2026年11月14日 19时00分00秒
Signed LotteryBest Bot
🎰 浦东依萌 半价券 📮 参与条件: 🪪 必须设置用户名 🎫 加入-依萌🥛の小家(浦东) 🎫 加入-上海【哈夫克】报告反馈 🎫 加入-上海【哈夫克】福利优惠 🎫 加入-上海【哈夫克】导航 🎫 加入-上海【哈夫克】出击大队 └ 🔑 发送口令﹝上海哈夫克﹞ 🎫 加入-上海【哈夫克】甄选 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 半价券 × 1 📅 开奖日期:(北京时间) 2026年11月14日 19时00分00秒
Signed LotteryBest Bot
🎰 普通喵喵 半价券 📮 参与条件: 🪪 必须设置用户名 🎫 加入-上海【哈夫克】报告反馈 🎫 加入-上海【哈夫克】福利优惠 🎫 加入-喵喵的花园🌺 🎫 加入-上海【哈夫克】导航 🎫 加入-上海【哈夫克】出击大队 └ 🔑 发送口令﹝上海哈夫克﹞ 🎫 加入-上海【哈夫克】甄选 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 半价券 × 1 ⚠️ 抽奖说明: 本次抽奖由 @mengqi200719 浦东喵喵 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证 📅 开奖日期:(北京时间) 2026年11月14日 20时00分00秒
Signed LotteryBest Bot
上海【哈夫克】福利优惠 pinned a photo
上海【哈夫克】福利优惠 pinned a photo
✨ 命运揭晓时刻 ✨ 闵行苗苗 200优惠券 开奖了 抽奖人数:21,抽奖号数:21 1. hututu 中得:200优惠券 2. Steveroger 中得:200优惠券 3. 小H是个摄影师 中得:200优惠券 抽奖说明: 本次抽奖由 @jiaojiao1010 闵行苗苗 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证
Signed Saber
✨ 命运揭晓时刻 ✨ 闵行璐遥 半价券 开奖了 抽奖人数:53,抽奖号数:53 1. LiLi 中得:半价券 抽奖说明: 本次抽奖由 @luyao895 闵行璐遥 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证
Signed Saber
上海【哈夫克】福利优惠 pinned a photo
✨ 命运揭晓时刻 ✨ 普陀小叶 200优惠券 开奖了 抽奖人数:23,抽奖号数:23 1. 余延 中得:200 优惠券 2. JrichCole 中得:200 优惠券 3. 一夜一次郎 中得:200 优惠券 抽奖说明: 本次抽奖由 @thurman10360 普陀 小叶 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证
Signed Saber
上海【哈夫克】福利优惠 pinned a photo
✨ 命运揭晓时刻 ✨ 虹口莲儿 半价券 开奖了 抽奖人数:38,抽奖号数:38 1. Ccc 中得:半价券 抽奖说明: 本次抽奖由 @lianer1212 虹口莲儿 赞助 1、无上课意向的兄弟,请勿抽奖。 2、中奖24小时内联系老师兑换(过期未兑换,视为恶意鸽子)永久黑名单 3、2天内需按时上课、并提交作业。如有特殊情况,提前报备。 4、凡无故缺席、未提交作业,未报备、将取消后续资格。 5、优惠券禁止私下转让或买卖 🔍 杜绝黑幕,点击查看本次开奖全程验证
Signed Saber
Showing the 12 most recent of 51 posts we hold for @HFKnb86. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 5 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“上海【哈夫克】福利优惠” (@HFKnb86), 9,155 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/HFKnb86.
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.