Telegram RegisterThe public register of Telegram
Telegram profile photo for AlitechBlog

Supergroup

AlitechBlog

@AlitechBlog

Has discussion group

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

1,961members

-102 since we began measuring on 7 August 2026

48 online right now

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

Register entry

Telegram ID-1001323482683
TypeSupergroup
Username@AlitechBlog
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live16 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/AlitechBlog

Topic

Technology — 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 100% 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,9612,0832,0227 August 2026 — 2,063 members8 August 2026 — 2,061 members11 August 2026 — 2,062 members15 August 2026 — 2,059 members17 August 2026 — 2,055 members20 August 2026 — 2,047 members24 August 2026 — 2,065 members27 August 2026 — 2,064 members30 August 2026 — 2,068 members3 September 2026 — 2,083 members8 September 2026 — 2,069 members12 September 2026 — 2,061 members16 September 2026 — 2,058 members20 September 2026 — 2,058 members1 October 2026 — 2,033 members8 October 2026 — 2,023 members13 October 2026 — 2,017 members17 October 2026 — 2,014 members20 October 2026 — 2,012 members23 October 2026 — 2,006 members27 October 2026 — 1,998 members29 October 2026 — 1,993 members1 November 2026 — 1,992 members4 November 2026 — 1,987 members7 November 2026 — 1,977 members12 November 2026 — 1,970 members16 November 2026 — 1,961 members7 August 202616 November 2026
27 measurements spanning 101 days, net -102. 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,943–2,101 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 27
Measured (UTC)MembersChange
16 Nov 2026, 22:201,961-9
12 Nov 2026, 00:081,970-7
7 Nov 2026, 20:461,977-10
4 Nov 2026, 13:441,987-5
1 Nov 2026, 17:201,992-1
29 Oct 2026, 17:221,993-5
27 Oct 2026, 00:201,998-8
23 Oct 2026, 20:162,006-6
20 Oct 2026, 11:192,012-2
17 Oct 2026, 04:182,014-3
13 Oct 2026, 21:192,017-6
8 Oct 2026, 06:582,023-10
1 Oct 2026, 11:572,033-25
20 Sept 2026, 02:322,058no change
16 Sept 2026, 14:592,058-3
12 Sept 2026, 15:582,061-8
8 Sept 2026, 23:382,069-14
3 Sept 2026, 10:262,083+15
30 Aug 2026, 22:032,068+4
27 Aug 2026, 22:482,064first 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“AlitechBlog” (@AlitechBlog), 1,961 members as measured 16 November 2026. Telegram Register, tgregister.com/channel/AlitechBlog.

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.