Channel
@runello_rus_python
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
9,947subscribers
+408 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001582627575 |
|---|---|
| Type | Channel |
| Username | @runello_rus_python |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/runello_rus_python |
Job listings — 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 11 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 11:38 | 9,947 | +12 |
| 2 Sept 2026, 07:04 | 9,935 | +101 |
| 30 Aug 2026, 13:47 | 9,834 | +55 |
| 27 Aug 2026, 20:53 | 9,779 | +118 |
| 24 Aug 2026, 17:53 | 9,661 | +2 |
| 21 Aug 2026, 05:18 | 9,659 | +25 |
| 17 Aug 2026, 19:36 | 9,634 | +38 |
| 14 Aug 2026, 11:36 | 9,596 | +43 |
| 11 Aug 2026, 07:48 | 9,553 | +1 |
| 7 Aug 2026, 21:56 | 9,552 | +13 |
| 7 Aug 2026, 05:31 | 9,539 | first reading |
67 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 34 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 67 (29 July 2026 – 29 August 2026) |
| Views total | 17,944 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 05:12 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Python Developer Грейд: Middle Стек: Python, Git, FastAPI, Litestar, asyncio, PostgreSQL, SQLAlchemy, Kafka Разработка и поддержка backend-сервисов на Python, проектирование архитектуры, работа с API, CI/CD, PostgreSQL, брокерами сообщений и очередями. Откликнуться через Runello-бот ↓ #python #middle #remote #global
Tech Lead Python (GigaChat) Грейд: Lead Стек: Python, распределённые системы, высоконагруженные сервисы, алгоритмы поиска, структуры данных, Linux, контейнеры, Kubernetes Ищем руководителя в команду поисковых технологий для AI-систем. Строим общий поисковый слой для продуктов на основе языковых моделей. Задача: сделать так, чтобы AI-системы могли быстро находить нужную… Откликнуться через Runello-бот ↓ #python #l…
Стажер-разработчик (Python) Грейд: Intern Стек: Python, FastAPI, aiohttp, Flask, REST API, Asynchronous programming, Event-driven architecture, Microservices Мы создаём инновационную систему агентов позволяющих облегчить процесс переводов для физических лиц. Наша цель — разработать систему, способную самостоятельно помогать и решать вопросы клиентов без че… Откликнуться через Runello-бот ↓ #python #intern #hybrid
💼 ХВАТИТ ИСКАТЬ РАБОТУ — ПУСТЬ ОНА НАЙДЁТ ТЕБЯ! Мы собрали папку-сокровищницу по теме КАРЬЕРА | ФРИЛАНС | ВАКАНСИИ 🚀 Внутри — только проверенные каналы, где: —⚡️ Свежие вакансии каждый день — офис, удалёнка, подработка —💸 Фриланс без посредников — заказы, биржи, лайфхаки по ценнику —📈 Карьерный рост — как просить повышение и получать его — 🧠 Советы HR-инсайдеров— что на самом деле смотрят в резюме — 🎯 Собеседовани…
Эксперт отдела обеспечения безопасности объектов критической информационной инфраструктуры Стек: Python, Pandas, NumPy, SQLAlchemy, OpenPyXL, Django, Flask, RESTful API Отдел обеспечения безопасности объектов критической информационной инфраструктуры в поисках эксперта. Вам предстоит автоматизация деятельности, аудит, работа с законодательством в сфере КИИ (ФЗ-187), … Откликнуться через Runello-бот ↓ #python #off…
Python-разработчик Грейд: Middle/Senior Стек: Python, Git, SOLID, ООП, LLM, Docker, OpenShift, Kubernetes Сбер Банк — крупнейший российский финансовый конгломерат, предоставляющий широкий спектр банковских услуг для частных лиц, малого бизнеса и корпоративных клиентов. Откликнуться через Runello-бот ↓ #python #middle #hybrid
Trainee/Python Developer Грейд: Trainee Стек: Python, Django, Flask, FastAPI, OOP, Clean Code, DRY, KISS Арелаг консалт — это рекрутинговое агентство, специализирующееся на подборе IT-специалистов для технологических компаний. Откликнуться через Runello-бот ↓ #python #trainee #remote #global
Middle Python-разработчик Грейд: Middle Стек: Python, PostgreSQL, HTTP, Message Queues, 1C Разработка страховых продуктов на вебе. Основное направление — ОГПО ВТС: обязательное страхование, которое раньше жило в 1С и переносится на собственный бэкенд. Плюс внутренние продукты компании: каби… Откликнуться через Runello-бот ↓ #python #middle #office
Вайбкодер / Vibe coder Стек: Python, API, VS Code, OpenRouter, Cursor, OpenAI, Claude, n8n KiteGroup - IT-команда на рынке мобильных приложений и перфоманс-маркетинга. Мы ищем Вайбкодера для интеграции AI-решений, автоматизации процессов и ускорения разработки проектов. Откликнуться через Runello-бот ↓ #python #remote #global
Trainee/Python Developer Грейд: Trainee Стек: Python, Django, Flask, FastAPI, OOP, Clean Code, DRY, KISS Арелаг консалт — это рекрутинговое агентство, специализирующееся на подборе IT-специалистов для технологических компаний. Откликнуться через Runello-бот ↓ #python #trainee #remote #global
Backend-разработчик Грейд: Middle Стек: Python, Django, Django REST Framework, PostgreSQL, Aiogram, aiohttp, Celery, Pytest Мы — Priqol Labs. Мы делаем собственные продукты, лутаем раунды инвестиций. У нас есть финтех-проект, который нацелен на автоматизацию процессов обмена фиата в криптовалюту и наоборот. Откликнуться через Runello-бот ↓ #python #middle #remote #global
Пока вы листаете сайты с вакансиями, хорошие предложения уже разбирают в телеграмм Собрали папку каналов, где каждый день выходят новые вакансии. Для тех, кто ищет постоянную работу, подработку, удалёнку или интересные проекты. Добавили всё в одну папку, чтобы не искать каналы по одному. Добавить себе ➡️ https://t.me/addlist/Ige-7KTVUUhiODhi 🔄 Ссылка будет открыта ещё 24 часа
Showing the 12 most recent of 67 posts we hold for @runello_rus_python. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Python Job Offers” (@runello_rus_python), 9,947 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/runello_rus_python.
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.