Telegram RegisterThe public register of Telegram
Telegram profile photo for King of Odd

Channel

King of Odd

@betodd10odd

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

5,758subscribers

+184 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-1003035599777
TypeChannel
Username@betodd10odd
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/betodd10odd

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@strategiesbettllo/2866 Jul 2026, 15:08 UTC@betodd10odd/242 · this entry6 Jul 2026, 15:08 UTC1.00under a minute
@strategiesbettllo/29118 Jul 2026, 14:47 UTC@betodd10odd/247 · this entry18 Jul 2026, 14:47 UTC1.00under a minute
@strategiesbettllo/29425 Jul 2026, 14:52 UTC@betodd10odd/250 · this entry25 Jul 2026, 14:52 UTC1.00under a minute
@strategiesbettllo/29527 Jul 2026, 18:49 UTC@betodd10odd/251 · this entry27 Jul 2026, 18:49 UTC1.00under a minute
@betodd10odd/255 · this entry5 Aug 2026, 15:53 UTC@strategiesbettllo/3025 Aug 2026, 15:53 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@strategiesbettllo5 (5/5 hand-verifiable sample passed)1.00under a minute@strategiesbettllo (41)

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 4 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 5 comparable posts for this entry, running 6 July 2026 to 5 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 2, the earliest publisher we hold is @strategiesbettllo. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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 1 other registered channel, 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

5,5585,7585,6587 August 2026 — 5,574 subscribers7 August 2026 — 5,574 subscribers8 August 2026 — 5,575 subscribers11 August 2026 — 5,558 subscribers14 August 2026 — 5,562 subscribers18 August 2026 — 5,595 subscribers20 August 2026 — 5,635 subscribers24 August 2026 — 5,668 subscribers27 August 2026 — 5,698 subscribers30 August 2026 — 5,730 subscribers2 September 2026 — 5,736 subscribers6 September 2026 — 5,750 subscribers11 September 2026 — 5,755 subscribers14 September 2026 — 5,756 subscribers18 September 2026 — 5,758 subscribers7 August 202618 September 2026
15 measurements spanning 42 days, net +184. 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 5,528–5,788 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:575,758+2
14 Sept 2026, 17:405,756+1
11 Sept 2026, 05:015,755+5
6 Sept 2026, 08:405,750+14
2 Sept 2026, 08:265,736+6
30 Aug 2026, 11:125,730+32
27 Aug 2026, 17:525,698+30
24 Aug 2026, 15:355,668+33
20 Aug 2026, 21:475,635+40
18 Aug 2026, 03:225,595+33
14 Aug 2026, 23:485,562+4
11 Aug 2026, 14:525,558-17
8 Aug 2026, 18:245,575+1
7 Aug 2026, 19:185,574no change
7 Aug 2026, 19:035,574first reading

Engagement

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

Reaction mix

164 reactions across 21 posts, in 2 distinct kinds. The most used accounts for 51.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8551.8%
👍7948.2%

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

Measured over the 21 most recent posts we hold, published 26 June 2026 to 9 August 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

9 Aug 2026, 17:58 UTC14 views8 reactionsread 12 August 2026

Today tips Palmerias 🆚 Sport Club Internacional ⏸ home win Odds⏩ 1.58 Brazil 🇧🇷 Campeonato Brasileiro 09.08.2026 (22:00)

👍62

7 Aug 2026, 16:56 UTC885 views8 reactionsread 12 August 2026

Today tips Wolves 🆚 Port Vale ⏸ home win and over 1.5 Odds⏩ 1.39 England 🏴󐁧󐁢󐁥󐁮󐁧󐁿 League Cup 07.08.2026 (21:45)

6👍2

5 Aug 2026, 15:53 UTC≈1,260 views8 reactionsread 12 August 2026

Today tips Gualberto 🆚 San Antonio Bulo Bulo Pick ➡️ both team score Odds 1.49 Bolivia 🇧🇴 Primera Division 05/08/2026 (22:00)

👍62

3 Aug 2026, 14:35 UTC≈1,220 views5 reactionsread 12 August 2026

Today tips Seinajoen 🆚 HJK Pick ➡️ over 2.5 Odds 1.46 Finland 🇫🇮 Veikkausliga 03/08/2026 19:00

3👍2

1 Aug 2026, 14:51 UTC≈1,230 views7 reactionsread 12 August 2026

Today tips Real Madrid 🆚 Fiorentina ⏸ over 2.5 Odds⏩ 1.44 Club Friendlies 01.08.2026 (19:00)

5👍2

29 Jul 2026, 15:09 UTC≈1,610 views13 reactionsread 12 August 2026

Today tips Grindavik 🆚 Leiknir Reykjavik Pick ➡️ both team score Odds 1.46 Iceland 🇮🇸 1 Deild 29/07/2026 (22:15)

8👍5

27 Jul 2026, 18:49 UTC≈1,250 views8 reactionsread 12 August 2026

Today tips Breidablik UBK 🆚 Vestanmanaeyja Pick ➡️ both team score Odds 1.4 Iceland 🇮🇸 Urvalsdeild 27/07/2026 (23:00)

4👍4

25 Jul 2026, 14:52 UTC≈1,240 views4 reactionsread 12 August 2026

Today tips Sporting Cp 🆚 As Monaco ⏸ home win either Half Standard Liege 🆚 Juventus ⏸ Away Score Odds⏩ 1.47 Club Friendlies 25.07.2026 (21:00)

2👍2

23 Jul 2026, 16:26 UTC≈1,440 views10 reactionsread 12 August 2026

Today tips BATE 🆚 Sion ⏸ Away Win and over 1.5 Odds⏩ 1.40 UEFA 🇪🇺 Conference League 23.07.2026 (20:00)

👍64

21 Jul 2026, 14:54 UTC≈1,780 views6 reactionsread 12 August 2026

Today tips Walsall 🆚 Aston Villa Pick ➡️ away win Odds 1.43 Club Friendlies 🌏 21/07/2026 (21:30)

👍42

18 Jul 2026, 14:47 UTC≈1,170 views8 reactionsread 12 August 2026

Daily tips LEAGUE ⏩ Latvia. 1st League DATE ⏩ 18.07.2026 TIME ⏩ 17:00 ACTIVITY ⏩ Skantes SK 🆚 Valmieras TAKE ⏩ Away Win And Total. Over (1.5) Odds ⏩ 1.50

👍62

15 Jul 2026, 17:32 UTC≈1,580 views8 reactionsread 12 August 2026

Today tips Libertad Loja 🆚 Tecinico Pick ➡️ both team score Odds 1.83 Ecuador 🇪🇨 Serie A 15/07/2026 (23:00)

7👍1

Showing the 12 most recent of 21 posts we hold for @betodd10odd. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“King of Odd” (@betodd10odd), 5,758 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/betodd10odd.

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.