Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州全区配送

Channel

广州全区配送

@shfrdsg

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

4subscribers

-2 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-1001985220815
TypeChannel
Username@shfrdsg
CreatedBetween 1 April 2023 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live9 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/shfrdsg

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

46521 August 2026 — 6 subscribers22 August 2026 — 6 subscribers14 September 2026 — 5 subscribers9 October 2026 — 4 subscribers21 August 20269 October 2026
4 measurements spanning 49 days, net -2. 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 11:564-1
14 Sept 2026, 12:425-1
22 Aug 2026, 12:186no change
21 Aug 2026, 23:026first reading

Engagement

6 posts held, back to 26 February 2024 — 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
19s
Average length
6s

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:36 UTC45 viewsread 21 August 2026
Photo

电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566

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

172-05-D 圈外❤️人一个客都不认识💕 ✨身高172 D 05年 体重100斤 新疆女孩✨ ✨真实大学生大二在读 ✨不抽烟 无不良嗜好✨ ✨零整容 真🐻不风尘 有耐心前凸后翘 ✨性格超好 初恋般的感觉 待客如男友 ✨可69 配合度高 可🏚️可外 电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566

16 Jun 2025, 17:32 UTC28 viewsread 21 August 2026
Photo

07 年 刚满18岁 🉑🐍蚊 69 丝袜 制服 双飞 •Height身高/170 •Weight体重/90斤 •Bust胸围/c · 少量毛 超级紧 水多多 • 情趣丝袜 上下粉嫩 刚破处 • 听话乖巧 性格温柔 安静聆听哥哥的话语 • 梦想是做幸福的小猫 • 让你感受从未体验过的紧致配合度100 电报客服: @WE19087 QQ客服:3540605506 微信客服: sghjh566

26 Feb 2024, 17:51 UTC112 viewsread 21 August 2026
Photo

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

26 Feb 2024, 17:50 UTC108 viewsread 21 August 2026
Photo

广州花都 工作室外出 微信扫码选人预约,每天后台自动更新 电报客服: @WE19087 QQ客服:3540605506 微信客服: zxc178568

26 Feb 2024, 17:50 UTC86 viewsread 21 August 2026
Photo

广州天河白云越秀区特服 后花 sm 无套 处 工作室 外出 微信扫码选人预约,每天后台自动更新 电报客服: @WE19087 QQ客服:3540605506 微信客服: zxc178568

Showing the 6 most recent of 6 posts we hold for @shfrdsg. 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 9 October 2026 — this entry's latest reading, not the date you are reading this.

“广州全区配送” (@shfrdsg), 4 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/shfrdsg.

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.