Telegram RegisterThe public register of Telegram
Telegram profile photo for Kevin

Channel

Kevin

@kevin_rich

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

10,107subscribers

-1,509 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001155627253
TypeChannel
Username@kevin_rich
CreatedBetween 1 September 2018 and 30 April 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/kevin_rich

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kevin_rich/8546 · this entry4 Aug 2026, 08:04 UTC@sportsbetting2023/65454 Aug 2026, 08:04 UTC1.00under a minute
@kevin_rich/8547 · this entry4 Aug 2026, 12:26 UTC@sportsbetting2023/65464 Aug 2026, 12:28 UTC1.002 minutes
@kevin_rich/8550 · this entry5 Aug 2026, 07:52 UTC@sportsbetting2023/65495 Aug 2026, 07:54 UTC1.002 minutes
@kevin_rich/8553 · this entry5 Aug 2026, 10:52 UTC@sportsbetting2023/65515 Aug 2026, 10:52 UTC1.00under a minute
@kevin_rich/8559 · this entry6 Aug 2026, 08:10 UTC@sportsbetting2023/65576 Aug 2026, 08:18 UTC1.008 minutes
@kevin_rich/8564 · this entry7 Aug 2026, 07:04 UTC@sportsbetting2023/65617 Aug 2026, 07:06 UTC1.002 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@sportsbetting20237 (7/7 hand-verifiable sample passed)1.002 minutesthis entry (7–0)
@tochnyische7 (7/7 hand-verifiable sample passed)1.002 minutesthis entry (7–0)
@americanfixedgame6 (6/6 hand-verifiable sample passed)1.002 minutesthis entry (6–0)
@freebets235 (5/5 hand-verifiable sample passed)1.003 minutesthis entry (5–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 0 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 8 comparable posts for this entry, running 4 August 2026 to 7 August 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 5, the earliest publisher we hold is @kevin_rich — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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.

Also posting the same content

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.

Growth

10,10711,61610,861.56 August 2026 — 11,616 subscribers7 August 2026 — 11,616 subscribers8 August 2026 — 11,605 subscribers10 August 2026 — 11,594 subscribers11 August 2026 — 11,592 subscribers12 August 2026 — 11,579 subscribers13 August 2026 — 11,573 subscribers14 August 2026 — 11,574 subscribers17 August 2026 — 11,563 subscribers18 August 2026 — 11,549 subscribers19 August 2026 — 11,535 subscribers20 August 2026 — 11,523 subscribers21 August 2026 — 11,510 subscribers23 August 2026 — 11,505 subscribers24 August 2026 — 11,494 subscribers25 August 2026 — 11,484 subscribers26 August 2026 — 11,474 subscribers27 August 2026 — 11,473 subscribers28 August 2026 — 11,475 subscribers29 August 2026 — 11,471 subscribers30 August 2026 — 11,466 subscribers31 August 2026 — 11,459 subscribers1 September 2026 — 11,437 subscribers2 September 2026 — 11,430 subscribers3 September 2026 — 11,422 subscribers5 September 2026 — 11,395 subscribers9 September 2026 — 11,378 subscribers11 September 2026 — 11,337 subscribers13 September 2026 — 11,325 subscribers15 September 2026 — 11,311 subscribers17 September 2026 — 10,444 subscribers25 September 2026 — 10,394 subscribers4 October 2026 — 10,328 subscribers8 October 2026 — 10,305 subscribers12 October 2026 — 10,263 subscribers14 October 2026 — 10,245 subscribers15 October 2026 — 10,238 subscribers16 October 2026 — 10,232 subscribers17 October 2026 — 10,228 subscribers18 October 2026 — 10,224 subscribers19 October 2026 — 10,215 subscribers20 October 2026 — 10,217 subscribers21 October 2026 — 10,207 subscribers22 October 2026 — 10,204 subscribers23 October 2026 — 10,202 subscribers24 October 2026 — 10,199 subscribers25 October 2026 — 10,194 subscribers26 October 2026 — 10,190 subscribers27 October 2026 — 10,183 subscribers28 October 2026 — 10,178 subscribers29 October 2026 — 10,176 subscribers30 October 2026 — 10,168 subscribers31 October 2026 — 10,151 subscribers1 November 2026 — 10,143 subscribers3 November 2026 — 10,137 subscribers4 November 2026 — 10,130 subscribers6 November 2026 — 10,116 subscribers7 November 2026 — 10,107 subscribers6 August 20267 November 2026
58 measurements spanning 92 days, net -1,509. 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 9,881–11,842 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
7 Nov 2026, 02:1910,107-9
6 Nov 2026, 03:0510,116-14
4 Nov 2026, 05:5110,130-7
3 Nov 2026, 05:3910,137-6
1 Nov 2026, 10:3610,143-8
31 Oct 2026, 13:5610,151-17
30 Oct 2026, 14:5610,168-8
29 Oct 2026, 14:0510,176-2
28 Oct 2026, 12:2110,178-5
27 Oct 2026, 12:2610,183-7
26 Oct 2026, 15:3010,190-4
25 Oct 2026, 18:4710,194-5
24 Oct 2026, 16:3610,199-3
23 Oct 2026, 15:3510,202-2
22 Oct 2026, 18:2710,204-3
21 Oct 2026, 15:2810,207-10
20 Oct 2026, 08:5410,217+2
19 Oct 2026, 08:5810,215-9
18 Oct 2026, 07:1610,224-4
17 Oct 2026, 07:2910,228first reading

Engagement

241 posts held, back to 3 August 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 52 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.35%
avg views ÷ 10,107 subscribers
Avg views / post
136
47 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
47
of 241 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 6 November 2026
Posts held241 (3 August 2026 – 6 November 2026)
Views total6,406
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 21:11 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
2m 21s
Average length
6s

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

Telegram’s own ‘edited’ marker: 0 of 47 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 20:42 UTC9 viewsread 6 November 2026
Photo

💳 Funds in the pocket Congratulations to everyone who placed a bet alongside us.

6 Nov 2026, 15:29 UTC59 viewsread 6 November 2026
Photo

💳vip predictions for today 10€ - 7 days https://t.me/tribute/app?startapp=s120O

6 Nov 2026, 10:36 UTC93 viewsread 6 November 2026

🤙 Should you require assistance, please contact me via direct message. @jack_smith_one

6 Nov 2026, 08:00 UTC113 viewsread 6 November 2026
Photo

exact score 0-0 with odds of 24.00 is available free of charge here 🤑 For those unable to locate the game, it is accessible here: After registration, navigate to the "Sports" tab, then access the search function (indicated by the small magnifying glass icon 🔍) and enter the name of the team.✅✅

5 Nov 2026, 22:19 UTC126 viewsread 6 November 2026
Photo

🫤😅👍😭😩 Free correct score 💯 🗓06 November 🕔17:00 UTC +2 😀Football: Malta Friendly Cup 😀Gharghur FC - Mdina Knights ❗️Score 0:0 ❗️Odds 24 https://beteefy.com/sport/line/201/95217/16664371

5 Nov 2026, 17:05 UTC123 viewsread 6 November 2026
Photo

https://beteefy.com/sport/live/201/103714/16486543 live

5 Nov 2026, 10:41 UTC149 viewsread 6 November 2026
Photo

💳vip predictions for today 10€ - 7 days https://t.me/tribute/app?startapp=s120O

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Точный счёт | Договорные матчи Бесплатно
@tochnyische · 26,260
Telegram ranks this channel #9 of 74 here — alongside 73 others — read 28 September 2026
1XBET ANIQ HISOB MELBET LINEBET KUPON FUTBOL
@a_1xbet_Melbet_Linebet_Aniqhisob · 35,386
Telegram ranks this channel #35 of 73 here — alongside 72 others — read 2 September 2026
FIXED GAMES | FREE MATCHES
@free_matches_free_bets · 47,274
Telegram ranks this channel #41 of 80 here — alongside 79 others — read 25 August 2026
DRUID LE BAOBAB💰🐍🦉😈
@druidlebaobabcanal · 18,181
Telegram ranks this channel #55 of 61 here — alongside 60 others — read 1 October 2026
🎗 FIFA SCORE EXACTE 🎗
@fifa_score_exacte · 18,013
Telegram ranks this channel #57 of 84 here — alongside 83 others — read 5 October 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Kevin” (@kevin_rich), 10,107 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/kevin_rich.

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.