Telegram RegisterThe public register of Telegram
Telegram profile photo for [Tennis_Tippar]

Channel

[Tennis_Tippar]

@tennis_tippar1

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

15,239subscribers

-141 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001613653360
TypeChannel
Username@tennis_tippar1
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live17 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/tennis_tippar1

Topic

Gambling & betting — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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

12.2 average views per post against 15,239 subscribers — an engagement rate of 0.08%. Across the 940 registered channels in the same cohort — 10,026–31,614 subscribers, posting mainly in Hindi — the middle half sit between 3.96% and 16.2%, with a median of 8.91%.

What this was computed from
Window30 days (23 August 2026 22 September 2026)
Posts measured215 of 215 published in the window (215 exact, 0 rounded by Telegram)
Views totalled2,613
Mature posts only0.109% over 12 posts read at least 24h after publication
Subscribers15,239 measured 17 September 2026
Cohortb10000:hin · 940 channels · p10 1.09% · p25 3.96% · p50 8.91% · p75 16.2% · p90 27.0%
Position in cohort0.213th percentile · 1/111 the cohort median
Uncertainty±0.189% of the figure, from Telegram’s rounding
Post languageHindi · 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 22 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

15,23915,38015,309.513 August 2026 — 15,380 subscribers13 August 2026 — 15,376 subscribers15 August 2026 — 15,370 subscribers16 August 2026 — 15,363 subscribers17 August 2026 — 15,355 subscribers18 August 2026 — 15,343 subscribers19 August 2026 — 15,338 subscribers20 August 2026 — 15,333 subscribers21 August 2026 — 15,331 subscribers23 August 2026 — 15,326 subscribers24 August 2026 — 15,315 subscribers25 August 2026 — 15,308 subscribers26 August 2026 — 15,307 subscribers27 August 2026 — 15,306 subscribers28 August 2026 — 15,304 subscribers30 August 2026 — 15,302 subscribers31 August 2026 — 15,293 subscribers1 September 2026 — 15,286 subscribers2 September 2026 — 15,277 subscribers4 September 2026 — 15,275 subscribers6 September 2026 — 15,263 subscribers10 September 2026 — 15,257 subscribers12 September 2026 — 15,249 subscribers13 September 2026 — 15,245 subscribers15 September 2026 — 15,243 subscribers17 September 2026 — 15,239 subscribers13 August 202617 September 2026
26 measurements spanning 35 days, net -141. 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 15,218–15,401 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
17 Sept 2026, 15:0115,239-4
15 Sept 2026, 13:5915,243-2
13 Sept 2026, 21:1915,245-4
12 Sept 2026, 05:4015,249-8
10 Sept 2026, 00:0115,257-6
6 Sept 2026, 17:4215,263-12
4 Sept 2026, 06:1515,275-2
2 Sept 2026, 18:3715,277-9
1 Sept 2026, 19:3415,286-7
31 Aug 2026, 21:3415,293-9
30 Aug 2026, 23:4415,302-2
28 Aug 2026, 18:1615,304-2
27 Aug 2026, 15:5715,306-1
26 Aug 2026, 19:1615,307-1
25 Aug 2026, 22:3315,308-7
24 Aug 2026, 19:2515,315-11
23 Aug 2026, 07:4315,326-5
21 Aug 2026, 21:5615,331-2
20 Aug 2026, 18:5515,333-5
19 Aug 2026, 18:3815,338first reading

Engagement

405 posts held, back to 12 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 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.08%
avg views ÷ 15,239 subscribers
Avg views / post
12.2
215 posts measured
Reaction rate
11.1%
reactions ÷ views · ER floor
Posts in window
215
of 405 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 2 of 215 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held405 (12 August 20263 September 2026)
Views total2,613
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:53 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 48s
Average length
15s

Measured directly from 7 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.

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.0%

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 2 of the 405 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 405 most recent posts we hold, published 12 August 2026 to 3 September 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

3 Sept 2026, 02:59 UTC13 views1 reactionsread 3 September 2026
Photo

Live profit sharing dn 5k to 55k profit

1

3 Sept 2026, 02:20 UTC15 viewsread 3 September 2026
Photo

30% Profit Sharing.......❤️‍🔥❤️‍🔥 Work......😘🔥

3 Sept 2026, 02:20 UTC16 viewsread 3 September 2026
Photo

30% Profit Sharing.......❤️‍🔥❤️‍🔥 Work......😘🔥

3 Sept 2026, 02:18 UTC15 viewsread 3 September 2026
Photo

22p jackpot dn nd dusted 🔥🔥 Player Won ✔️✔️

2 Sept 2026, 18:47 UTC16 viewsread 3 September 2026
Photo

LIVE US OPEN TENNIS PAID WORK DONE & DUSTED ❤️ ✅ JO AAYEGA PAISA KAMAYEGA 💯✅

2 Sept 2026, 14:55 UTC17 viewsread 3 September 2026
Photo

ADVANCE TENNIS MATCH 🎾 #Munar WIN KARO BOOK 📖 SET COMPULSORY❤️

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“[Tennis_Tippar]” (@tennis_tippar1), 15,239 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tennis_tippar1.

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.