Channel
@Tennis_Match
On this record: Topic Β· Observations Β· Also posting the same content Β· Growth Β· Engagement Β· What this channel posts Β· Posts Β· Cite this entry
4,646subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
| Telegram ID | -1001170658826 |
|---|---|
| Type | Channel |
| Username | @Tennis_Match |
| Created | Between 1 March 2018 and 30 June 2021β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Tennis_Match |
Gambling & betting β 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
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.
Posts published here appear word for word on 4 other registered channels. The matching is on the text itself, not on Telegramβs forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Match_Football/42694 May 2026, 14:13 UTC | @Tennis_Match/4693 Β· this entry4 May 2026, 14:13 UTC | 1.00 | under a minute |
| @Match_Football/42716 May 2026, 14:23 UTC | @Tennis_Match/4695 Β· this entry6 May 2026, 14:23 UTC | 1.00 | under a minute |
| @Tennis_Match/4700 Β· this entry16 May 2026, 14:12 UTC | @Match_Football/427616 May 2026, 14:12 UTC | 1.00 | under a minute |
| @Tennis_Match/4706 Β· this entry22 May 2026, 14:28 UTC | @Match_Football/428222 May 2026, 15:24 UTC | 1.00 | 56 minutes |
| @Match_Football/428323 May 2026, 14:03 UTC | @Tennis_Match/4707 Β· this entry23 May 2026, 14:03 UTC | 1.00 | under a minute |
| @Match_Football/428526 May 2026, 14:15 UTC | @Tennis_Match/4709 Β· this entry26 May 2026, 14:16 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Match_Football | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @namantyagiofficial | 19 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | @namantyagiofficial (19β0) |
| @Namanpachori | 18 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | @Namanpachori (18β0) |
| @Jaanvi_and_Maanvi_Cricket_Report | 17 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | @Jaanvi_and_Maanvi_Cricket_Report (17β0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp β in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 64 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
βPublished firstβ means first in this corpus. We hold 20 comparable posts for this entry, running 4 May 2026 to 31 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detectorβs own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 5, the earliest publisher we hold is @Jaanvi_and_Maanvi_Cricket_Report. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy Β· clone_mutual, last confirmed 7 August 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.
This channelβs posts match, word for word or near enough, posts on 4 other registered channels, 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 |
|---|---|---|
| 7 Aug 2026, 04:30 | 4,646 | no change |
| 7 Aug 2026, 04:26 | 4,646 | first reading |
20 posts held, back to 4 May 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 7 pagesof 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 31 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramβs own channel header, read 12 August 2026 β not the date at the top of this page, which is when the subscriber count was last read. A count marked β was rounded by Telegram before we ever saw it β t.me prints these counters in full below 1,000 and to three significant figures above, so β142,000 means somewhere between 141,500 and 142,499.
πINDIAN PREMIER LEAGUE 2026π FINAL π ROYALS CHALLENGERS BANGLORE VS GUJRAT TITANS MATCH WINNER PREDICTION β‘οΈ BANGLORE OR RCB WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π QUALIFIER 2ND π RAJASTHAN ROYALS VS GUJRAT TITANS MATCH WINNER PREDICTION β‘οΈ GUJRAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π ELEMINATION 1ST π RAJASTHAN ROYALS VS SUNRISERS HYDERABAD MATCH WINNER PREDICTION β‘οΈ HYDERABAD OR SRH WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π QUALIFER 1ST π GUJRAT TITANS VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION β‘οΈ GUJRAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 69TH T20 π MUMBAI INDIANS VS RAJASTHAN ROYALS MATCH WINNER PREDICTION β‘οΈ MUMBAI OR MI WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 68TH T20 π LUCKNOW SUPER KINGS VS PUNJAB KINGS MATCH WINNER PREDICTION β‘οΈ PUNJAB OR PKBS WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 67TH T20 π SUNRISERS HYDERABAD VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION β‘οΈ BANGLORE OR RCB WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 66TH T20 π CHENNAI SUPER KINGS VS GUJRAT TITANS MATCH WINNER PREDICTION β‘οΈ GUJARAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 65TH T20 π MUMBAI INDIAN VS KOLKATA KNIGHT RIDERS MATCH WINNER PREDICTION β‘οΈ KOLKATA OR KKR WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 64TH T20 π RAJASTHAN ROYALS VS LUCKNOW SUPER GIANTS MATCH WINNER PREDICTION β‘οΈ RAJASTHAN OR RR WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 63TH T20 π CHENNAI SUPER KINGS VS SUNRISERS HYDERABAD MATCH WINNER PREDICTION β‘οΈ HYDERABAD OR SRH WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
πINDIAN PREMIER LEAGUE 2026π 61ST T20 π PUNJAB KINGS VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION β‘οΈ PUNJAB OR PKBS WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko π https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET β Λ’α΅α΅Κ³αΆΚ° α΅βΏ α΅α΅Λ‘α΅α΅Κ³α΅α΅
Showing the 12 most recent of 20 posts we hold for @Tennis_Match. 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.
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 7 August 2026 β this entry's latest reading, not the date you are reading this.
βππππππ ππΌππΎπ πΎβ (@Tennis_Match), 4,646 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Tennis_Match.
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.