Telegram RegisterThe public register of Telegram
Telegram profile photo for 时光深圳大圈、广州大圈 全国资源

Channel

时光深圳大圈、广州大圈 全国资源

@szxc520

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

3,463subscribers

+2,323 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003405795234
TypeChannel
Username@szxc520
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/szxc520

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

6613,5722,116.510 August 2026 — 1,140 subscribers11 August 2026 — 1,116 subscribers14 August 2026 — 1,062 subscribers17 August 2026 — 987 subscribers24 August 2026 — 801 subscribers31 August 2026 — 661 subscribers10 September 2026 — 3,572 subscribers14 September 2026 — 3,525 subscribers18 September 2026 — 3,463 subscribers3,46310 August 202618 September 2026
9 measurements spanning 39 days, net +2,323. 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 224–4,009 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 14:393,463-62
14 Sept 2026, 12:393,525-47
10 Sept 2026, 21:193,572+2,911
31 Aug 2026, 19:36661-140
24 Aug 2026, 14:36801-186
17 Aug 2026, 18:05987-75
14 Aug 2026, 14:331,062-54
11 Aug 2026, 04:261,116-24
10 Aug 2026, 14:311,140first reading

Engagement

3 posts held, back to 10 August 2026the 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 3 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
25s
Average length
8s

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

10 Aug 2026, 12:00 UTC5 viewsread 10 August 2026
Photo

古驰✝️深圳 #心心 ✦ 07年🉑验 大一新生 ✦ 净高171 真粉🐻D+ 体重 52KG ✦ 天然0整 无纹身 无疤痕 弹力满满 ✦ 🍑臀 肉感小女友不喜瘦 青涩乖巧💞 平时上课需预约 只见高素质温柔的你🥰 #小纯 #南山

10 Aug 2026, 12:00 UTC6 viewsread 10 August 2026
Photo

古驰✝️深圳 #米朵 首次↓氵真实新面孔冷白皮 ^ O^承诺:超甜超纯超白超粉纯生活照 ♛你的乖巧女友 167D 06年 98斤 ❤️❤️喜欢圆脸的福音 ★韩系甜美☆天然无整 ⭐娃娃脸,完美身材 皮肤细滑白嫩 声音奶萌奶萌 🌸敏感体质易湿 外表娇羞 服务超好 🌸期待素质哥哥 🈶jk 丝袜 #小纯 #福田 #萝莉 #舌吻 #登记 #代开

10 Aug 2026, 12:00 UTC3 viewsread 10 August 2026
Photo

古驰✝️深圳 #小梦 05年纯情少萝,女大小甜妹 165cm 40kg D 盈盈一握小细腰 小巧玲珑清纯可爱通体雪白 上下粉嫩紧致多多双商高乖巧听话不催不事(好评选手看真实好评图) 听话配合,期待哥哥来调教,极大反差给你小女友般的体验 可69蛇纹 囿jk,丝袜qq #小纯 #福田 #侨乡

Showing the 3 most recent of 3 posts we hold for @szxc520. 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 2 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.

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

“时光深圳大圈、广州大圈 全国资源” (@szxc520), 3,463 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/szxc520.

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.