Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳各区配送

Channel

深圳各区配送

@ag57536

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

7subscribers

-3 since we began measuring on 21 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001751644281
TypeChannel
Username@ag57536
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live1 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/ag57536

Topic

Adult — 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 78% 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

7108.521 August 2026 — 10 subscribers23 August 2026 — 10 subscribers8 September 2026 — 9 subscribers17 September 2026 — 8 subscribers1 October 2026 — 7 subscribers21 August 20261 October 2026
5 measurements spanning 41 days, net -3. 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 7–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 20:387-1
17 Sept 2026, 05:598-1
8 Sept 2026, 12:359-1
23 Aug 2026, 00:4210no change
21 Aug 2026, 23:0210first reading

Engagement

6 posts held, back to 21 November 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 6 posts for this entry, the most recent from 16 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
27s
Average length
9s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

16 Jun 2025, 17:28 UTC54 viewsread 21 August 2026
Photo

电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566 174 🦋兼职模特 骚欲天花板 •🌸年龄 03年 •🌸体重 48kg •🌸身高 174cm •🌸🐻 D➕ •🌸兴趣爱好:健身 游泳 羽毛球 •🌸身材高挑无赘肉 •马甲线 水蛇腰 •🌸敏感体质会娇喘 •主动配合榨汁机 •🌸性格超好无不良嗜好 🉑🐍🉑6️⃣9️⃣🉑🚗🉑✌🏻🉑🪂🉑3P🉑登记代开

16 Jun 2025, 17:25 UTC45 viewsread 21 August 2026
Photo

• 175cm.36 D身材比例完美 • 乘风破浪同款姐姐 最懂男人心 • 巨灯長蹆都给你 有前有后 又嗲又瘙 • 天然O整 知性大方气质名媛风 • Computer Science and Technology • 文科女,爱好/健身 旅行电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566

16 Jun 2025, 17:13 UTC34 viewsread 21 August 2026
Photo

深圳 180 C 03年 极品气质长腿御姐纯欲天花板车模兼职 电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566

26 Feb 2024, 18:04 UTC91 viewsread 21 August 2026
Photo

深圳各区特服 工作室外出均可 微信支付宝浏览器扫码选人预约,每天后台自动更新 电报客服: @WE19087 QQ客服:3540605506 微信客服: zxc178568

26 Feb 2024, 18:04 UTC88 viewsread 21 August 2026
Photo

深圳各区特服 工作室外出均可 微信支付宝浏览器扫码选人预约,每天后台自动更新 电报客服: @WE19087 QQ客服:3540605506 微信客服: zxc178568

21 Nov 2023, 21:26 UTC147 viewsread 21 August 2026
Photo

深圳各区特服 工作室外出 微信扫码选人预约,每天后台自动更新 电报客服: @WE19087 QQ客服:3540605506 微信客服: zxc178568

Showing the 6 most recent of 6 posts we hold for @ag57536. 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 1 registered channel — 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.

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

“深圳各区配送” (@ag57536), 7 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/ag57536.

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.