Telegram RegisterThe public register of Telegram
Telegram profile photo for 收菜

Channel

收菜

@hhtxxcc0001

Has discussion group

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

2,110subscribers

+552 since we began measuring on 27 September 2026

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

Register entry

Telegram ID-1002295912587
TypeChannel
Username@hhtxxcc0001
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live16 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/hhtxxcc0001

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 15 October 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

1,5582,1101,83427 September 2026 — 1,558 subscribers28 September 2026 — 1,558 subscribers4 October 2026 — 1,655 subscribers11 October 2026 — 1,712 subscribers15 October 2026 — 1,728 subscribers18 October 2026 — 1,770 subscribers20 October 2026 — 1,793 subscribers23 October 2026 — 1,823 subscribers26 October 2026 — 1,842 subscribers29 October 2026 — 1,887 subscribers1 November 2026 — 1,951 subscribers4 November 2026 — 1,986 subscribers7 November 2026 — 2,025 subscribers10 November 2026 — 2,067 subscribers16 November 2026 — 2,110 subscribers27 September 202616 November 2026
15 measurements spanning 49 days, net +552. 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,475–2,193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 01:462,110+43
10 Nov 2026, 16:152,067+42
7 Nov 2026, 13:092,025+39
4 Nov 2026, 11:501,986+35
1 Nov 2026, 21:291,951+64
29 Oct 2026, 10:451,887+45
26 Oct 2026, 02:411,842+19
23 Oct 2026, 12:541,823+30
20 Oct 2026, 18:551,793+23
18 Oct 2026, 02:291,770+42
15 Oct 2026, 03:011,728+16
11 Oct 2026, 16:161,712+57
4 Oct 2026, 21:391,655+97
28 Sept 2026, 00:021,558no change
27 Sept 2026, 23:471,558first 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

Republished by

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

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

“收菜” (@hhtxxcc0001), 2,110 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/hhtxxcc0001.

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.