Channel
@qieting
On this record: Growth · Engagement · Posts · Citations · Cite this entry
18subscribers
+8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003644617037 |
|---|---|
| Type | Channel |
| Usernames | @baobiao @huolongguo @lizhi @menglong @putao @qieting @wanlong @ximen @zhuzai |
| Created | 15 December 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 10 times, most recently 6 September 2026 |
| On Telegram | t.me/qieting |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 11:34 | 18 | no change |
| 28 Aug 2026, 04:59 | 18 | no change |
| 27 Aug 2026, 22:23 | 18 | no change |
| 27 Aug 2026, 16:37 | 18 | no change |
| 26 Aug 2026, 18:48 | 18 | no change |
| 26 Aug 2026, 16:38 | 18 | no change |
| 26 Aug 2026, 14:09 | 18 | no change |
| 26 Aug 2026, 12:33 | 18 | no change |
| 25 Aug 2026, 23:14 | 18 | +8 |
| 12 Aug 2026, 09:48 | 10 | no change |
| 12 Aug 2026, 09:46 | 10 | no change |
| 7 Aug 2026, 01:00 | 10 | first reading |
2 posts held, back to 15 December 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 9 pages 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 2 posts for this entry, the most recent from 15 December 2025. An engagement rate over an empty window would be a number about nothing.
@yuntu 云图 1300u @qieting 窃听2000u @wanlong 万隆1300u @ximen 西门2200u @lizhi 荔枝10000u @putao 葡萄13000u @huolongguo 火龙果3500u @baobiao 保镖4000u @menglong 猛龙3200u @zhuzai 主宰5600u @konglong 恐龙5000u 出售以上精品用户名 联系 地主 @dizhu 更多精品用户名选址： @xuan
Channel created
Showing the 2 most recent of 2 posts we hold for @qieting. 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 3 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“地主精品用户名15” (@qieting), 18 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/qieting.
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.