Channel
Build REST APIs with Flask and Python
@python3_flask
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,489subscribers
-74 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001329750727 |
|---|---|
| Type | Channel |
| Username | @python3_flask |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/python3_flask |
Topic
Education — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 07:17 | 4,489 | -5 |
| 9 Nov 2026, 02:54 | 4,494 | -1 |
| 5 Nov 2026, 14:49 | 4,495 | +1 |
| 2 Nov 2026, 17:17 | 4,494 | -1 |
| 30 Oct 2026, 15:18 | 4,495 | -9 |
| 27 Oct 2026, 12:39 | 4,504 | -4 |
| 24 Oct 2026, 09:38 | 4,508 | -3 |
| 21 Oct 2026, 03:40 | 4,511 | -5 |
| 17 Oct 2026, 19:19 | 4,516 | -7 |
| 11 Oct 2026, 09:37 | 4,523 | -5 |
| 5 Oct 2026, 06:17 | 4,528 | -10 |
| 26 Sept 2026, 21:39 | 4,538 | -14 |
| 18 Sept 2026, 04:58 | 4,552 | -1 |
| 13 Sept 2026, 15:54 | 4,553 | -3 |
| 10 Sept 2026, 01:36 | 4,556 | -7 |
| 7 Sept 2026, 19:42 | 4,563 | no change |
| 7 Sept 2026, 16:17 | 4,563 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@english_music_lyric · 22,231
Telegram ranks this channel #41 of 53 here — alongside 52 others — read 25 September 2026
@Master_Coding_Interview · 30,285
Telegram ranks this channel #42 of 60 here — alongside 59 others — read 7 September 2026
@AIjobz · 20,911
Telegram ranks this channel #70 of 81 here — alongside 80 others — read 25 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“Build REST APIs with Flask and Python” (@python3_flask), 4,489 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/python3_flask.
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.