За ИЮЛЬ я заработал +266.000 рублей на техничке Или обычный месячный доход технического специалиста на фрилансе. Не путайте с IT-направлением, здесь все в разы проще: без сложных терминов, нудной теории и кодов программирования. В чем суть: создавать чат-ботов в специальном конструкторе по готовой инструкции, где за несколько часов можно легко делать 3.000 - 4.000 рублей чистыми. В первый месяц работы, новички зар…

Channel
Python jobs | Вакансии в IT
@Python_Jbs
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7,136subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002010650911 |
|---|---|
| Type | Channel |
| Username | @Python_Jbs |
| Description | Вакансии для Python разработчиков. • Купить рекламу: https://t.me/+iVfQ8Iyk8Kg0ZTE6 • Разместить пост - @IT_JobsBot • Админ - @Art_666999 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/Python_Jbs |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 22:31 | 7,136 | -14 |
| 7 Aug 2026, 14:45 | 7,150 | no change |
| 7 Aug 2026, 14:39 | 7,150 | first reading |
Engagement
23 posts held, back to 23 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 11 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.99%
- avg views ÷ 7,136 subscribers
- Avg views / post
- 213
- 23 posts measured
- Reaction rate
- 0.53%
- reactions ÷ views · ER floor
- Posts in window
- 23
- of 23 held
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. It is computed over the 6 of 23 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 23 (23 July 2026 – 11 August 2026) |
| Views total | 4,909 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:29 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.
What this channel posts
- Photos
- 36
- Links
- 745
Lifetime counters from Telegram’s own channel header, read 12 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.
Reaction mix
8 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 75.0% | |
| 👎 | 1 | 12.5% | |
| 🔥 | 1 | 12.5% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 23 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 23 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Аккаунты под рекламу. FB / TikTok / Google / iOS. Фарм, агентские, с историей, BM ready. Рекламные кабинеты, developer-аккаунты, agency доступ Переходи @roiaccount акки, аки, аккаунты, аккаунт, farm, фарм, фармы, аккаунт фарм, developer console google, developer ios, tiktok ads accounts, ads accounts, trusted accounts, bm ready, business ready, агентские аккаунты, agency accounts, fb акки, fb аккаунты, фб акки, фб …
#вакансия Название компании: Филиал ФКУ «Налог-Сервис» ФНС России в г. Москве Вакансия: Junior Backend разработчик (Node.js) Формат работы: офис (гибрид после испытательного) Город и адрес офиса: Москва, Походный проезд, д. 3, стр. 1. Ближайшие станции метро: Волоколамская, Сходненская, Трикотажная. Занятость: полная Зарплатная вилка: от 80 000 до 100 000 ₽ на руки Контакты: тг @mniimaya Описание вакансии: Ищем Junio…
Вы фрилансер и не знаете где искать заказы? Бот найдет их для вас 💪 Заказы на: дизайн, веб-дизайн, таргет, smm, копирайт, веб-разработка, seo, инфографика карточек WB, вакансии для менеджеров WB и многое другое. • Бот с заказами для фрилансеров • Бот с заказами по работе с маркетплейсами Активируйте бесплатную подписку и начните получать заявки от заказчиков уже сегодня 🔥
Senior Frontend Developer (React) Компания: Tango Зарплата: $3,000–5,000 (net), обсуждается по результатам интервью. Ищем Senior Frontend Developer в продуктовую команду Tango — одного из крупнейших международных сервисов для live-streaming и социальных коммуникаций с миллионами пользователей по всему миру. ### Что предстоит делать * Разрабатывать и развивать высоконагруженные веб-приложения на React. * Работать в…
#вакансия#PythonDeveloper#Backend#SeniorPython#Scraping Backend Developer (Python / Scraping Product) Компания: CyberYozh Формат: удаленно Занятость: полная Зарплата: от $4,000 до $5,500+ (на руки, в зависимости от глубины экспертизы). Контакты: https://t.me/vi_kostyunina Привет!👋 Мы международная, быстрорастущая экосистема компаний в сфере кибербезопасности, образования и технологий. Наши основные проекты: https://…
Hi, I am a Full-Stack Developer with 5.5+ years of experience building secure, scalable, and high-performance web applications. My expertise includes Laravel, Node.js, React.js, FastAPI, Angular, MySQL, MongoDB, REST APIs, and AI-powered integrations. I have hands-on experience with AWS services, including Lambda, EC2, S3, Cognito, and API Gateway, along with CI/CD deployment pipelines using GitHub Actions and other…
❤1
We're Hiring: Freelance React Native Developer (Remote) Compensation: ₹40,000/month + ₹2,000/month AI Allowance We're looking for a passionate React Native Developer to join our growing team and build high-quality mobile applications for international clients. Responsibilities: Develop high-quality cross-platform mobile applications using React Native Integrate REST APIs and third-party services Optimize applicati…
🎰 Looking for a reliable partner to publish and promote your iGaming app? I help mobile app developers launch and scale their Android projects. My services include: ✅ Google Play app publishing (in compliance with Google Play policies) ✅ Google Ads campaign setup and management ✅ Meta Ads (Facebook & Instagram) setup and optimization ✅ AdMob integration for eligible apps ✅ ASO (App Store Optimization) to improve a…
📌 HUNTTECH ВАКАНСИЯ | Senior Аналитик ИБ ID запроса: 13 868 О проекте: Проект по ИБ. 🗓 Срок привлечения: до конца года. Продолжительность проекта: от 6 месяцев до года. 📍 Формат работы: Удаленно. Локация: РФ. Гражданство: РФ. Часовой пояс: Москва (UTC+03:00, Europe/Moscow) ± 2. Part-time — 50%. 🤝 Форма сотрудничества: ГПХ или ИП. 💰 Вознаграждение: ГПХ — 1 400 руб./час на руки. ИП — 1 700 руб./час, налоги оплачи…
Senior Frontend Developer (React) Компания: Tango Локация: Limassol, Cyprus (релокация возможна) Формат: гибрид Зарплата: $3,000–5,000 (net), обсуждается по результатам интервью. Ищем Senior Frontend Developer в продуктовую команду Tango — одного из крупнейших международных сервисов для live-streaming и социальных коммуникаций с миллионами пользователей по всему миру. Что предстоит делать Разрабатывать и развивать…
❤1
#ищу #ios #swift #swiftui #parttime #remote #senior 👋 Всем привет! Ищу интересные part-time проекты (около **20 часов в неделю**). 💰 Ставка — 2000 ₽/час. ## Немного обо мне Senior iOS Developer с 7 годами коммерческого опыта. За карьеру успел поработать в крупном банке, бигтехе и продуктовом стартапе. Прошел путь от стажёра до инженера, который отвечает не только за разработку, но и за архитектуру решений, техн…
Showing the 12 most recent of 23 posts we hold for @Python_Jbs. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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
- 1
- 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
- 1
- vacant every time we have ever looked
@Python_Jbs named 1 handle 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 2 posts, 8 August 2026 – 9 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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Python jobs | Вакансии в IT” (@Python_Jbs), 7,136 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Python_Jbs.
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.