Telegram RegisterThe public register of Telegram
Telegram profile photo for 【稻香】邮箱和日志扫号教学频道

Channel

【稻香】邮箱和日志扫号教学频道

@dx8632

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

1,684subscribers

-187 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-1003099843314
TypeChannel
Username@dx8632
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live31 October 2026
Measurements held23
Confirmed unchanged1 time, most recently 31 October 2026
On Telegramt.me/dx8632

Topic

Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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,6842,0841,8847 August 2026 — 1,871 subscribers8 August 2026 — 1,883 subscribers11 August 2026 — 1,908 subscribers14 August 2026 — 1,946 subscribers17 August 2026 — 1,975 subscribers20 August 2026 — 1,997 subscribers24 August 2026 — 2,031 subscribers27 August 2026 — 2,046 subscribers30 August 2026 — 2,061 subscribers3 September 2026 — 2,084 subscribers8 September 2026 — 2,076 subscribers12 September 2026 — 2,052 subscribers16 September 2026 — 2,031 subscribers20 September 2026 — 2,031 subscribers2 October 2026 — 1,840 subscribers8 October 2026 — 1,805 subscribers13 October 2026 — 1,794 subscribers16 October 2026 — 1,776 subscribers19 October 2026 — 1,757 subscribers22 October 2026 — 1,742 subscribers25 October 2026 — 1,720 subscribers28 October 2026 — 1,703 subscribers31 October 2026 — 1,684 subscribers7 August 202631 October 2026
23 measurements spanning 85 days, net -187. 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,624–2,144 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
31 Oct 2026, 13:551,684-19
28 Oct 2026, 11:271,703-17
25 Oct 2026, 18:171,720-22
22 Oct 2026, 18:381,742-15
19 Oct 2026, 14:401,757-19
16 Oct 2026, 19:191,776-18
13 Oct 2026, 21:281,794-11
8 Oct 2026, 14:561,805-35
2 Oct 2026, 12:141,840-191
20 Sept 2026, 15:482,031no change
16 Sept 2026, 11:382,031-21
12 Sept 2026, 20:392,052-24
8 Sept 2026, 12:192,076-8
3 Sept 2026, 01:242,084+23
30 Aug 2026, 23:042,061+15
27 Aug 2026, 13:182,046+15
24 Aug 2026, 06:122,031+34
20 Aug 2026, 19:151,997+22
17 Aug 2026, 22:131,975+29
14 Aug 2026, 19:461,946first 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.

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

“【稻香】邮箱和日志扫号教学频道” (@dx8632), 1,684 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/dx8632.

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.