Telegram RegisterThe public register of Telegram
Telegram profile photo for 元朗睇唔到請加@yuenlong1314

Channel

元朗睇唔到請加@yuenlong1314

@annashen555

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,685subscribers

+37 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001550481042
TypeChannel
Username@annashen555
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live11 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/annashen555

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 25 September 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

1,6481,6851,666.57 August 2026 — 1,648 subscribers10 August 2026 — 1,653 subscribers13 August 2026 — 1,654 subscribers16 August 2026 — 1,655 subscribers19 August 2026 — 1,658 subscribers22 August 2026 — 1,665 subscribers26 August 2026 — 1,668 subscribers29 August 2026 — 1,669 subscribers31 August 2026 — 1,672 subscribers4 September 2026 — 1,674 subscribers9 September 2026 — 1,670 subscribers13 September 2026 — 1,667 subscribers18 September 2026 — 1,664 subscribers25 September 2026 — 1,664 subscribers27 September 2026 — 1,669 subscribers5 October 2026 — 1,676 subscribers11 October 2026 — 1,685 subscribers7 August 202611 October 2026
17 measurements spanning 65 days, net +37. 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 1,642–1,691 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 14:381,685+9
5 Oct 2026, 11:561,676+7
27 Sept 2026, 11:211,669+5
25 Sept 2026, 02:421,664no change
18 Sept 2026, 09:551,664-3
13 Sept 2026, 17:581,667-3
9 Sept 2026, 18:191,670-4
4 Sept 2026, 07:381,674+2
31 Aug 2026, 20:041,672+3
29 Aug 2026, 03:531,669+1
26 Aug 2026, 01:271,668+3
22 Aug 2026, 19:451,665+7
19 Aug 2026, 11:061,658+3
16 Aug 2026, 17:461,655+1
13 Aug 2026, 05:051,654+1
10 Aug 2026, 14:311,653+5
7 Aug 2026, 11:011,648first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

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.

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

“元朗睇唔到請加@yuenlong1314” (@annashen555), 1,685 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/annashen555.

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.