Telegram RegisterThe public register of Telegram
Telegram profile photo for YTsaurus Community Chat (RU)

Supergroup

YTsaurus Community Chat (RU)

@ytsaurus_ru

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

1,410members

+10 since we began measuring on 7 August 2026

631 online right now

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

Register entry

Telegram ID-1001597349761
TypeSupergroup
Username@ytsaurus_ru
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live18 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/ytsaurus_ru

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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,3951,4181,406.57 August 2026 — 1,400 members10 August 2026 — 1,395 members14 August 2026 — 1,396 members17 August 2026 — 1,397 members20 August 2026 — 1,405 members24 August 2026 — 1,403 members30 August 2026 — 1,399 members2 September 2026 — 1,407 members6 September 2026 — 1,409 members11 September 2026 — 1,412 members18 September 2026 — 1,413 members27 September 2026 — 1,414 members29 September 2026 — 1,414 members5 October 2026 — 1,416 members12 October 2026 — 1,417 members15 October 2026 — 1,418 members21 October 2026 — 1,414 members24 October 2026 — 1,417 members27 October 2026 — 1,414 members30 October 2026 — 1,412 members2 November 2026 — 1,413 members9 November 2026 — 1,412 members13 November 2026 — 1,405 members18 November 2026 — 1,410 members1,4107 August 202618 November 2026
24 measurements spanning 103 days, net +10. 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,392–1,421 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
18 Nov 2026, 13:161,410+5
13 Nov 2026, 01:071,405-7
9 Nov 2026, 01:061,412-1
2 Nov 2026, 10:301,413+1
30 Oct 2026, 07:371,412-2
27 Oct 2026, 09:291,414-3
24 Oct 2026, 12:471,417+3
21 Oct 2026, 17:161,414-4
15 Oct 2026, 10:161,418+1
12 Oct 2026, 01:161,417+1
5 Oct 2026, 09:171,416+2
29 Sept 2026, 17:281,414no change
27 Sept 2026, 12:011,414+1
18 Sept 2026, 06:591,413+1
11 Sept 2026, 06:011,412+3
6 Sept 2026, 18:371,409+2
2 Sept 2026, 09:451,407+8
30 Aug 2026, 08:241,399-4
24 Aug 2026, 04:131,403-2
20 Aug 2026, 04:441,405first 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 18 November 2026 — this entry's latest reading, not the date you are reading this.

“YTsaurus Community Chat (RU)” (@ytsaurus_ru), 1,410 members as measured 18 November 2026. Telegram Register, tgregister.com/channel/ytsaurus_ru.

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.