Telegram RegisterThe public register of Telegram
Telegram profile photo for FBI天眼 只发布一手资源

Channel

FBI天眼 只发布一手资源

@cheguansuo88

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

40,347subscribers

-2,817 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002159934768
TypeChannel
Username@cheguansuo88
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 October 2026
Measurements held50
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/cheguansuo88

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.

Growth

40,34743,16441,755.57 August 2026 — 43,164 subscribers7 August 2026 — 43,164 subscribers8 August 2026 — 43,096 subscribers9 August 2026 — 43,020 subscribers10 August 2026 — 42,975 subscribers11 August 2026 — 42,933 subscribers12 August 2026 — 42,886 subscribers14 August 2026 — 42,831 subscribers15 August 2026 — 42,790 subscribers17 August 2026 — 42,692 subscribers18 August 2026 — 42,642 subscribers19 August 2026 — 42,593 subscribers20 August 2026 — 42,555 subscribers21 August 2026 — 42,515 subscribers23 August 2026 — 42,477 subscribers25 August 2026 — 42,425 subscribers25 August 2026 — 42,409 subscribers26 August 2026 — 42,372 subscribers28 August 2026 — 42,351 subscribers29 August 2026 — 42,319 subscribers30 August 2026 — 42,282 subscribers31 August 2026 — 42,231 subscribers1 September 2026 — 42,200 subscribers2 September 2026 — 42,121 subscribers3 September 2026 — 42,082 subscribers5 September 2026 — 42,009 subscribers8 September 2026 — 41,892 subscribers11 September 2026 — 41,797 subscribers13 September 2026 — 41,711 subscribers15 September 2026 — 41,671 subscribers17 September 2026 — 41,593 subscribers19 September 2026 — 41,519 subscribers26 September 2026 — 41,271 subscribers4 October 2026 — 41,015 subscribers9 October 2026 — 40,821 subscribers13 October 2026 — 40,720 subscribers14 October 2026 — 40,668 subscribers15 October 2026 — 40,638 subscribers16 October 2026 — 40,605 subscribers17 October 2026 — 40,592 subscribers18 October 2026 — 40,566 subscribers19 October 2026 — 40,542 subscribers20 October 2026 — 40,525 subscribers21 October 2026 — 40,502 subscribers22 October 2026 — 40,477 subscribers23 October 2026 — 40,456 subscribers24 October 2026 — 40,432 subscribers26 October 2026 — 40,412 subscribers26 October 2026 — 40,394 subscribers27 October 2026 — 40,347 subscribers7 August 202627 October 2026
50 measurements spanning 81 days, net -2,817. 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 39,924–43,587 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
27 Oct 2026, 20:5640,347-47
26 Oct 2026, 21:4040,394-18
26 Oct 2026, 00:2740,412-20
24 Oct 2026, 22:1640,432-24
23 Oct 2026, 21:0740,456-21
22 Oct 2026, 19:1840,477-25
21 Oct 2026, 16:0040,502-23
20 Oct 2026, 14:5940,525-17
19 Oct 2026, 13:0740,542-24
18 Oct 2026, 16:2740,566-26
17 Oct 2026, 18:4840,592-13
16 Oct 2026, 17:3640,605-33
15 Oct 2026, 14:1840,638-30
14 Oct 2026, 16:1640,668-52
13 Oct 2026, 07:0540,720-101
9 Oct 2026, 03:2140,821-194
4 Oct 2026, 17:1741,015-256
26 Sept 2026, 20:0041,271-248
19 Sept 2026, 17:5641,519-74
17 Sept 2026, 08:1541,593first reading

Engagement

162 posts held, back to 18 June 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 161 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.461%
avg views ÷ 40,347 subscribers
Avg views / post
186
78 posts measured
Reaction rate
0.633%
reactions ÷ views · ER floor
Posts in window
78
of 162 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 12 of 78 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 27 October 2026
Posts held162 (18 June 2026 – 27 October 2026)
Views total14,522
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Oct 2026, 12:10 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.

Reaction mix

20 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 90.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1890.0%
😁15.00%
🤡15.00%

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 18 of the 162 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 162 most recent posts we hold, published 18 June 2026 to 27 October 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

27 Oct 2026, 09:27 UTC60 viewsread 27 October 2026

微信流水带id 快线开 限量😍😍号发车😍😍号左右回单 收满即停 报单不撤 接受不了时间的别报 一年😍😍🤣🤣两年 😍😍🤣🤣 三年😍😍🤣🤣四年😍😍🤣🤣 五年😍😍🤣🤣 敏感收费不给单 报单不撤 收必回 限量 带身份证报单 身份证号必须是微信的绑定身份证(错误信息吃单)

26 Oct 2026, 13:22 UTC108 viewsread 27 October 2026

老三页 开同😍🤣🤣🤣😍 人轨+开同🤣😍🤣🤣😍 大关联开😍😍🤣🤣😍 人轨 😍😍😍😍 单开 😍🤣🤣😍 飞火 😍🤣🤣😍 5-10年记录 开同五年 同住人系统现在卡 报单须知 遗漏稍大 同住人查空不收费 保真不保漏 再报当天隔天 另有两页开同🤣🤣🤣🤣🤣 5年飞火 😍😍🤣🤣

24 Oct 2026, 06:41 UTC173 viewsread 27 October 2026

老三页 人轨+开同😍😍🤣🤣🤣 开同😍🤣🤣🤣😍 大关联开😍😍🤣🤣😍 人轨 😍😍😍😍 单开 😍🤣🤣😍 飞火 😍🤣🤣😍 5-10年记录 开同五年 同住人系统现在卡 报单须知 遗漏稍大 同住人查空不收费 保真不保漏 再报当天隔天 另有两页开同🤣🤣🤣🤣🤣 5年飞火 😍😍🤣🤣

23 Oct 2026, 04:42 UTC210 viewsread 27 October 2026

老三页 人轨+开同😍😍🤣🤣🤣 开同😍😍🤣🤣😍 人轨 😍😍😍😍 单开 😍🤣🤣😍 飞火 😍🤣🤣😍 5-10年记录 开同五年 同住人系统现在卡 报单须知 遗漏稍大 同住人查空不收费 保真不保漏 截止10月21日前的单子全部回完 再报当天隔天 另有5年飞火 😍😍🤣🤣 可吃敏感单

21 Oct 2026, 17:12 UTC207 views1 reactionsread 27 October 2026

老三页 开同😍😍🤣🤣😍 人轨 😍😍😍😍 单开 😍🤣🤣😍 飞火 😍🤣🤣😍 5-10年记录 开同五年 同住人系统现在卡 报单须知 遗漏稍大 同住人查空不收费 保真不保漏 截止10月21日前的单子全部回完 再报当天隔天 另有打印版飞火 😍😍🤣🤣 可吃敏感单

❤1

20 Oct 2026, 07:03 UTC221 viewsread 27 October 2026

源头云搜 😍😍🤣😍 当天回单 限量15单 云搜+犯罪+网逃+撤销 云搜护照 云搜吸毒涉毒 云搜失信 云搜名下车 云搜名下公司 选其一 空收费

19 Oct 2026, 15:31 UTC233 viewsread 27 October 2026

微信流水不带ID 支付宝流水带id 一个月 🤣🤣🤣🤣 三个月 🤣🤣🤣🤣 六个月 🤣🤣🤣🤣 一年 🤣🤣🤣🤣 两年 🤣🤣🤣🤣🤣 三年 🤣🤣🤣🤣🤣 出8888条 保真不保漏 ! 当天隔天回 有单量可谈 无盲流水 😍 😍 😍🤣😍😍 🤣 😍 😍😍😍😍 🤣 😂 😍😍😍😍 🤣 😂 🤣😍🤣🤣 上限8888 报单谨慎 扯皮别来

19 Oct 2026, 15:30 UTC214 viewsread 27 October 2026

老三页遗漏最小版 开同😍😍🤣🤣😍 人轨 😍😍😍😍 单开 😍🤣🤣😍 飞火 😍🤣🤣😍 5-10年记录 开同五年 同住人系统现在卡 报单须知 遗漏稍大 同住人查空不收费 保真不保漏 再报当天隔天 另有打印版飞火 😍😍🤣🤣 可吃敏感单

19 Oct 2026, 02:26 UTC216 views0 reactionsread 27 October 2026

手机轨迹系列 开普勒手机轨迹版 出全部 😍😍😍😍 一年内所有轨迹 满5条出单收费 回单时间 : 当天/ 隔天回单 保真不保漏 开普勒版本因设备识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。

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

Posts edited after publishing

@cheguansuo88 edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
14 August 2026
Most recent edit
10 October 2026

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

“FBI天眼 只发布一手资源” (@cheguansuo88), 40,347 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/cheguansuo88.

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.