导航分类,点击直接跳转 先生 - 小姐 点击直接跳转
Channel
先生/小姐
@qiongq
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
5subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003918724778 |
|---|---|
| Type | Channel |
| Username | @qiongq |
| Created | 20 April 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/qiongq |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 03:57 | 5 | -1 |
| 31 Aug 2026, 05:46 | 6 | +2 |
| 13 Aug 2026, 09:48 | 4 | no change |
| 10 Aug 2026, 03:46 | 4 | first reading |
Engagement
6 posts held, back to 20 April 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 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 6 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
1
小姐 @aoxiaojie 138 敖小姐 @bangxiaojie 108 班小姐 @beixiaojie 168 北小姐 @boxiaojie 128 波小姐 @canxiaojie 108 灿小姐 @cengxiaojie 138 曾小姐 @cenxiaojie 108 岑小姐 @chanxiaojie 108 产小姐 馋小姐 @chaxiaojie 138 茶小姐 @chouxiaojie 108 丑小姐 @chuaixiaojie 138 初爱小姐 @chuxiaojie 198 楚小姐 @cixiaojie 138 辞小姐 @danxiaojie 138 单小姐 @diexiaojie 168 蝶小姐 @dunxiaojie 108 顿小姐 @enxiaojie 168 恩小姐 @feixiaojie 168 菲小姐 @gaixiaojie 108 盖小姐 @gangxiaojie 108 甘小姐 @g…
Channel name was changed to «先生/小姐»
先生 @bangxiansheng 138 邦先生 @banxiansheng 108 板先生 @biaoxiansheng 138 彪先生 @binxiansheng 138 彬先生 斌先生 @buxiansheng 138 布先生 @cengxiansheng 138 曾先生 @cexiansheng 138 策先生 @chongxiansheng 108 虫先生 @chouxiansheng 108 臭先生 @chuixiansheng 108 锤先生 @chunxiansheng 108 淳先生 @cixiansheng 108 辞先生 @couxiansheng 108 凑先生 @cunxiansheng 108 寸先生 @dangxiansheng 138 荡先生 @enxiansheng 138 恩先生 @gaixiansheng 138 盖先生 @gangxiansheng 138 钢先生 @ganxi…
Channel created
Showing the 6 most recent of 6 posts we hold for @qiongq. 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.
Mentions
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.
Names
Channels on the register whose handles appear in this channel's posts.
@bbb77x · 31 postdd2jd
@dd2jd · 31 postfeihuohuo
@feihuohuo · 31 postff6zf
@ff6zf · 31 postggx9g
@ggx9g · 31 postjiaolaolao
@jiaolaolao · 11 postjjc3j
@jjc3j · 31 postjjjwwb
@jjjwwb · 31 postll3ql
@ll3ql · 11 postmitongtong
@mitongtong · 11 postpingjiajia
@pingjiajia · 31 postpp0cp
@pp0cp · 41 postppprrg
@ppprrg · 41 postqiaopinpin
@qiaopinpin · 41 postqincheche
@qincheche · 31 postttk6t
@ttk6t · 11 postvv9lv
@vv9lv · 11 postwoguangguang
@woguangguang · 11 postww8kw
@ww8kw · 31 postwwu8w
@wwu8w · 11 postwwwiix
@wwwiix · 11 postyangjiangjiang
@yangjiangjiang · 31 postyinxiangxiang
@yinxiangxiang · 31 postzaitaitai
@zaitaitai · 31 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@qiongq named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 14 August 2026 – 14 August 2026
Cite this entry
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“先生/小姐” (@qiongq), 5 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/qiongq.
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.