🐙GIT @Githublib @GitTools @ru_gitlab

Channel
Python в Telegram
@itpython
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
17subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001636233671 |
|---|---|
| Type | Channel |
| Username | @itpython |
| Description | Чаты и каналы посвященные python и около него. |
| Created | Between 1 December 2021 and 9 August 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/itpython |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 20:46 | 17 | no change |
| 7 Aug 2026, 17:44 | 17 | first reading |
Engagement
20 posts held, back to 9 August 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
🍆Redis/Kafka/Celery @proKafka
🔍Elastic @elasticsearch_ru
💾ML и нейронка @neurohive @ai_machinelearning_big_data @artificialintelligencedl @datascienceiot @neuro_channel @machinee_learning @machinelearning_jobs @machinelearning_ru @machinelearning_rus @machinelearningtest @neural
🪒Parsing/scraping @scrapy_python @selenium_python
🔀Алгоритмы @structuredata
🔎Osint @cybdetective @data1eaks @gebutcher @grablab_osint_ru @mechtaparanoika1 @netstalkerscom @osint_club_channel @osint_info @osintby @pulsechanel @quick_osint боты: @autoteka_bot @deputatdumy_bot @emailphonebot @gemane440172985108bot @get_contact_bot @getcont_bot @getcontact_officialbot @getfb_bot @hdhdhdhdhdhdhdhdhd_bot @leakedinfobot @maigret_osint_bot @neberitrubku_bot @neberitrubkubot @nomer_org_bot @nomeror…
🔬Тестирование и QA @testerlib @typical_qa @QA_House Работа: @job_qa @qa_ru @qa_resumes @qa_bad_company @qa_jobs @qa_siberia
👨🏻🔧DevOps @devopsslib @devops_ru @devops_deflope @devo_pes @ru_devops работа: @devops_jobs
🐳Docker @ru_docker @docker_ru
📌Хостинг и облака @heroku_ru @pro_hosting
🖥pyQT @ru_pyqt @qt_chat
Showing the 12 most recent of 20 posts we hold for @itpython. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@aiogram_ru · 2,1991 postCyber Detective
@cybdetective · 26,7151 postDATABASE DESIGN
@database_design · 1,3561 postБазы данных. Книги по программированию
@dbbooks · 16,6781 postDevOps для ДевоПсов
@devo_pes · 3,2181 postDjango Unleashed Framework
@django_prog · 1,3011 postRemocate: релокация, удалёнка, работа и вакансии
@evacuatejobs · 134,4801 postGitHub Сообщество
@Githublib · 8,3871 postGroup moved to @tgscan_support_ru
@grablab_osint_ru · 1,9761 postMachinelearning tests
@Machinelearningtest · 6621 postMechtaParanoika
@MechtaParanoika1 · 1,4461 postНейроканал
@neuro_channel · 11,1111 postOSINT CLUB
@osint_club_channel · 34,6341 postPARSING
@proxy4parsing · 5571 postProxy Bar
@proxy_bar · 21,1981 postPulSe
@Pulsechanel · 19,8631 postPython Jobs
@python_djangojobs · 14,5411 postRelocationDEV by GeeckoMove
@relocationdev · 23,7251 postSenior SQL Developer
@seniorsql · 14,4251 postSQL и БД Learning
@sql_and_db_learning · 141 postSQLpedia | Базы данных
@sql_wiki · 5,9981 postData Science. SQL hub
@sqlhub · 35,8731 postData Science: Алгоритмы и Структуры данных
@structuredata · 7,7371 postТипичный QA
@typical_qa · 2,1901 post
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 24
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 24
- vacant every time we have ever looked
@itpython named 24 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Python в Telegram” (@itpython), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/itpython.
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.