Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海【哈夫克】甄选

Channel

上海【哈夫克】甄选

@HFKnb666

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

11,878subscribers

-1,818 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001599747346
TypeChannel
Username@HFKnb666
CreatedBetween 1 September 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/HFKnb666

Growth

11,87818,51215,1956 August 2026 — 13,696 subscribers7 August 2026 — 13,639 subscribers8 August 2026 — 18,512 subscribers9 August 2026 — 18,495 subscribers10 August 2026 — 18,470 subscribers11 August 2026 — 18,326 subscribers12 August 2026 — 18,257 subscribers13 August 2026 — 18,233 subscribers14 August 2026 — 18,204 subscribers16 August 2026 — 18,046 subscribers17 August 2026 — 17,942 subscribers18 August 2026 — 16,703 subscribers19 August 2026 — 16,718 subscribers20 August 2026 — 13,064 subscribers22 August 2026 — 13,072 subscribers23 August 2026 — 13,101 subscribers24 August 2026 — 13,130 subscribers25 August 2026 — 13,149 subscribers27 August 2026 — 13,140 subscribers28 August 2026 — 13,088 subscribers29 August 2026 — 12,967 subscribers30 August 2026 — 12,859 subscribers31 August 2026 — 12,652 subscribers1 September 2026 — 12,455 subscribers2 September 2026 — 12,196 subscribers4 September 2026 — 11,878 subscribers6 August 20264 September 2026
26 measurements spanning 29 days, net -1,818. 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 10,883–19,507 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
4 Sept 2026, 08:5711,878-318
2 Sept 2026, 21:4512,196-259
1 Sept 2026, 16:5912,455-197
31 Aug 2026, 17:0612,652-207
30 Aug 2026, 19:5512,859-108
29 Aug 2026, 23:1612,967-121
28 Aug 2026, 21:4713,088-52
27 Aug 2026, 00:4613,140-9
25 Aug 2026, 23:0213,149+19
24 Aug 2026, 23:4713,130+29
23 Aug 2026, 11:4613,101+29
22 Aug 2026, 00:4913,072+8
20 Aug 2026, 19:2313,064-3,654
19 Aug 2026, 19:2416,718+15
18 Aug 2026, 20:0616,703-1,239
17 Aug 2026, 19:4617,942-104
16 Aug 2026, 15:1318,046-158
14 Aug 2026, 21:2718,204-29
13 Aug 2026, 16:0518,233-24
12 Aug 2026, 16:3418,257first reading

Engagement

65 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 55 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.77%
avg views ÷ 11,878 subscribers
Avg views / post
328
61 posts measured
Reaction rate
0.455%
reactions ÷ views · ER floor
Posts in window
61
of 65 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. It is computed over the 26 of 61 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held65 (4 August 20261 September 2026)
Views total20,036
Reactions total43
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 21:42 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

Video runtime
4m 16s
Average length
10s

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

Reaction mix

43 reactions across 23 posts, in 1 kind.

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

Measured over the 65 most recent posts we hold, published 4 August 2026 to 1 September 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

1 Sept 2026, 07:53 UTC867 viewsread 2 September 2026
Photo

😂干员ID: #Ts彤彤(男娘) 哈夫克评级: 😂 位置: #静安 资料:171cm 52kg 胸D 费用:1000p 1500pp 直属联系方式: @tstt123 🤖双向助理: @tstt321bot ✅标签: 标签 Ts 男娘 大胸 御姐 69 口爆 后入 好评在下方评论区

1 Sept 2026, 06:44 UTC160 views1 reactionsread 2 September 2026
Photo

😂干员ID:#馨馨 哈夫克评级:😂 位置:#普陀 资料:165cm 51kg 胸C 费用:700p 1100pp 直属联系方式: @My130z 🤖双向助理:@xinxindejiqiren_bot ✅标签:水多 气质 温柔 双飞 环境好 服务系 屁股大 口技无敌 情绪价值高 好评在下方评论区

1

1 Sept 2026, 06:40 UTC153 viewsread 2 September 2026
Photo

😂干员ID: #浪浪 哈夫克评级: 😂 位置:#长宁 资料:159cm 50kg 胸D 费用:499/45m 699/70m 999/100m 直属联系方式: @moshangchuan 🤖双向助理: @langlang9_bot ✅标签: 半套 推油 服务 中小 抓龙筋 古法抓龙筋 好评在下方评论区

1 Sept 2026, 05:57 UTC159 views1 reactionsread 2 September 2026
Photo

😂干员ID: #奶糖 哈夫克评级: 😂 位置::#虹口 资料:162cm 49kg 胸C 费用:1200p 1900pp 3800包夜 直属联系方式: @cjh520 🤖双向助理: @LL520cjh_bot ✅标签: cos 舌吻 口爆 足交 中式按摩 日式调情 制服诱惑 好评在下方评论区

1

31 Aug 2026, 09:14 UTC5 viewsread 31 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7217300461

Signed 极搜🔍资源搜索@JISOU

31 Aug 2026, 09:01 UTC23 viewsread 31 August 2026
Photo

😂干员ID:#悠悠 哈夫克评级:😂 位置:#松江 资料:165cm 52kg 胸D 费用:800p 1600pp 直属联系方式:@Wxr0606 🤖双向助理:@YouYmik52_bot ✅标签: 舌吻 大胸 毒龙 口爆AB面 鸳鸯浴 制服丝袜 好评在下方评论区

31 Aug 2026, 07:45 UTC33 viewsread 31 August 2026
Photo

😂干员ID:#婉婉 哈夫克评级:😂 位置:#浦东 资料:166cm 49kg 胸C 费用:1100p 1900pp 直属联系方式:@wwaann1 🤖双向助理:http://t.me/wanwanww_bot ✅标签:08 69 舌吻 制服 丝袜 刚下海 开发性高 好评在下方评论区

31 Aug 2026, 07:30 UTC31 views2 reactionsread 31 August 2026
Photo

😂干员ID:#钱多多 哈夫克评级:😂 位置:#徐汇 资料:170cm 50kg 胸D 费用:1000p 1800pp 5000包夜 直属联系方式:@qiandd39 🤖双向助理:@qiandd88bot ✅标签:拍不露脸视频 颜射 回魂萧 水中萧 冰火两重天 深喉 口爆 69 性玩具 轻度耳光 好评在下方评论区

2

31 Aug 2026, 06:46 UTC39 views1 reactionsread 31 August 2026
Photo

😂干员ID:#小熊酱酱 哈夫克评级: 😂 位置:#长宁 资料:160cm 50kg 胸D 费用:1500p 2500pp 直属联系方式: @xiongjiang520 🤖双向助理: @xiaobaobao520_bot ✅标签: cos 鸳鸯浴 水中萧 对镜做爱 好评在下方评论区

1

30 Aug 2026, 09:51 UTC31 viewsread 30 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7217300461

Signed 极搜🔍资源搜索@JISOU

30 Aug 2026, 05:31 UTC308 viewsread 30 August 2026
Photo

😂干员ID:#小辣椒 哈夫克评级:😂 位置:#长宁 资料:160cm 45kg 胸B 费用:1200p 2300pp 直属联系方式:@xxw3823 🤖双向助理:@xiaolaojiao_bot ✅标签:08 69 3点粉 白小纯 制服诱惑 好评在下方评论区

30 Aug 2026, 05:21 UTC235 views1 reactionsread 30 August 2026
Photo

😂干员ID:#可馨 哈夫克评级:😂 位置:#黄埔 资料:163cm 50kg 胸B 费用:500p 900pp 1600包夜 直属联系方式:@kexin2027 🤖双向助理:@sxjqr22bot ✅标签:大胸 制服 胸推 毒龙 鸳鸯浴 舞蹈老师 好评在下方评论区

1

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

Forward network

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.

Mentions

Named by 6 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.

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

“上海【哈夫克】甄选” (@HFKnb666), 11,878 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/HFKnb666.

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.