立案详情 立案侦查 😃😃😃😀 只出最新一条 当天隔天回单 空收一半 私聊拿版 工作日18.00前当天回单 今天已经稳定回一批单子
👍2

Channel
@dscd5555
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
21,769subscribers
-366 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003845323182 |
|---|---|
| Type | Channel |
| Usernames | @dscd5555 @sfddd |
| Created | Between 1 February 2026 and 30 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 78 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/dscd5555 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 18:09 | 21,769 | -44 |
| 27 Oct 2026, 04:01 | 21,813 | -9 |
| 26 Oct 2026, 20:00 | 21,822 | -25 |
| 26 Oct 2026, 02:26 | 21,847 | no change |
| 25 Oct 2026, 18:05 | 21,847 | -16 |
| 24 Oct 2026, 23:27 | 21,863 | -6 |
| 24 Oct 2026, 14:39 | 21,869 | -148 |
| 23 Oct 2026, 23:36 | 22,017 | -31 |
| 23 Oct 2026, 16:41 | 22,048 | -11 |
| 23 Oct 2026, 01:57 | 22,059 | -15 |
| 22 Oct 2026, 15:58 | 22,074 | -7 |
| 21 Oct 2026, 23:50 | 22,081 | -12 |
| 21 Oct 2026, 11:41 | 22,093 | -23 |
| 20 Oct 2026, 16:59 | 22,116 | no change |
| 20 Oct 2026, 08:39 | 22,116 | -11 |
| 19 Oct 2026, 15:00 | 22,127 | -3 |
| 19 Oct 2026, 12:07 | 22,130 | -15 |
| 18 Oct 2026, 14:39 | 22,145 | no change |
| 18 Oct 2026, 13:29 | 22,145 | -82 |
| 17 Oct 2026, 17:11 | 22,227 | first reading |
170 posts held, back to 30 July 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 85 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 October 2026 |
|---|---|
| Posts held | 170 (30 July 2026 – 12 October 2026) |
| Views total | 60,320 |
| Reactions total | 129 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Oct 2026, 20:21 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.
332 reactions across 134 posts, in 7 distinct kinds. The most used accounts for 78.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 260 | 78.3% | |
| ❤ | 59 | 17.8% | |
| 🤓 | 4 | 1.20% | |
| 🤡 | 3 | 0.904% | |
| 😍 | 2 | 0.602% | |
| 😨 | 2 | 0.602% | |
| 🤣 | 2 | 0.602% |
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 137 of the 170 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 332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 170 most recent posts we hold, published 30 July 2026 to 12 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.
立案详情 立案侦查 😃😃😃😀 只出最新一条 当天隔天回单 空收一半 私聊拿版 工作日18.00前当天回单 今天已经稳定回一批单子
👍2
支付宝带id 微信不带id 一月😀😀😃😀三月😃😀😃😀 半年😀😃😃😀一年😀😃😃😃😀 两年😀😀😃😃😀三年😃😃😃😃😀 保真不保漏 ❗️当天回❗️当天回 上限8888 保真不保漏~ —————————————— 快线反诈流水❗️当天回单 一月 😃😃😃😀三月 😃😃😃😀 半年😃😃😃😀一年😀😀😃😀 利息收费 出单收费 保真不保漏上限1000
👍3
公网机主 周五开 公网名下手机号 周四开 独家!条出!给原图! 部分号码注销 或者人已经在国外,过不了三要素 不接受扯皮
👍1
名下资产 福利 😀😃😃😀 法院直出,附法院拍照回单 1. 名下全部银行卡卡号 + 账户余额(剔除:不活跃账户、睡眠卡、已注销卡) 2. 名下全部实名微信账户余额 3. 名下全部实名支付宝账户余额 4. 名下股票、证券、保险资产信息 敏感别报 扣费不给单 3-7天回 板子私聊
👍2
名下卡不带余 😃😃😃😀 保真不保漏 回单周期:3个工作日! ————————————————- 名下所有卡号带余额 😀😀😃😀 保真不保漏 敏感人物 扣单 敏感包括 公检法 各大人物 回单时间:报单日开始3-7天回单 余额有失败的(反馈不出来)介意勿报!
👍2
【名下资产查询】 提供身份证号码姓名报单 (北京、上海户籍不要) 反馈: 💰名下支付宝微信账户余额 💰名下银行卡账户余额 💰名下房,名下车辆,民政婚姻,名下保险、证券(系统反馈多少给多少) 回单时间3-5天左右 😃😀😃😀 只做源头业务,所有业务均经过埋雷测试,支持一切售后,欢迎打假,可放心下单
👍3
我不想做任何不认识的春江公群业务员 老板的单子 说起来也是干查档的 基本的常识都没有,单子少,事特别多 订单号都不会验证,神人
👍6
美团最新地址 😀😃😃😀 一年内最新十条 一条也收费 文件回单 已测试 真正的美团 提供:手机号报单 3-5天回 ————————————————— 淘宝闪购外卖地址 😃😃😀 订单收货地址 无遗漏 一年最新1-10条 当天的也能出来 找人首选 用的人多 基本都是外卖 提供:手机号 当天回
👍4
一年内美团饿了么😀😀😃😀 目前空车 来的明天回⚡️ 目前不止外卖还有很多电商购物一体‼️ 1-2天回单 基本上无遗漏 私聊拿模板 带订单编号 下单人手机号 收货人手机号 收货地址 商家名称 商家地址 商家id 商品详情 提供:手机号 无需身份证
👍4
公网微信两件套 开 😀😀😃😀 1-2天左右回
👍3
真地址 个户 😃😀 人在秒 人在秒 人在秒 24小时个户带头 批量可谈 19:30以后出头唯一线路
👍2
司法冻结 😃😃😃😀 反炸出单 原图出单 有流水 有经办 晚上回 晚上回
❤1👍1
Showing the 12 most recent of 170 posts we hold for @dscd5555. 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.
@dscd5555 edited 2 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
需不需要助理
The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 170 most recent posts we hold, published 30 July 2026 to 12 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
“大帅社工库查档开户交流群” (@dscd5555), 21,769 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/dscd5555.
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.