Telegram RegisterThe public register of Telegram
Telegram profile photo for Python сообщество (FastAPI)

Supergroup

Python сообщество (FastAPI)

@python_community_rus

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

4,681members

-180 since we began measuring on 7 August 2026

1,303 online right now

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

Register entry

Telegram ID-1001852919951
TypeSupergroup
Username@python_community_rus
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live4 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/python_community_rus

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 13 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

4,6814,8614,7717 August 2026 — 4,861 members8 August 2026 — 4,860 members11 August 2026 — 4,854 members14 August 2026 — 4,847 members17 August 2026 — 4,838 members24 August 2026 — 4,822 members30 August 2026 — 4,823 members1 September 2026 — 4,823 members2 September 2026 — 4,818 members7 September 2026 — 4,814 members11 September 2026 — 4,809 members15 September 2026 — 4,802 members26 September 2026 — 4,784 members5 October 2026 — 4,757 members11 October 2026 — 4,739 members15 October 2026 — 4,723 members17 October 2026 — 4,721 members21 October 2026 — 4,713 members23 October 2026 — 4,706 members27 October 2026 — 4,694 members29 October 2026 — 4,688 members1 November 2026 — 4,685 members4 November 2026 — 4,681 members7 August 20264 November 2026
23 measurements spanning 89 days, net -180. 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 4,654–4,888 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
4 Nov 2026, 11:194,681-4
1 Nov 2026, 15:384,685-3
29 Oct 2026, 18:574,688-6
27 Oct 2026, 04:274,694-12
23 Oct 2026, 20:514,706-7
21 Oct 2026, 06:494,713-8
17 Oct 2026, 22:384,721-2
15 Oct 2026, 03:284,723-16
11 Oct 2026, 19:394,739-18
5 Oct 2026, 06:014,757-27
26 Sept 2026, 16:404,784-18
15 Sept 2026, 17:374,802-7
11 Sept 2026, 18:174,809-5
7 Sept 2026, 05:354,814-4
2 Sept 2026, 20:384,818-5
1 Sept 2026, 23:354,823no change
30 Aug 2026, 22:384,823+1
24 Aug 2026, 17:274,822-16
17 Aug 2026, 19:494,838-9
14 Aug 2026, 09:284,847first 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“Python сообщество (FastAPI)” (@python_community_rus), 4,681 members as measured 4 November 2026. Telegram Register, tgregister.com/channel/python_community_rus.

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.