Telegram RegisterThe public register of Telegram
Telegram profile photo for Python CDMX

Supergroup

Python CDMX

@PythonCDMX

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

1,572members

+46 since we began measuring on 7 August 2026

64 online right now

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

Register entry

Telegram ID-1001151090136
TypeSupergroup
Username@PythonCDMX
CreatedBetween 1 August 2018 and 30 April 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live19 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/PythonCDMX

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 27 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,5201,5931,556.57 August 2026 — 1,526 members8 August 2026 — 1,525 members11 August 2026 — 1,528 members15 August 2026 — 1,532 members18 August 2026 — 1,533 members21 August 2026 — 1,535 members25 August 2026 — 1,530 members27 August 2026 — 1,529 members30 August 2026 — 1,525 members7 September 2026 — 1,520 members12 September 2026 — 1,528 members15 September 2026 — 1,531 members27 September 2026 — 1,531 members29 September 2026 — 1,563 members6 October 2026 — 1,561 members12 October 2026 — 1,563 members15 October 2026 — 1,579 members18 October 2026 — 1,583 members22 October 2026 — 1,584 members25 October 2026 — 1,586 members31 October 2026 — 1,593 members2 November 2026 — 1,585 members5 November 2026 — 1,586 members9 November 2026 — 1,584 members14 November 2026 — 1,574 members19 November 2026 — 1,572 members1,5727 August 202619 November 2026
26 measurements spanning 104 days, net +46. 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,509–1,604 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 26
Measured (UTC)MembersChange
19 Nov 2026, 13:371,572-2
14 Nov 2026, 14:171,574-10
9 Nov 2026, 09:411,584-2
5 Nov 2026, 15:191,586+1
2 Nov 2026, 22:261,585-8
31 Oct 2026, 06:501,593+7
25 Oct 2026, 11:061,586+2
22 Oct 2026, 08:391,584+1
18 Oct 2026, 21:281,583+4
15 Oct 2026, 15:541,579+16
12 Oct 2026, 13:101,563+2
6 Oct 2026, 03:191,561-2
29 Sept 2026, 05:001,563+32
27 Sept 2026, 16:141,531no change
15 Sept 2026, 16:571,531+3
12 Sept 2026, 01:191,528+8
7 Sept 2026, 22:191,520-5
30 Aug 2026, 12:251,525-4
27 Aug 2026, 22:491,529-1
25 Aug 2026, 02:181,530first 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 19 November 2026 — this entry's latest reading, not the date you are reading this.

“Python CDMX” (@PythonCDMX), 1,572 members as measured 19 November 2026. Telegram Register, tgregister.com/channel/PythonCDMX.

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.