Channel
@python_0
On this record: Topic · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
3,243subscribers
-87 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001430334642 |
|---|---|
| Type | Channel |
| Username | @python_0 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/python_0 |
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 14 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 06:58 | 3,243 | -1 |
| 14 Sept 2026, 11:21 | 3,244 | -4 |
| 11 Sept 2026, 06:38 | 3,248 | -22 |
| 6 Sept 2026, 06:22 | 3,270 | -10 |
| 1 Sept 2026, 18:36 | 3,280 | -7 |
| 29 Aug 2026, 21:05 | 3,287 | -6 |
| 27 Aug 2026, 07:28 | 3,293 | -3 |
| 24 Aug 2026, 15:38 | 3,296 | -6 |
| 20 Aug 2026, 16:07 | 3,302 | -10 |
| 17 Aug 2026, 17:04 | 3,312 | -6 |
| 14 Aug 2026, 21:26 | 3,318 | -7 |
| 11 Aug 2026, 04:42 | 3,325 | -4 |
| 8 Aug 2026, 00:18 | 3,329 | -1 |
| 7 Aug 2026, 06:15 | 3,330 | first reading |
20 posts held, back to 1 August 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 3 pages of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
BCG INTERNAL REFERRAL OPPORTUNITY APPLY LINKS Apply all 3 roles ✅👇❤️ 🚀🔥Data Analyst Role 15 LPA https://lnkd.in/db4hmYuC 🚀🔥IT Software Engineer 20 LPA package https://lnkd.in/dYrweqpU 🚀🔥Software Engineer Planning Team 12 LPA package https://lnkd.in/dEGE9yPh 👉Telegram Link: https://t.me/nxthiring Share With Your Fresher Friends ❤️
🚀🔥 BCG Internal Referral Opportunity apply link 🎓 𝗘𝗹𝗶𝗴𝗶𝗯𝗶𝘁𝘆: all batches Freshers and 3year Exp candidates Eligible ✅They accept Freshers also just update Resume 💼 𝗥𝗼𝗹𝗲: analyst Role 💰 𝗦𝗮𝗹𝗮𝗿𝘆: ₹5 LPA Expected 👉 Apply Link : https://tinyurl.com/3psnhfa8 𝗦𝗵𝗮𝗿𝗲 𝗪𝗶𝘁𝗵 𝗬𝗼𝘂𝗿 𝗙𝗿𝗶𝗲𝗻𝗱𝘀 🧡
Company: Athenahealth Role: Operations Analyst CTC: upto 20LPA (expected) Location: Chennai Apply Link: https://tinyurl.com/3ufv8rnn Share With Your Friends
Company: Athenahealth Role: Marketing Automation & Ai Manager Qualifications: Bachelor’s/ Master’s Degree Experience: Freshers/experience CTC: upto 15LPA (expected) Apply Link: https://tinyurl.com/yaz6x57s Share With Your Friends
Company: Aramco Role: Maintenance Engineering Specialist Link: https://tinyurl.com/3wwu86ds Company: Qualcomm Role: Cpu Software Engineer Link: https://tinyurl.com/bd32sm2m Company: Qualcomm Role: Design - Staff Engineer Link: https://tinyurl.com/y476sn2d Company: Qualcomm Role: Gpu Dv Staff/senior Staff Engineer Link: https://tinyurl.com/584c8uwn Company: Qualcomm Role: Cpu Staff Engineer Link: https://tinyurl.c…
Company: Airlearn Role: Video Editing Intern Apply Link: https://tinyurl.com/wee8z6v5 Share With Your Friends
Daily jobs Updates pinned «Company: Birla Institute of Technology and Science Role: Content Development Apply Link: https://tinyurl.com/ybc867d3 Company: ALLEN Digital Role: Graphic Designer Apply Link: https://tinyurl.com/55xzeuua Company: Ultima Markets Role: Business Development…»
Company: Birla Institute of Technology and Science Role: Content Development Apply Link: https://tinyurl.com/ybc867d3 Company: ALLEN Digital Role: Graphic Designer Apply Link: https://tinyurl.com/55xzeuua Company: Ultima Markets Role: Business Development Manager Apply Link: https://tinyurl.com/3beby8pu
Company: Aramco Role: Technology Consultant Apply Link: https://tinyurl.com/23znavmf Company: Aramco Role: Analyzer Engineer Apply Link: https://tinyurl.com/784nptm7 Share With Your Friends
Company: GE Vernova Role: Lead Verification and Validation Engineer Experience: Freshers/experience Apply Link: https://tinyurl.com/3anj3cw2 *Share With your Friends*
Company: GE Vernova Rolee: systems Engineering Apply Link: https://tinyurl.com/8vvkt9wz Share With your Friends
Company: Prentis Role: Product Engineer Apply Link: https://tinyurl.com/v623vfar Company: Cloud Security Web Title: Associate Product Apply Link: https://tinyurl.com/48pxt5bb
Showing the 12 most recent of 20 posts we hold for @python_0. 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.
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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Daily jobs Updates” (@python_0), 3,243 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/python_0.
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.