躺平两个月回来了之前有了解过的没有及时回复的老板可以来问问你需要的“业务”,或许我可以做业务全开,瓦片尚有翻身日,东风也有转南时”2026还有5个月,加油⛽
❤2

Channel
@s680ddt
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
157subscribers
+22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002796055984 |
|---|---|
| Type | Channel |
| Username | @s680ddt |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/s680ddt |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 4 Nov 2026, 08:38 | 157 | +1 |
| 27 Oct 2026, 11:38 | 156 | -1 |
| 19 Oct 2026, 21:58 | 157 | -2 |
| 2 Oct 2026, 15:18 | 159 | +6 |
| 17 Sept 2026, 02:39 | 153 | +2 |
| 8 Sept 2026, 19:15 | 151 | +8 |
| 30 Aug 2026, 00:28 | 143 | +3 |
| 15 Aug 2026, 12:28 | 140 | +6 |
| 9 Aug 2026, 00:15 | 134 | no change |
| 8 Aug 2026, 02:35 | 134 | -1 |
| 7 Aug 2026, 19:14 | 135 | first reading |
18 posts held, back to 9 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 18 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
28 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 67.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 67.9% | |
| 👍 | 7 | 25.0% | |
| 👏 | 1 | 3.57% | |
| 🥰 | 1 | 3.57% |
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 10 of the 18 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 9 November 2025 to 26 July 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.
躺平两个月回来了之前有了解过的没有及时回复的老板可以来问问你需要的“业务”,或许我可以做业务全开,瓦片尚有翻身日,东风也有转南时”2026还有5个月,加油⛽
❤2
需要港卡 美卡实名企业微信的老板,可代实名,可出成品,价格十分优惠,可以联系我 @Aujinqian
Signed 爆单 阿乐
QQ登录不上的 没有入口的号,来我这边,有新方法,有办法可以上号,包开
Signed 爆单 阿乐
批发钉钉,包不做业务隔天不死 从现在开始 来拿货的 找我 半月 满月 半年 满年都有 @Aujinqian
Signed 爆单 阿乐
Photo, posted without a caption
❤4
Signed 爆单 阿乐
1.快手实名激活成品直登号 安卓机备份包登录 靠谱好用 2.快手双参激活成品直登号,安卓设备云机登录 一种分身大师登录 一种云机登录 需要的老板联系
❤1🥰1
Signed 爆单 阿乐
快手激活成品号 直登流程(全实名) --限安卓手机 打开root权限 电脑云手机(雷电云 红手指) 1.打开云机 下载好最新版本的快手 和上号器 2.去设置打开root权限 3.打开上号器 输入参数 一键上号 自动登录跳转到快手 售后规则;包48小时内不会自动掉线 包7天内不跳二次激活 7天内找回包换 功能自测 有货 需要的老板滴滴 @Aujinqian
Signed 爆单 阿乐
出实名红薯号 设备干净/刷机=耐用耐操
Signed 爆单组 阿乐
QQ号扫码查违规 目前只有图2扫码查不出来
❤1
Signed 爆单组 阿乐
各位大佬:由于行情原因导致工作室和地推都去高价地方产值和做号,所以明天开始咱们快手📱现货实名成品上涨二十,有需要的晚上预约发号白天上号。
Signed 爆单组 阿乐
QQ解封 小红书实名 企业微信实名 pinned «小红书实名 解核对📱 QQ解封📱 陌陌号📱 快手激活实名号📱 微信辅助注册📱 成品飞机号\代开会员📱 企业微信实名/微信实名📱 淘宝解封»
各位老板:快手成品实名号要货的每天晚上来预约,马上没货了就只能再等一天,每天名额有限。@Aujinqian
Signed 爆单组 阿乐
Showing the 12 most recent of 18 posts we hold for @s680ddt. 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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“QQ解封 小红书实名 企业微信实名” (@s680ddt), 157 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/s680ddt.
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.