Telegram RegisterThe public register of Telegram

Channel

㊙️高德 天眼查人/档 @zhencha 案例

@zhencha

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

1,082subscribers

-9 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002834788938
TypeChannel
Username@zhencha
CreatedBetween 1 June 2025 and 3 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/zhencha

Growth

1,0821,0911,086.57 August 2026 — 1,091 subscribers7 August 2026 — 1,091 subscribers11 August 2026 — 1,082 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -9. 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 1,081–1,092 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:081,082-9
7 Aug 2026, 18:511,091no change
7 Aug 2026, 04:011,091first reading

Engagement

14 posts held, back to 3 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 posts for this entry, the most recent from 3 August 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 5 posts, in 1 kind.

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

Measured over the 14 most recent posts we hold, published 3 August 2025 to 3 August 2025, 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

3 Aug 2025, 16:38 UTCviews —

Channel name was changed to «㊙️高德 天眼查人/档 @zhencha 案例»

3 Aug 2025, 16:36 UTC≈2,810 views1 reactionsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:犯罪网逃 云搜版 👍需要提供:身份证号码 👍查寻结果:犯罪记录➕网逃记录 😃 联系 @@feiu 双向 @gddb

1

3 Aug 2025, 16:36 UTC≈3,430 views1 reactionsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:车辆档案查询 👍需要提供:车牌号 👍查寻结果:如图所示 😃 联系 @feiu 双向 @gddb

1

3 Aug 2025, 16:36 UTC≈1,290 viewsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:立案详情 👍需要提供:身份证号 👍查寻结果:立案编号 案情简要 办案单位 同案人,所有嫌疑人 到案 或者 在逃 😃 联系 @feiu 双向 @gddb

3 Aug 2025, 16:36 UTC≈1,320 viewsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:抖音实名 👍需要提供:抖音号 👍查寻结果:实名信息 😃 联系 @feiu 双向 @gddb

3 Aug 2025, 16:36 UTC≈1,510 views2 reactionsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:人脸识别 👍需要提供:清晰照片 👍查寻结果:如图所示 😃 联系 @feiu 双向 @gddb

2

3 Aug 2025, 16:36 UTC≈1,680 viewsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:司法口供 嫌疑人口供 👍需要提供:身份证号码/银行卡号 👍查寻结果:如图所示是司法口供,嫌疑人口供很敏感,部分地区可出,空收一半; 😃 联系 @feiu 双向 @gddb

3 Aug 2025, 16:36 UTC≈2,170 views1 reactionsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:车辆车轨 👍需要提供:车牌号 👍查寻结果:车辆照片+车辆轨迹最新 😃 联系 @feiu 双向 @gddb

1

3 Aug 2025, 16:36 UTC≈5,070 views11 reactionsread 7 August 2026
Video

😁😁😁😁😁😁😁😁 👍集团永不失联 @gaode 高德 😄😄😄😄😄😄 👍司法口供👍犯罪网逃👍立案详情 👍人脸识别👍个户全户👍手机定位 👍手机轨迹👍开房记录👍人轨车轨 👍微支实名👍查收款码👍抖音实名 👍卡号实名👍手机实名👍现住地址 👍外卖快递👍常用号码👍护照反查 👍名下车房👍名下公司👍名下护照 👍名下号码👍名下卡号👍身份正反 👍银行流水👍微支流水👍微Q提取 👍查出入境👍人员关联👍卡内余额 👍模糊找人👍银行预留👍公司法人 👍飞机火车👍婚姻医疗👍学历征信 👍车牌车主👍车辆违章👍社保记录 👍通话记录👍以上没例出的也能查 随时为你守候 飞机有我们 问题轻松搞定👍 😂😂😂😂😂😂😂 联系客服进入 @gaode 👈🏻 所有业务可咨询,提供任何咨询服务包括免费法律咨询;负责人 @feiu 高端外围 @gdww 高端包养 @gdby

11

3 Aug 2025, 16:36 UTC860 viewsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:名下公司 👍需要提供:身份证号码 👍查寻结果:名下所有公司,个体,所有名下公司信息 😃 联系 @feiu 双向 @gddb

3 Aug 2025, 16:36 UTC890 views0 reactionsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:名下所有银行卡 👍需要提供:身份证号码 👍查寻结果:名下所有银行卡,不保证遗漏 😃 联系 @feiu 双向 @gddb

3 Aug 2025, 16:36 UTC975 viewsread 7 August 2026
Photo

😄😄😄😄😄😄 👍查询业务:银行卡查余额 👍需要提供:银行卡 或者 身份证号 👍查寻结果:工,农业,中国,建设,邮政,广发,光大 😃 联系 @feiu 双向 @gddb

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

Citation-graph rank

Citation-graph rank — 149,620 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“㊙️高德 天眼查人/档 @zhencha 案例” (@zhencha), 1,082 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/zhencha.

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.