Channel
盯射-旗袍
@jintianxiawuqushizhongxinliuda41
On this record: Topic · Growth · Engagement · Citations · Cite this entry
42subscribers
+33 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004426366806 |
|---|---|
| Type | Channel |
| Username | @jintianxiawuqushizhongxinliuda41 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 October 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 9 |
| On Telegram | t.me/jintianxiawuqushizhongxinliuda41 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 22 October 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Oct 2026, 19:33 | 42 | no change |
| 21 Oct 2026, 18:06 | 42 | +1 |
| 6 Oct 2026, 10:15 | 41 | +3 |
| 25 Sept 2026, 17:20 | 38 | +2 |
| 3 Sept 2026, 09:35 | 36 | +2 |
| 27 Aug 2026, 08:15 | 34 | +1 |
| 21 Aug 2026, 08:04 | 33 | +1 |
| 14 Aug 2026, 21:55 | 32 | +23 |
| 6 Aug 2026, 21:46 | 9 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 11 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.
@baidengbaideng · 101 post欧博官网|欧博私网|欧博开户|欧博代理
@longteng1423 · 171 post玛卡提修车 玛卡提上门 马提亚外围 玛卡提扶手
@makatiot · 1081 post欧博百家乐 亚星百家乐 欧博官网 亚星官网
@oubohh1 · 41 post亚星开户 欧博开户 亚星网址 欧博网址
@oubott2 · 61 post欧博代理|亚星代理|欧博百家乐|亚星百家乐
@oubovvi · 51 post环享娱乐-鼎信国际-非凡棋牌-永利国际-黄金轮娱乐
@Shuran77 · 71 post台灣外送茶🍀北部
@tw6697 · 851 post颜庄
@yanzhuang12 · 241 post欧博私网 亚星私网 亚星假网 欧博假网
@yaxingdx · 71 post皇冠百家乐 亚星百家乐 欧博百家乐 百家乐代理
@yaxingguanwang996 · 61 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.
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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“盯射-旗袍” (@jintianxiawuqushizhongxinliuda41), 42 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/jintianxiawuqushizhongxinliuda41.
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.