Telegram RegisterThe public register of Telegram
Telegram profile photo for Mehta is Back

Channel

Mehta is Back

@mehtaisbackofficial_0

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Cite this entry

31,172subscribers

-6,575 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001723933951
TypeChannel
Username@mehtaisbackofficial_0
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/mehtaisbackofficial_0

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 15 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far below this size band

2.1 average views per post against 31,172 subscribers — an engagement rate of 0.007%. Across the 7,317 registered channels in the same cohort — 10,000–31,622 subscribers, posting mainly in English — the middle half sit between 2.30% and 13.2%, with a median of 6.19%.

What this was computed from
Window30 days (12 August 2026 11 September 2026)
Posts measured46 of 46 published in the window (46 exact, 0 rounded by Telegram)
Views totalled95
Mature posts only0.007% over 46 posts read at least 24h after publication
Subscribers31,172 measured 11 September 2026
Cohortb10000:eng · 7,317 channels · p10 0.669% · p25 2.30% · p50 6.19% · p75 13.2% · p90 23.4%
Position in cohort0.014th percentile · 1/1000 the cohort median
Uncertainty±0.093% of the figure, from Telegram’s rounding
Post languageEnglish · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_low, last confirmed 11 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

31,17237,74734,459.57 August 2026 — 37,747 subscribers7 August 2026 — 37,747 subscribers8 August 2026 — 37,147 subscribers9 August 2026 — 36,876 subscribers10 August 2026 — 36,575 subscribers11 August 2026 — 36,061 subscribers12 August 2026 — 35,722 subscribers14 August 2026 — 35,431 subscribers15 August 2026 — 35,249 subscribers16 August 2026 — 34,508 subscribers17 August 2026 — 34,277 subscribers18 August 2026 — 33,811 subscribers19 August 2026 — 33,718 subscribers20 August 2026 — 33,605 subscribers22 August 2026 — 33,552 subscribers23 August 2026 — 33,405 subscribers25 August 2026 — 33,328 subscribers26 August 2026 — 33,218 subscribers27 August 2026 — 33,064 subscribers28 August 2026 — 33,045 subscribers29 August 2026 — 32,680 subscribers30 August 2026 — 32,450 subscribers31 August 2026 — 32,190 subscribers1 September 2026 — 32,092 subscribers2 September 2026 — 31,890 subscribers3 September 2026 — 31,603 subscribers5 September 2026 — 31,527 subscribers8 September 2026 — 31,336 subscribers11 September 2026 — 31,172 subscribers7 August 202611 September 2026
29 measurements spanning 34 days, net -6,575. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 30,186–38,733 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
11 Sept 2026, 03:4031,172-164
8 Sept 2026, 08:2031,336-191
5 Sept 2026, 06:4231,527-76
3 Sept 2026, 13:3831,603-287
2 Sept 2026, 09:5331,890-202
1 Sept 2026, 09:5432,092-98
31 Aug 2026, 08:5432,190-260
30 Aug 2026, 06:4732,450-230
29 Aug 2026, 07:1332,680-365
28 Aug 2026, 05:3833,045-19
27 Aug 2026, 03:4533,064-154
26 Aug 2026, 03:1333,218-110
25 Aug 2026, 03:4633,328-77
23 Aug 2026, 23:0433,405-147
22 Aug 2026, 07:0733,552-53
20 Aug 2026, 23:2433,605-113
19 Aug 2026, 21:2933,718-93
18 Aug 2026, 22:0533,811-466
17 Aug 2026, 20:4534,277-231
16 Aug 2026, 22:2334,508first reading

Engagement

59 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.007%
avg views ÷ 31,172 subscribers
Avg views / post
2.1
46 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
46
of 59 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held59 (7 August 20263 September 2026)
Views total95
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Sept 2026, 13:24 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

Video runtime
1m 00s
Average length
15s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC3 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC3 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026

YESTERDAY 📊PROFIT BOOKED IN ACCOUNT HANDLING SERVICE ✅✅ DON'T MISS OPPORTUNITY 🤔✔️

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

3 Sept 2026, 13:12 UTC2 viewsread 7 September 2026
Photo

🔜 Account Management Work🛡💡 🔹BEST TRADING WORK • Risk Management ↗️ 🔻High accuracy = Real Profit 🤑👨‍💻

Showing the 12 most recent of 59 posts we hold for @mehtaisbackofficial_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.

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Mehta is Back” (@mehtaisbackofficial_0), 31,172 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/mehtaisbackofficial_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.