Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑猫查档(备用防失联)

Channel

黑猫查档(备用防失联)

@HMFC66

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

2,041subscribers

+8 since we began measuring on 4 November 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004408062903
TypeChannel
Username@HMFC66
CreatedBetween 1 June 2026 and 31 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live20 November 2026
Measurements held6
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/HMFC66

Growth

2,0332,0422,037.54 November 2026 — 2,033 subscribers4 November 2026 — 2,034 subscribers7 November 2026 — 2,037 subscribers10 November 2026 — 2,036 subscribers15 November 2026 — 2,042 subscribers20 November 2026 — 2,041 subscribers2,0414 November 202620 November 2026
6 measurements spanning 16 days, net +8. 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 2,032–2,043 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 16:122,041-1
15 Nov 2026, 11:592,042+6
10 Nov 2026, 15:202,036-1
7 Nov 2026, 10:082,037+3
4 Nov 2026, 17:302,034+1
4 Nov 2026, 06:222,033first reading

Engagement

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

ERR · 30 days
0.296%
avg views ÷ 2,041 subscribers
Avg views / post
6.0
20 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 4 November 2026
Posts held20 (3 November 2026 – 4 November 2026)
Views total121
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 06:22 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.

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).

4 Nov 2026, 05:44 UTC2 viewsread 4 November 2026

车大档 😁😁😁😁 黄牌 摩托车 货车 都可以出 报单备注车型 不符合/空不收 提供:车牌号

4 Nov 2026, 05:11 UTC4 viewsread 4 November 2026

美团订房+点餐一体 😁😁😁😁 最新一页记录 点餐不带地址 隔天稳定回 不限量 提供:手机号

4 Nov 2026, 04:49 UTC4 viewsread 4 November 2026
Photo

条出名下车 😁😁😁 无遗漏 不带详情 只出车牌 文字作图回单 包实时 当天回 空收费

4 Nov 2026, 00:15 UTC7 viewsread 4 November 2026
Photo

5年 医疗记录 😁😁😁 非发票改版 独家系统 和卫健委系统差不多数据 保真不保漏 全天人在秒 代理批量来拿价格

4 Nov 2026, 00:14 UTC7 viewsread 4 November 2026

四网宽带地址😁😁😁 移动 电信 联通 广电 都能出 可指定地区运营商 只出一个 找人的好项目 有哪个给哪个,适合找老赖,名下没手机号的,总要租房办宽带吧,直接上门去抓他,比定位好用,用别人的手机号办宽带也一样出 报单提供 名字 身份证号码 每天下午开秒

4 Nov 2026, 00:13 UTC7 viewsread 4 November 2026

支付宝收款码反 二件套😁😁😁 名字手机号 三件套😁😁😁 名字手机号身份证号 三件套出不来的给两件套 收两件套的钱

3 Nov 2026, 22:01 UTC9 viewsread 4 November 2026

微信号反实名 出名字身份证号 包过核验 有名 有地区😁😁😁 无名 无地区😁😁😁 破解出不来的做公网才能出 公网微反一件套😁😁😁 出名字手机号 公网微反二件套😁😁😁😁 出名字手机号身份证号 1-3天内回单 客服 @HMFC8 双向机器人 @HMFC88bot

3 Nov 2026, 21:43 UTC8 viewsread 4 November 2026

1.史上最牛逼个人名下资产轨迹背景调查 😁😁😁😁😁 名下所有银行卡带余额+银行卡流水+全户+名下房+名下车+违章+名下保险+飞火+住宿记录+出入境+名下信托基金+名下银行理财+名下证券+税务信息+在逃撤销+资产流水总额+同行人+名下企业 保真不保漏 敏感收费不给单 2.名下资产查询 😁😁😁😁 名下银行卡账户余额 名下支付宝微信账户余额 名下房 名下车辆 民政婚姻 名下保险 证券(系统反馈多少给多少) 工作日2-5天回完 姓名身份证报单 敏感不要 北京上海不要 客服 @HMFC8 双向机器人 @HMFC88bot

3 Nov 2026, 21:12 UTC7 viewsread 4 November 2026

公网名下银行卡😁😁😁 名下抖音号 😁😁😁 名下快手号 😁😁😁 名下小红书号 😁😁😁 名下网易云号 😁😁😁 抖音号反查手机号😁😁 婚姻记录 😁😁😁 地区房产 😁😁😁 医疗记录 😁😁😁 12306强登 😁😁😁 出入境记录 😁😁😁 抖音关联人 😁😁😁 宽带地址 😁😁😁 PLC假地址 😁😁 小关联 😁😁😁 常用综合快递地址 😁😁😁 客服 @HMFC8 双向机器人 @HMFC88bot

3 Nov 2026, 21:04 UTC6 viewsread 4 November 2026
Photo

3年医疗记录 开 医疗老系统 😁😁😁 在医院用过身份证办理的都有记录 资料是各医院统筹后上传 接收到多少信息记录全部都出 保真不保漏 以医疗系统为准! 提供:名字身份证号 客服 @HMFC8 双向机器人 @HMFC88bot

Showing the 12 most recent of 20 posts we hold for @HMFC66. 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 20 November 2026 — this entry's latest reading, not the date you are reading this.

“黑猫查档(备用防失联)” (@HMFC66), 2,041 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/HMFC66.

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.