About TG Inspector
TG Inspector checks public Telegram channel signals before an advertising purchase. It calculates a 0–100 cleanliness index and explains which observations increased or reduced confidence.
The problem it solves
Advertisers usually see a channel's subscriber count and public post views. Both numbers can be manipulated, while Telegram's internal acquisition and demographic analytics remain private to channel administrators.
TG Inspector checks whether public signals are internally consistent: how views relate to subscribers, how they vary between posts, whether old posts continue gaining views, and how people react or comment. Manipulation often breaks one or more of these relationships.
- Advertisers get evidence for a buy-or-skip decision before transferring money.
- Channel owners can share an independent check instead of an unverifiable analytics screenshot.
- Agencies can compare several candidate channels before approving a media plan.
Cleanliness-index signals
Each available signal produces a risk value from 0 to 1. Weighted signal risk becomes a 0–100 risk score. Cleanliness index = 100 − risk score, so a higher index is better.
- ERR and reach — 25%. Median views relative to subscribers. Very low reach can indicate an inactive audience; an extreme value can indicate manipulated views.
- View variation — 15%. Real posts usually perform differently; mechanically similar counts across many posts deserve scrutiny.
- View maturation — 15%. Organic posts often keep gaining views, while purchased delivery may arrive as a short burst and stop.
- Reactions — 10%. Reaction volume and composition relative to views.
- Comments — 25%. Language patterns and commenter structure, with authors anonymized before LLM analysis.
- Metadata — 10%. Channel age, Telegram service flags, advertising load, and deleted-post signals.
When a block is unavailable, its weight is redistributed among the remaining signals and confidence decreases. High confidence starts at 80% available weight; medium starts at 50%.
Grade and traffic-light scale
| Grade | Cleanliness | Risk score | Zone | Interpretation |
|---|---|---|---|---|
| A+ | 91–100 | 0–9 | green | No visible manipulation signals |
| A | 81–90 | 10–19 | green | Clean, with minor deviations |
| B | 70–80 | 20–30 | green | Generally normal; verify the noted signals |
| C | 55–69 | 31–45 | yellow | Some doubts; negotiate and request more data |
| D | 40–54 | 46–60 | yellow | Material warning signs and overpayment risk |
| F | 0–39 | 61–100 | red | High manipulation risk |
What happens during a check
- Collection. Public posts, views, reactions, comments, description, and Telegram service flags are saved as one snapshot.
- Scoring. Deterministic rules calculate each available signal and the final score.
- LLM analysis. A language model reviews anonymized comments and content, then writes a summary. It cannot alter the score.
- Report. The user receives the index, grade, metrics, findings, expected advertising reach, and questions for the channel owner.
What the service cannot establish
- It does not issue a verdict of guilt. The score estimates statistical risk and does not prove intent.
- It cannot see internal Telegram analytics. Acquisition sources, demographics, and private conversion data are visible only to the administrator.
- It does not editorially rate content quality. Content and ad-load flags inform an advertiser; they do not judge the channel's value.
- It cannot check private channels without public access to posts.
- It does not replace negotiation. The report provides evidence and questions; the purchasing decision remains yours.
Data, privacy, and public pages
Only public metrics are used. TG Inspector does not request access to private channels or collect subscriber identities. Comment authors are replaced with anonymous account labels before LLM processing.
High-risk channel pages are excluded from search indexing and public selections. Channel size alone does not restrict indexing: pages for channels of any size may appear in search results.
A channel owner may request removal from public access through the bot. See the Privacy Policy, Terms of Use, and methodology.