蓝色字体地区已开放 点击即可入群 津 🔗 天津市 冀 河北省 🔗 石家庄市 🔗 唐山市 🔗 邯郸市 🔗 保定市 🔗 沧州市 🔗 邢台市 🔗 廊坊市 🔗 承德市 🔗 秦皇岛市
Channel
津 . 冀 精品资源 新模式
@jjjpzy
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
-4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001813056304 |
|---|---|
| Type | Channel |
| Username | @jjjpzy |
| Created | 18 May 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 10 October 2026 |
| On Telegram | t.me/jjjpzy |
Topic
Local community — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 52% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 01:59 | 6 | -2 |
| 31 Aug 2026, 00:54 | 8 | -1 |
| 23 Aug 2026, 02:52 | 9 | -1 |
| 12 Aug 2026, 08:31 | 10 | no change |
| 8 Aug 2026, 21:31 | 10 | first reading |
Engagement
2 posts held, back to 18 May 2023 — 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 2 posts for this entry, the most recent from 18 May 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @jjjpzy. 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 25 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@anhuiziyuan · 731 post北京 品茶资源
@beijingwaiweiziyuan · 261 post长沙品茶资源
@changshaziyuan2 · 931 post成都 约炮资源
@chengduziyuan2 · 651 post杭州 宁波 约炮资源群
@fafg1231 · 701 post佛山 品茶资源
@foshanziyuan2 · 371 post成都市品茶资源群
@ggjk321 · 201 post广州约炮资源 ❤️
@gzypzy · 2021 post惠州市 品🍵资源
@hbbjjj12 · 591 post河南 品茶资源
@henanziyuan · 461 post河源品茶资源
@heyuanziyuan2 · 341 post海口市 品茶资源 楼凤 约炮 线下 外围
@hjnjg321 · 321 post湖北品茶资源
@hubeiziyuan · 391 post杭州 约炮 🍵 浙江🍵 台州🍵宁波🍵 瑞安🍵义乌🍵嘉善🍵湖州🍵约炮信息
@hzypzyxx · 1331 post梅州市 中山市 品🍵资源 外围 约炮 楼凤 线下
@jjbbh89 · 751 post南京 品茶 ✈️资源
@nanjingziyuan1 · 231 post三亚 品茶资源
@sanyaziyuan2 · 261 post武汉市 品🍵资源
@sdgdsgda · 391 post山东 品茶资源
@shandongziyuan2 · 1451 post山西 品茶资源
@shanxiziyuan · 681 post四川品茶资源
@sichuanyuepao · 421 post深圳 中山线下约炮资源
@szxxzy · 641 post天津 ✈️资源
@tianjingziyuan · 581 post珠海 约炮资源
@zhuhaiziyuan2 · 571 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 2
- vacant every time we have ever looked
@jjjpzy named 2 handles 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, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“津 . 冀 精品资源 新模式” (@jjjpzy), 6 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/jjjpzy.
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.