Telegram RegisterThe public register of Telegram
Telegram profile photo for FIXED MATCHES CORRECT SCORES

Channel

FIXED MATCHES CORRECT SCORES

@Correctscore_Fixedmatchesbetting

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Domains linked from posts · Cite this entry

4,915subscribers

-95,597 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002187123538
TypeChannel
Username@Correctscore_Fixedmatchesbetting
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/Correctscore_Fixedmatchesbetting

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 100% 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 in near-verbatim form on 9 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@Correctscore_Fixedmatchesbetting/7944 · this entry6 Aug 2026, 10:04 UTC@Englandfixedmatchesservice/74096 Aug 2026, 10:06 UTC1.002 minutes
@Englandfixedmatchesservice/74116 Aug 2026, 10:19 UTC@Correctscore_Fixedmatchesbetting/7946 · this entry6 Aug 2026, 10:19 UTC1.00under a minute
@Correctscore_Fixedmatchesbetting/7947 · this entry6 Aug 2026, 22:04 UTC@Englandfixedmatchesservice/74126 Aug 2026, 22:06 UTC1.002 minutes
@Correctscore_Fixedmatchesbetting/8020 · this entry16 Aug 2026, 10:09 UTC@Englandfixedmatchesservice/748416 Aug 2026, 10:09 UTC1.00under a minute
@Englandfixedmatchesservice/760212 Sept 2026, 22:10 UTC@Correctscore_Fixedmatchesbetting/8133 · this entry12 Sept 2026, 22:10 UTC1.00under a minute
@Correctscore_Fixedmatchesbetting/8184 · this entry9 Oct 2026, 08:16 UTC@Englandfixedmatchesservice/76509 Oct 2026, 08:17 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Englandfixedmatchesservice89 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (48–41)
@BET365_1XBET_BETWAY_22BET10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–4)
@ukfixedmatchservice_Bet3657 (7/7 hand-verifiable sample passed)1.0010 days@ukfixedmatchservice_Bet365 (6–1)
@ukfixedmatchserviceBet3656 (6/6 hand-verifiable sample passed)1.0011 days@ukfixedmatchserviceBet365 (6–0)
@BET365_FIXED_MATCHES6 (6/6 hand-verifiable sample passed)0.985.8 hours@BET365_FIXED_MATCHES (6–0)
@FIXED_MATCHES_WiN16 (6/6 hand-verifiable sample passed)0.985.7 hours@FIXED_MATCHES_WiN1 (6–0)
@europeanfixedmatchservices_1XBET5 (5/5 hand-verifiable sample passed)1.0015 days@europeanfixedmatchservices_1XBET (3–2)
@usafixedmatcheservice_sportybet5 (5/5 hand-verifiable sample passed)1.0011 days@usafixedmatcheservice_sportybet (3–2)
@Europefixedmatch5 (5/5 hand-verifiable sample passed)0.9674 minutes@Europefixedmatch (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. 79 of the 80 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 175 comparable posts for this entry, running 5 August 2026 to 12 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @Englandfixedmatchesservice. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 17 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

4,915100,51252,713.57 August 202613 November 2026
64 measurements spanning 98 days, net -95,597. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
13 Nov 2026, 12:564,915-12,584
11 Nov 2026, 00:4817,499-23
9 Nov 2026, 09:4517,522-26
8 Nov 2026, 00:4517,548-9
6 Nov 2026, 21:5617,557-7
6 Nov 2026, 00:5417,564-4
4 Nov 2026, 23:4617,568-11
4 Nov 2026, 02:4117,579+18
3 Nov 2026, 04:4017,561+27
2 Nov 2026, 06:4817,534-10,693
1 Nov 2026, 10:0428,227-17,281
31 Oct 2026, 10:2645,508+18
30 Oct 2026, 12:3745,490-35,477
29 Oct 2026, 10:2880,967-4,457
28 Oct 2026, 08:0985,424-24
27 Oct 2026, 11:3185,448-40
26 Oct 2026, 11:1685,488-26
25 Oct 2026, 08:4585,514+3
24 Oct 2026, 11:0585,511-1,133
23 Oct 2026, 13:3586,644first reading

Engagement

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

ERR · 30 days
1.23%
avg views ÷ 4,915 subscribers
Avg views / post
60.4
57 posts measured
Reaction rate
0.602%
reactions ÷ views · ER floor
Posts in window
59
of 301 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 57 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 12 November 2026
Posts held301 (5 August 2026 – 12 November 2026)
Views total3,440
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 05:08 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 27s
Average length
22s

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.

Reaction mix

31,832 reactions across 100 posts, in 9 distinct kinds. The most used accounts for 11.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🥰3,60011.3%
🎉3,57911.2%
💯3,57511.2%
🤩3,56811.2%
❤3,53711.1%
😍3,50611.0%
🔥3,50111.0%
❤‍🔥3,48410.9%
👍3,48210.9%

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 101 of the 301 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 31,832 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 301 most recent posts we hold, published 5 August 2026 to 12 November 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

Telegram’s own ‘edited’ marker: 3 of 59 posts held from the last 30 days (5.08%) 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).

12 Nov 2026, 17:07 UTC10 viewsread 13 November 2026
Photo

🔥 REAL TESTIMONIALS. REAL RESULTS. REAL MONEY 🔥 I’m honestly blown away by what VIP members are achieving right now. People who started with small steps are now living big — securing apartments, driving their dream cars, owning beautiful homes, and traveling without thinking twice. This is not luck, this is what happens when you plug into something that works. Every day, I get messages from members celebrating wins …

12 Nov 2026, 17:05 UTC10 viewsread 13 November 2026
Photo

😅, LIVE 🎥 WATCH TILL END NO ONE DOES IT BETTER IT’S FIXED WHEN I SAID IT IS 💪 CONGRATULATIONS TO YOU ALL THAT PARTAKES IN TO YESTERDAY MATCHES

12 Nov 2026, 17:05 UTC7 viewsread 13 November 2026
Photo

Morning, lads! ☀️🇬🇧 Today's 2 Combined Correct Score picks will be dropping soon. 👀🔥 Keep your eyes peeled, get yourselves ready, and don't miss today's action. See you all shortly. 💷

12 Nov 2026, 17:05 UTC7 viewsread 13 November 2026
Video

We are the best ever you can do business of fixed match with 100% satisfaction. No doubt about that. Here is another testimony from the vip channel 👇👇👇👇👇👇👇👇👇

12 Nov 2026, 17:05 UTC6 viewsread 13 November 2026
Photo

🚀 How to Join VIP: 1. Message admin directly 2. Get payment details 3. Make payment 4. Receive your VIP ticket instantly ⚠️ Don’t wait till it’s too late… spots are limited! ✉️ Message now and secure your place in the next winning game ⭐️

12 Nov 2026, 17:04 UTC7 viewsread 13 November 2026
Photo

UNCOVERED For Todays fixed Event✅ How could you miss that? Congratulations to everyone that participated ✅ Contact for next bet

12 Nov 2026, 17:01 UTC9 viewsread 13 November 2026
Photo

Happy Client Spain 🇪🇸 💶💶💶💶💶 WOW😉, there has been some huge results again for Today’s tickets ! Members are making a Thousands as always 🤩 🥇“Whatever you can do or dream you can, begin it. Boldness has genius, magic, and power in it."🥇 Message Me Here

11 Nov 2026, 13:14 UTC19 viewsread 13 November 2026
Photo

Next Fixed Match received ✅ #Odd: 598:00 All interested members should message me for booking… 🔅 let’s win this monster ticket together 🎁 This match security is very high.. with no chance of losing💡My slots are very few… Don’t stand a chance to miss Date : ( 11 / November / 2026 ) Match available in every bookie Hit Me Up 🤙

11 Nov 2026, 13:14 UTC19 viewsread 13 November 2026
Video

🔊Good News Everyone 🔊 Today's Fixed Game is Ready and Set for a big win🎖 🔊All information is directly from both clubs High Odds #Game is 100% Fixed And No Chance of loosing #Winning is 100% Guaranteed🎖 To join The VIP group & promotion inquiries. Contact @

11 Nov 2026, 13:14 UTC17 viewsread 13 November 2026
Photo

Good Morning Lads😁❤️ Don’t Work Like A Slave When You Can Earn Like A King 👑 A Reasonable and Money Minded Being Will Understand that Taking Positive Risk With Me Is The Goal Without Risk There won’t Be The Word Rich nvest with Me Today & Earn Big Easily ➡️➡️

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

Posts recorded as deleted after publishing

We recorded 5 posts on @Correctscore_Fixedmatchesbetting as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
15 August 2026
Most recent seen missing
20 October 2026
Median time before seen missing
14 hours
Seen missing in the last 30 days
1

Domains linked from posts

One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

bet365.com4 posts · 5 August 2026 – 7 August 2026 · example post

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

“FIXED MATCHES CORRECT SCORES” (@Correctscore_Fixedmatchesbetting), 4,915 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/Correctscore_Fixedmatchesbetting.

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.