企业微信三合一原机🉑寄设备🉑转云机,已过获客,需要的滴滴 微信实名,企业法人,营业执照,三合一 广东地区快递当天到 出微信换绑 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道

Channel
@DS16888999
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
7,659subscribers
-267 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001850195799 |
|---|---|
| Type | Channel |
| Username | @DS16888999 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/DS16888999 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 04:38 | 7,659 | -15 |
| 14 Sept 2026, 15:00 | 7,674 | -25 |
| 11 Sept 2026, 09:37 | 7,699 | -32 |
| 7 Sept 2026, 01:17 | 7,731 | -26 |
| 2 Sept 2026, 01:32 | 7,757 | -28 |
| 30 Aug 2026, 00:28 | 7,785 | -23 |
| 27 Aug 2026, 10:59 | 7,808 | -52 |
| 24 Aug 2026, 07:24 | 7,860 | -26 |
| 20 Aug 2026, 23:52 | 7,886 | -13 |
| 18 Aug 2026, 01:22 | 7,899 | -13 |
| 14 Aug 2026, 23:53 | 7,912 | -14 |
| 11 Aug 2026, 17:05 | 7,926 | no change |
| 11 Aug 2026, 16:15 | 7,926 | first reading |
16 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 14 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 25 August 2026 |
|---|---|
| Posts held | 16 (30 July 2026 – 25 August 2026) |
| Views total | 3,262 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:26 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.
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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 100.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 2 of the 16 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 July 2026 to 25 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.
企业微信三合一原机🉑寄设备🉑转云机,已过获客,需要的滴滴 微信实名,企业法人,营业执照,三合一 广东地区快递当天到 出微信换绑 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
大叔微信出货群🍉 pinned «大叔集团总押金😀😃😃😃😃💰 1.主要收快手实名未实名 租号 无限续租盘 无限位置 秒上 2.钉钉买断 新注册 月号年号都要 3.长期招收QQ续租价格拉满无限续租 4.大量收刚注册实名小红书无限续租»
上新美国 香港1-7天短信白 现货500+
Signed A大叔(骗子号没开会员)防骗子进频道
出出192手表ZC 换绑 出扫码3-8年白 抖音有货 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
原机一证一开企业绿标主体: ❶二合一 :创建人和信微是同一个实名人,营业执照是另外一个人 ❷三合一 :营业执照法人 创建人 微信 同个实名人 客服: @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
企业微信三合一原机🉑寄设备🉑转云机,已过获客,需要的滴滴 微信实名,企业法人,营业执照,三合一 广东地区快递当天到 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
企业微信三合一原机 微信实名,企业法人,营业执照,三合一 广东地区快递当天到 24h自助发卡机器人 @DS02468_bot
Signed A大叔(骗子号没开会员)防骗子进频道
出出192手表ZC 换绑 出扫码3-8年白 抖音有货 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
美卡真护照支付宝,包上号,包支付,需要的来, 出支付宝真实护照,一手自产自销 后期出现人核验 可以配合人脸 但不保证百分之百 真护照微信,10万额度
👍1
Signed A大叔(骗子号没开会员)防骗子进频道
😂😂香港微信系列 大量出 不包功能 包登录十分钟 香港1~3月短信【绑卡实名】 香港半年短信【绑卡实名】 香港一年短信【绑卡实名】
Signed A大叔(骗子号没开会员)防骗子进频道
企业微信三合一原机 微信实名,企业法人,营业执照,三合一 广东地区快递当天到 24h自助发卡机器人 @DS02468_bot
Signed A大叔(骗子号没开会员)防骗子进频道
出出162手表ZC 换绑 出扫码3-8年白 抖音有货 @DS02468
Signed A大叔(骗子号没开会员)防骗子进频道
Showing the 12 most recent of 16 posts we hold for @DS16888999. 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.
@DS16888999 edited 3 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.
Named by 2 registered channels — 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“大叔微信出货群🍉” (@DS16888999), 7,659 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/DS16888999.
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.