Telegram RegisterThe public register of Telegram
Telegram profile photo for BaikalOS [EN]

Supergroup

BaikalOS [EN]

@baikalos

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

2,183members

+110 since we began measuring on 7 August 2026

69 online right now

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

Register entry

Telegram ID-1001392240800
TypeSupergroup
Username@baikalos
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live14 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/baikalos

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 81% 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

2,0342,1832,108.57 August 2026 — 2,073 members8 August 2026 — 2,074 members11 August 2026 — 2,073 members14 August 2026 — 2,071 members17 August 2026 — 2,070 members20 August 2026 — 2,062 members24 August 2026 — 2,058 members27 August 2026 — 2,054 members30 August 2026 — 2,056 members7 September 2026 — 2,057 members12 September 2026 — 2,051 members15 September 2026 — 2,046 members20 September 2026 — 2,046 members27 September 2026 — 2,040 members5 October 2026 — 2,034 members11 October 2026 — 2,036 members17 October 2026 — 2,042 members20 October 2026 — 2,057 members23 October 2026 — 2,066 members25 October 2026 — 2,077 members28 October 2026 — 2,089 members31 October 2026 — 2,099 members2 November 2026 — 2,106 members6 November 2026 — 2,152 members9 November 2026 — 2,173 members14 November 2026 — 2,183 members7 August 202614 November 2026
26 measurements spanning 98 days, net +110. 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 2,012–2,205 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 26
Measured (UTC)MembersChange
14 Nov 2026, 03:092,183+10
9 Nov 2026, 12:182,173+21
6 Nov 2026, 03:162,152+46
2 Nov 2026, 23:562,106+7
31 Oct 2026, 10:272,099+10
28 Oct 2026, 14:142,089+12
25 Oct 2026, 19:452,077+11
23 Oct 2026, 00:462,066+9
20 Oct 2026, 04:402,057+15
17 Oct 2026, 15:162,042+6
11 Oct 2026, 12:592,036+2
5 Oct 2026, 10:572,034-6
27 Sept 2026, 03:172,040-6
20 Sept 2026, 15:072,046no change
15 Sept 2026, 19:582,046-5
12 Sept 2026, 06:012,051-6
7 Sept 2026, 19:422,057+1
30 Aug 2026, 12:542,056+2
27 Aug 2026, 19:032,054-4
24 Aug 2026, 18:142,058first 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“BaikalOS [EN]” (@baikalos), 2,183 members as measured 14 November 2026. Telegram Register, tgregister.com/channel/baikalos.

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.