Follow or connect with me on my new LinkedIn account. 🤝💼 I’m planning to share latest insights and news of tech industry. 📰🚀 Also will notify if i’m hiring new talents. 👥✨

Channel
Mahesh Chauhan
@MaheshChauhan
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
4,729subscribers
-127 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 | -1001608619919 |
|---|---|
| Type | Channel |
| Username | @MaheshChauhan |
| Created | 8 December 2021 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/MaheshChauhan |
Topic
Technology — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 36% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 17:38 | 4,729 | -5 |
| 13 Sept 2026, 00:18 | 4,734 | -12 |
| 8 Sept 2026, 21:41 | 4,746 | -14 |
| 3 Sept 2026, 09:42 | 4,760 | -12 |
| 30 Aug 2026, 22:34 | 4,772 | -5 |
| 27 Aug 2026, 14:55 | 4,777 | -7 |
| 24 Aug 2026, 07:35 | 4,784 | -13 |
| 20 Aug 2026, 12:13 | 4,797 | -15 |
| 17 Aug 2026, 19:37 | 4,812 | -13 |
| 14 Aug 2026, 23:55 | 4,825 | -15 |
| 11 Aug 2026, 10:08 | 4,840 | -16 |
| 8 Aug 2026, 01:48 | 4,856 | no change |
| 7 Aug 2026, 07:31 | 4,856 | first reading |
Engagement
18 posts held, back to 8 December 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 8 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 18 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Paid subscription of bots? Purchase from @SubscriptionForBot 💰
📣 If anyone wants me to code a paid bot of their choice then message on @MaheshChauhanBot with complete description of what you want. 💎 ⚠️ Note: Don’t message for save restricted content bots or txt to file bots
Fixes in SRCB open source!! - Thumbanil & screenshot working - Public groups supported - Topics supported - Restricted Bots supported - Session gen bot link updated - other minor fixes
VPS deploy for Save Restricted Content Bot Read "The Hard Way" from here https://github.com/vasusen-code/SaveRestrictedContentBot#deploy Support: @TeamDrone
I've been reported that heroku is banning VIDEOconvertor I tried to fix the issue by updating the requirements, you can try deploying. Source - Click here Support : @TeamDrone
Temporary deploy link for Save Restricted bot: - First fork and star : Click here - Fill Vars here and deploy : Click here Donate💸 : UPI [Thankyou] Last Updated : 01/june/22 at 19:42
Heroku Deploy for VideoConvertor: (You can deploy by this method until heroku fixes it's internal issues) •open repo in desktop mode •Star repo first & fork it •go to settings of your fork and rename it to any other name •go to the branch you want to deploy •click on deploy to heroku
Okteto deploy update You can now deploy VideoConvertor and SaveRestrictedBot on Cloud.Okteto.com Tutorial : Click here
VIDEO CONVERTOR v1.4 •Encode into x264, x265, 240p, 360p, 480p and 780p •Two types of compress: - HEVC - Losless compress - FAST - 3X to 4x Faster compress •Generate 10 screenshots of videos •minor changes Source [🌟]: For personal use - click here For your channel - click here
Save restricted Bot UPDATE: Repo: Github.com/vasusen-code/SaveRestrictedContentBot •Fixed all bugs •Smart Batch upload for both public and private (upto 100 files) •Telethon to Pyrogram •Sweet Readme.md There will be no more updates in the repo.
Small Update: Repo: Github.com/Vasusen-code/SaveRestrictedContentBot • Caption supported • Get restricted messages • Forcesubcribe • Use telethon String instead of pyrogram Read this, i dont have time to reply questions regarding stuffs mentioned in repo.
Showing the 12 most recent of 18 posts we hold for @MaheshChauhan. 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
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Mahesh Chauhan” (@MaheshChauhan), 4,729 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/MaheshChauhan.
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.