Telegram RegisterThe public register of Telegram
Telegram profile photo for Betleaks • Fixed Matches

Channel

Betleaks • Fixed Matches

@fixed_matches

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

14,983subscribers

-86 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001372270395
TypeChannel
Username@fixed_matches
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held20
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/fixed_matches

Growth

14,98315,07015,026.57 August 2026 — 15,069 subscribers7 August 2026 — 15,069 subscribers8 August 2026 — 15,068 subscribers9 August 2026 — 15,070 subscribers10 August 2026 — 15,068 subscribers11 August 2026 — 15,062 subscribers12 August 2026 — 15,059 subscribers13 August 2026 — 15,046 subscribers14 August 2026 — 15,041 subscribers16 August 2026 — 15,036 subscribers17 August 2026 — 15,026 subscribers18 August 2026 — 15,018 subscribers19 August 2026 — 15,016 subscribers20 August 2026 — 15,012 subscribers21 August 2026 — 15,005 subscribers22 August 2026 — 15,004 subscribers24 August 2026 — 14,997 subscribers25 August 2026 — 14,990 subscribers26 August 2026 — 14,985 subscribers27 August 2026 — 14,983 subscribers7 August 202627 August 2026
20 measurements spanning 21 days, net -86. 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 14,970–15,083 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 15:5614,983-2
26 Aug 2026, 14:2314,985-5
25 Aug 2026, 13:0214,990-7
24 Aug 2026, 10:2314,997-7
22 Aug 2026, 19:3815,004-1
21 Aug 2026, 10:0815,005-7
20 Aug 2026, 13:0315,012-4
19 Aug 2026, 16:0415,016-2
18 Aug 2026, 16:1315,018-8
17 Aug 2026, 16:0815,026-10
16 Aug 2026, 08:0415,036-5
14 Aug 2026, 19:2515,041-5
13 Aug 2026, 09:3415,046-13
12 Aug 2026, 11:5415,059-3
11 Aug 2026, 09:3315,062-6
10 Aug 2026, 08:0115,068-2
9 Aug 2026, 05:5215,070+2
8 Aug 2026, 04:5815,068-1
7 Aug 2026, 01:3015,069no change
7 Aug 2026, 01:2415,069first reading

Engagement

6 posts held, back to 21 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 41 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 6 posts for this entry, the most recent from 4 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

500 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
18236.4%
👍17434.8%
🔥14428.8%

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

Measured over the 6 most recent posts we hold, published 21 April 2026 to 4 May 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

4 May 2026, 14:45 UTC≈15,400 views84 reactionsread 27 August 2026

​🗓 May 8 · · · · · · · · · · · · · · · · · · · · · · · · · ⚽️ 🇮🇹 Italy. Serie B. · · · · · · · · · · · · · · · · · · · · · · · · · Outcome ❕ Odds: 2.10+ ❕ Price: 1000€ (~0.0155 BTC) Correct Score ❕ Odds: 10.00+ ❕ Price: 3000€ (~0.0455 BTC) · · · · · · · · · · · · · · · · · · · · · · · · · · ⏱ Payment until 16:00 [UTC] · · · · · · · · · · · · · · · · · · · · · · · · · · To get information, you need to: 1) make

37👍28🔥19

4 May 2026, 14:42 UTC≈2,350 views67 reactionsread 27 August 2026
Photo

Report 2/2 🗓 May 1 🇮🇹 Italy. Serie B.

👍28🔥2118

4 May 2026, 14:41 UTC≈2,150 views85 reactionsread 27 August 2026
Photo

Report 1/2 🗓 May 1 🇮🇹 Italy. Serie B.

33👍28🔥24

21 Apr 2026, 17:00 UTC≈15,500 views105 reactionsread 27 August 2026

​🗓 May 1 · · · · · · · · · · · · · · · · · · · · · · · · · ⚽️ 🇮🇹 Italy. Serie B. · · · · · · · · · · · · · · · · · · · · · · · · · Outcome ❕ Odds: 2.40+ ❕ Price: 1000€ (~0.0105 BTC) Correct Score ❕ Odds: 9.00+ ❕ Price: 3000€ (~0.0315 BTC) · · · · · · · · · · · · · · · · · · · · · · · · · · ⏱ Payment until 14:00 [UTC] · · · · · · · · · · · · · · · · · · · · · · · · · · To get information, you need to: 1) make a

37👍36🔥32

21 Apr 2026, 16:54 UTC≈1,200 views85 reactionsread 27 August 2026
Photo

Report 2/2 🗓 April 11 🇮🇹 Italy. Serie B.

30👍28🔥27

21 Apr 2026, 16:53 UTC944 views74 reactionsread 27 August 2026
Photo

Report 1/2 🗓 April 11 🇮🇹 Italy. Serie B.

27👍26🔥21

Showing the 6 most recent of 6 posts we hold for @fixed_matches. 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.

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.

Betleaks
@Betleaks_Official · 64,439
Telegram ranks this channel #55 of 76 here — alongside 75 others — read 21 August 2026
Правила Бизнеса
@Business_rules · 63,980
Telegram ranks this channel #65 of 73 here — alongside 72 others — read 21 August 2026

This channel appears in 2 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“Betleaks • Fixed Matches” (@fixed_matches), 14,983 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/fixed_matches.

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.