Channel name was changed to «查档 开户 开盒 找人»

Channel
查档 开户 开盒 找人
@synb6635
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
9,898subscribers
-413 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002467463824 |
|---|---|
| Type | Channel |
| Username | @synb6635 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/synb6635 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 19:39 | 9,898 | -33 |
| 12 Sept 2026, 21:43 | 9,931 | -42 |
| 8 Sept 2026, 12:36 | 9,973 | -27 |
| 5 Sept 2026, 06:18 | 10,000 | -6 |
| 3 Sept 2026, 11:56 | 10,006 | -13 |
| 2 Sept 2026, 06:52 | 10,019 | -16 |
| 1 Sept 2026, 08:26 | 10,035 | -5 |
| 31 Aug 2026, 11:04 | 10,040 | -14 |
| 30 Aug 2026, 11:33 | 10,054 | -7 |
| 29 Aug 2026, 13:25 | 10,061 | -6 |
| 28 Aug 2026, 15:55 | 10,067 | -11 |
| 27 Aug 2026, 18:53 | 10,078 | -11 |
| 26 Aug 2026, 18:58 | 10,089 | -12 |
| 25 Aug 2026, 17:08 | 10,101 | -26 |
| 24 Aug 2026, 13:53 | 10,127 | -27 |
| 22 Aug 2026, 21:05 | 10,154 | -15 |
| 21 Aug 2026, 07:26 | 10,169 | -5 |
| 20 Aug 2026, 09:12 | 10,174 | -8 |
| 19 Aug 2026, 09:45 | 10,182 | -6 |
| 18 Aug 2026, 13:05 | 10,188 | first reading |
Engagement
23 posts held, back to 8 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 34 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.02%
- avg views ÷ 9,898 subscribers
- Avg views / post
- 299
- 2 posts measured
- Reaction rate
- 0.34%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 23 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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 23 (8 July 2026 – 24 August 2026) |
| Views total | 598 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 04:00 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
- 2m 01s
- Average length
- 30s
Measured directly from 4 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
40 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 42.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 42.5% | |
| 👍 | 12 | 30.0% | |
| 🤣 | 4 | 10.0% | |
| 🎉 | 2 | 5.00% | |
| 👏 | 2 | 5.00% | |
| 👀 | 1 | 2.50% | |
| 😁 | 1 | 2.50% | |
| 🤔 | 1 | 2.50% |
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 13 of the 23 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 8 July 2026 to 24 August 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 Stars
- Stars received
- 3
- across the posts below
- Posts paid on
- 3
- of 20 we hold a reading for · 15%
- Most on one post
- 1
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @synb6635. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 23 most recent posts we hold for this entry, published 8 July 2026 to 24 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
🎭欢迎来到专业查档必果集团👍
❤1
本频道已被 @bbgg 收购
出售频道出售群组有需要的扣一
接广告
本频道拒绝任何违法违规不碰红线不触底线
❤3👏1
出售此款出身份证py脚本无限制不限用死了售后三个月 需准备 姓名 手机号 需要请联系 @liktVsvbsbiP_bot
情x跟time如果看到请联系我
❤1
送几个婚姻发姓名身份证
👍2❤1
有需要做代理的联系我获取代理价,单独给你开站你不用交押金以及其他缴费开站是免费的你只需要负责宣传每天晚上领钱就行了 @liktVsvbsbiP_bot
👍2❤1🎉1
前运营者 目前已将此频道出售 我是现在新运营者 @fgthni 以后有什么事找我
🤣4
需要搭建bot机器人的联系我 https://t.me/liktVsvbsbiP_bot 本频道广告如果涉及违法犯罪一切跟此频道无关请擦亮眼睛注意分辨
👍3❤1🎉1🤔1😁1
Showing the 12 most recent of 23 posts we hold for @synb6635. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@synb6635 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“查档 开户 开盒 找人” (@synb6635), 9,898 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/synb6635.
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.