Telegram RegisterThe public register of Telegram
Telegram profile photo for БЕГ В УЗБЕКИСТАНЕ / RUN UZBEKISTAN

Supergroup

БЕГ В УЗБЕКИСТАНЕ / RUN UZBEKISTAN

@runcht

Has discussion group

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

2,602members

+40 since we began measuring on 6 August 2026

981 online right now

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

Register entry

Telegram ID-1001141260147
TypeSupergroup
Username@runcht
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live6 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/runcht

Topic

Sports — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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,5522,6252,588.56 August 2026 — 2,562 members6 August 2026 — 2,561 members10 August 2026 — 2,554 members12 August 2026 — 2,552 members16 August 2026 — 2,555 members19 August 2026 — 2,560 members22 August 2026 — 2,577 members25 August 2026 — 2,576 members28 August 2026 — 2,572 members31 August 2026 — 2,578 members5 September 2026 — 2,575 members10 September 2026 — 2,605 members14 September 2026 — 2,603 members14 September 2026 — 2,603 members18 September 2026 — 2,609 members29 September 2026 — 2,616 members6 October 2026 — 2,625 members12 October 2026 — 2,621 members15 October 2026 — 2,611 members18 October 2026 — 2,614 members21 October 2026 — 2,616 members24 October 2026 — 2,613 members28 October 2026 — 2,616 members31 October 2026 — 2,615 members2 November 2026 — 2,607 members6 November 2026 — 2,602 members2,6026 August 20266 November 2026
26 measurements spanning 92 days, net +40. 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,541–2,636 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 26
Measured (UTC)MembersChange
6 Nov 2026, 05:182,602-5
2 Nov 2026, 19:372,607-8
31 Oct 2026, 03:492,615-1
28 Oct 2026, 05:292,616+3
24 Oct 2026, 23:272,613-3
21 Oct 2026, 19:092,616+2
18 Oct 2026, 11:452,614+3
15 Oct 2026, 17:012,611-10
12 Oct 2026, 14:472,621-4
6 Oct 2026, 02:402,625+9
29 Sept 2026, 01:422,616+7
18 Sept 2026, 21:162,609+6
14 Sept 2026, 22:062,603no change
14 Sept 2026, 03:362,603-2
10 Sept 2026, 04:212,605+30
5 Sept 2026, 02:382,575-3
31 Aug 2026, 22:082,578+6
28 Aug 2026, 18:032,572-4
25 Aug 2026, 13:222,576-1
22 Aug 2026, 21:192,577first 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“БЕГ В УЗБЕКИСТАНЕ / RUN UZBEKISTAN” (@runcht), 2,602 members as measured 6 November 2026. Telegram Register, tgregister.com/channel/runcht.

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.