Channel
@qdszf
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
59subscribers
-82 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002715607883 |
|---|---|
| Type | Channel |
| Username | @qdszf |
| Created | Between 1 June 2025 and 20 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/qdszf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 04:17 | 59 | -1 |
| 2 Sept 2026, 01:36 | 60 | -23 |
| 25 Aug 2026, 09:51 | 83 | -4 |
| 17 Aug 2026, 12:04 | 87 | -51 |
| 10 Aug 2026, 13:35 | 138 | -3 |
| 9 Aug 2026, 15:16 | 141 | first reading |
20 posts held, back to 20 July 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 20 posts for this entry, the most recent from 1 August 2025. An engagement rate over an empty window would be a number about nothing.
13 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 6 | 46.2% | |
| 💩 | 4 | 30.8% | |
| 🤮 | 2 | 15.4% | |
| 👍 | 1 | 7.69% |
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 4 of the 20 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 July 2025 to 1 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子的昵称： 小言 骗子用户名： @xyyyds18867 苹果直达链接：tg://user?id=7663809893 安卓直达链接：tg://openmessage?user_id=7663809893 其他联系方式： 群组频道链接： 被骗的总金额： 2u 被骗过程说明： 脑残东西 换皮狗 全家死光了 死妈小言 公示人： 他爷爷钟情
💩2👍1👎1
民政婚姻10u 明天早上回 民政婚姻10u 明天早上回 民政婚姻10u 明天早上回 民政婚姻10u 明天早上回 民政婚姻10u 明天早上回 支持各大担保 民政局直出 联系 @zqcd888
👎5💩2🤮2
真地址6u 假地址4u 全天秒 民政婚姻 12u 秒线 民政婚姻 批量10u 秒 10u收几单 明天早上回 公网补齐8u 无视17位 公网猎魔8u 可排除空无需收费 文字全12u 当天回单 联通3u秒 联系 @zqcd888 频道 @qdszf
📣春江供需资讯‼️♻️ 民政婚姻 秒秒秒 无需等待 渠道读了秒 不用等下午啥的 早9—晚6读了秒 12u 有量来拿价格 @zqcd888 真地址 假地址 全天秒6u/4u 真地址 假地址 全天秒6u/4u 真地址 假地址 全天秒6u/4u 专注以下查档业务⬇️ 婚姻 支百 破解支百 支机 码反 联通 三网机主 文字全 公网补齐 公网猎魔 名下车 名下房 专注以下查档业务⬇️ 婚姻 支百 破解支百 支机 码反 联通 三网机主 文字全 公网补齐 公网猎魔 名下车 名下房 专注以下查档业务⬇️ 婚姻 支百 破解支百 支机 码反 联通 三网机主 文字全 公网补齐 公网猎魔 名下车 名下房 民政婚姻 秒秒秒 无需等待 渠道读了秒 不用等下午啥的 早9—晚6读了秒 12u 供应商品:婚姻 查档 商品介绍:民政婚姻秒秒秒 商品价格:12u 是否售后:是 是否支持担保:是 保费哪方承担:需方 交易货币支持:USDT 对接联…
青岛市政府 pinned a photo
民政婚姻 包真 渠道读了秒
✅充值成功，充值金额：75 USDT，获取积分金额：750
💰 +300充值到账 Tron USDT 当前余额：300.2918
真支百回单
✅充值成功，充值金额：99 USDT，获取积分金额：990
过了晚7 依旧秒
破解支百回单
Showing the 12 most recent of 20 posts we hold for @qdszf. 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“青岛市政府” (@qdszf), 59 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/qdszf.
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.