Telegram RegisterThe public register of Telegram
Telegram profile photo for 郑州中圈

Channel

郑州中圈

@zzzzzzz857

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

144subscribers

-7 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-1001371107942
TypeChannel
Username@zzzzzzz857
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/zzzzzzz857

Growth

144151147.56 August 2026 — 151 subscribers8 August 2026 — 151 subscribers23 August 2026 — 148 subscribers7 September 2026 — 146 subscribers15 September 2026 — 144 subscribers6 August 202615 September 2026
5 measurements spanning 39 days, net -7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 143–152 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 04:36144-2
7 Sept 2026, 01:38146-2
23 Aug 2026, 10:37148-3
8 Aug 2026, 19:45151no change
6 Aug 2026, 23:18151first reading

Engagement

17 posts held, back to 11 December 2022the 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 17 posts for this entry, the most recent from 14 April 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Apr 2023, 09:53 UTC≈3,240 viewsread 8 August 2026
Photo

大号被封,请联系备用号 QQ: 3572096324 有需要老板请联系 QQ群:810590086

14 Apr 2023, 09:06 UTC≈3,110 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

13 Apr 2023, 07:58 UTC≈2,630 viewsread 8 August 2026
Photo

开工,有需要老板请联系QQ:2580845479 QQ群:810590086

9 Apr 2023, 16:11 UTC≈2,320 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

1 Apr 2023, 12:31 UTC≈2,020 viewsread 8 August 2026
Photo

周末请提前预约,否则剩下的都是这种了。/笑哭

30 Mar 2023, 10:34 UTC≈1,780 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

25 Mar 2023, 09:42 UTC≈1,600 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

22 Mar 2023, 11:06 UTC≈1,460 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

18 Mar 2023, 06:36 UTC≈1,310 viewsread 8 August 2026
Photo

周六请提前预约,有需要老板请联系QQ:2580845479 QQ群:810590086

15 Mar 2023, 07:04 UTC≈1,230 viewsread 8 August 2026
Photo

🌸🌸🌸🌸🌸🌸 郑州楼凤频道 @zzzzzz888857 郑州中圈频道 @zzzzzzz857 长沙楼凤频道 @cccc85777 武汉楼凤频道 @xxzzz8577777 全国频道(私人订制) @aaaaa888777 北京频道 @cccc8857 上海频道 @ccccc85777 广州频道 @cccc857777 深圳频道 @ccccc8588 成都频道 @ccccc8577 价格区间: 楼凤:600起 包夜:2000起 中端:1500起 包夜:4000起 高端:3000起 包夜:8000起 即日起:新人外围预约 收取会费200¥ 第一次消费抵扣 会员终生有效! 客服电报:@keyue11 一: 真诚约会 约会流程 (请您仔细看下) 约不约没关系(可长期关注我) 二: 全国 一 二 三 线 大城市 省会 港澳台 部分海外 长期 都有最新资源

9 Mar 2023, 10:48 UTC537 viewsread 8 August 2026
Forwarded from @ccccc8577Photo

主营全国外围会所 有需要老板滴滴 非诚勿扰

Showing the 12 most recent of 17 posts we hold for @zzzzzzz857. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 7 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.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“郑州中圈” (@zzzzzzz857), 144 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zzzzzzz857.

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.