Telegram RegisterThe public register of Telegram
Telegram profile photo for Bettime90 | بت تایم ۹۰

Channel

Bettime90 | بت تایم ۹۰

@bettime90

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

9,920subscribers

-471 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001436844677
TypeChannel
Username@bettime90
DescriptionBettime90Vip | بت تایم نود وی آی پی پیش بینی ورزشی ٫ کازینو زنده , بازی انفجار ،کازینو اولویشن ، بازی پلینو Sports Betting & live casino آدرس ورژن جدید سایت: Bettime90vip.com آدرس ورژن قدیمی سایت: Bettime90.com اینستاگرام سایت: @Bettime90
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/bettime90

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 1 other registered channel. 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
@bettime90Vip/89728 Jul 2026, 06:02 UTC@bettime90/6754 · this entry28 Jul 2026, 09:55 UTC1.003.9 hours
@bettime90Vip/90029 Jul 2026, 19:10 UTC@bettime90/6756 · this entry29 Jul 2026, 19:13 UTC1.004 minutes
@bettime90Vip/90129 Jul 2026, 20:35 UTC@bettime90/6757 · this entry29 Jul 2026, 20:36 UTC1.00under a minute
@bettime90Vip/90330 Jul 2026, 20:31 UTC@bettime90/6759 · this entry30 Jul 2026, 20:32 UTC1.0072 seconds
@bettime90Vip/9071 Aug 2026, 21:09 UTC@bettime90/6763 · this entry1 Aug 2026, 21:15 UTC1.006 minutes
@bettime90Vip/9166 Aug 2026, 06:32 UTC@bettime90/6771 · this entry6 Aug 2026, 20:30 UTC1.0014 hours
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
@bettime90Vip21 (8/8 hand-verifiable sample passed)0.9826 minutes@bettime90Vip (20–1)

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. 5 of the 20 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 88 comparable posts for this entry, running 26 July 2026 to 15 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 @bettime90 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 16 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

9,91910,39110,1555 August 2026 — 10,391 subscribers6 August 2026 — 10,390 subscribers6 August 2026 — 10,390 subscribers7 August 2026 — 10,383 subscribers7 August 2026 — 10,376 subscribers9 August 2026 — 10,377 subscribers10 August 2026 — 10,360 subscribers11 August 2026 — 10,355 subscribers12 August 2026 — 10,344 subscribers13 August 2026 — 10,333 subscribers14 August 2026 — 10,330 subscribers15 August 2026 — 10,320 subscribers16 August 2026 — 10,315 subscribers17 August 2026 — 10,311 subscribers19 August 2026 — 10,302 subscribers20 August 2026 — 10,296 subscribers21 August 2026 — 10,284 subscribers22 August 2026 — 10,274 subscribers24 August 2026 — 10,264 subscribers25 August 2026 — 10,257 subscribers26 August 2026 — 10,252 subscribers27 August 2026 — 10,253 subscribers28 August 2026 — 10,244 subscribers29 August 2026 — 10,243 subscribers30 August 2026 — 10,240 subscribers30 August 2026 — 10,233 subscribers31 August 2026 — 10,227 subscribers1 September 2026 — 10,226 subscribers2 September 2026 — 10,217 subscribers4 September 2026 — 10,212 subscribers7 September 2026 — 10,194 subscribers10 September 2026 — 10,175 subscribers12 September 2026 — 10,155 subscribers14 September 2026 — 10,147 subscribers15 September 2026 — 10,142 subscribers17 September 2026 — 10,134 subscribers27 September 2026 — 10,098 subscribers4 October 2026 — 10,050 subscribers9 October 2026 — 10,034 subscribers13 October 2026 — 10,006 subscribers14 October 2026 — 9,995 subscribers18 October 2026 — 9,984 subscribers21 October 2026 — 9,975 subscribers24 October 2026 — 9,961 subscribers27 October 2026 — 9,955 subscribers30 October 2026 — 9,945 subscribers3 November 2026 — 9,933 subscribers5 November 2026 — 9,927 subscribers9 November 2026 — 9,919 subscribers12 November 2026 — 9,920 subscribers9,9205 August 202612 November 2026
50 measurements spanning 99 days, net -471. 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,848–10,462 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
12 Nov 2026, 22:519,920+1
9 Nov 2026, 01:419,919-8
5 Nov 2026, 17:019,927-6
3 Nov 2026, 00:109,933-12
30 Oct 2026, 16:159,945-10
27 Oct 2026, 22:259,955-6
24 Oct 2026, 16:159,961-14
21 Oct 2026, 16:099,975-9
18 Oct 2026, 01:479,984-11
14 Oct 2026, 22:359,995-11
13 Oct 2026, 12:2810,006-28
9 Oct 2026, 08:3810,034-16
4 Oct 2026, 22:0210,050-48
27 Sept 2026, 15:5810,098-36
17 Sept 2026, 16:1710,134-8
15 Sept 2026, 17:2110,142-5
14 Sept 2026, 00:2110,147-8
12 Sept 2026, 08:5710,155-20
10 Sept 2026, 04:5810,175-19
7 Sept 2026, 02:0110,194first reading

Engagement

88 posts held, back to 26 July 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.54%
avg views ÷ 9,920 subscribers
Avg views / post
451
21 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
21
of 88 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 15 November 2026
Posts held88 (26 July 2026 – 15 November 2026)
Views total9,464
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 12:27 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

Photos
≈4,690
Videos
≈1,900
Links
≈6,050

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 21 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).

15 Nov 2026, 22:51 UTC189 viewsread 17 November 2026
Photo

🟠 بت تایم ۹۰، این بار در BETTIME VIP! جدید ترین اخبار و بونوس‌ها بت تایم رو از این به بعد در کانال جدیدمون دنبال کنید. 🟠 به جمع ما در بت تایم VIP بپیوندید! 🔗 @Bettime90Vip 🔗 @Bettime90Vip

30 Oct 2026, 09:50 UTC≈1,130 viewsread 17 November 2026
Photo

⚽️ لالیگا اسپانیا - هفته ۱۱ ویارئال 🆚 اسپانیول 📆 جمعه ۸ آبان ماه,ساعت ۲۳:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

30 Oct 2026, 07:55 UTC956 viewsread 17 November 2026
Photo

⚽️ لیگ برتر ایران - هفته ۱۱ خیبر خرم آباد 🆚 سپاهان 📆 جمعه ۸ آبان ماه,ساعت ۱۷:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

29 Oct 2026, 07:54 UTC754 viewsread 17 November 2026
Photo

⚽️ لیگ حرفه‌ای عربستان - هفته ۱۲ النصر 🆚 الخلود 📆 پنجشنبه ۷ آبان ماه,ساعت ۲۱:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

28 Oct 2026, 20:34 UTC662 viewsread 17 November 2026
Photo

⚽️ مسابقات فوتبال 📆 پنجشنبه ۷ آبان ماه در «بت تایم نود» به صورت زنده تماشا کنید و پیش‌بینی کنید 🎰 پیش‌بینی با بالاترین ضرایب 💵 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

27 Oct 2026, 07:04 UTC503 viewsread 17 November 2026
Photo

⚽️ لیگ نخبگان آسیا - گروهی شباب الاهلی 🆚 استقلال 📆 سه شنبه ۵ آبان ماه,ساعت ۱۹:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

25 Oct 2026, 20:30 UTC473 viewsread 17 November 2026
Photo

⚽️ مسابقات فوتبال 📆 دوشنبه ۴ آبان ماه در «بت تایم نود» به صورت زنده تماشا کنید و پیش‌بینی کنید 🎰 پیش‌بینی با بالاترین ضرایب 💵 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

25 Oct 2026, 18:02 UTC446 viewsread 17 November 2026
Photo

⚽️ لالیگا اسپانیا - هفته ۱۰ بارسلونا 🆚 رئال مادرید 📆 یکشنبه ۳ آبان ماه,ساعت ۲۳:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

25 Oct 2026, 08:44 UTC396 viewsread 17 November 2026
Photo

⚽️ لیگ برتر انگلیس - هفته ۸ منچستریونایتد 🆚 بورنموث 📆 یکشنبه ۳ آبان ماه,ساعت ۱۷:۳۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

25 Oct 2026, 07:01 UTC328 viewsread 17 November 2026
Photo

⚽️ لیگ برتر ایران - هفته ۱۰ پرسپولیس 🆚 فولاد 📆 یکشنبه ۳ آبان ماه,ساعت ۱۶:۴۵ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

24 Oct 2026, 20:32 UTC331 viewsread 17 November 2026
Photo

⚽️ مسابقات فوتبال 📆 یکشنبه ۳ آبان ماه در «بت تایم نود» به صورت زنده تماشا کنید و پیش‌بینی کنید 🎰 پیش‌بینی با بالاترین ضرایب 💵 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

24 Oct 2026, 12:00 UTC326 viewsread 17 November 2026
Photo

⚽️ لالیگا اسپانیا - هفته ۱۰ والنسیا 🆚 ویارئال 📆 شنبه ۲ آبان ماه,ساعت ۲۰:۰۰ در «بت تایم نود» به صورت زنده تماشا و پیش‌بینی کنید 🏦 پیش‌بینی با بالاترین ضرایب 💰 تا ۳۵٪ کش بک روزانه ▶️ پخش زنده اختصاصی 📱 ٪۱۰۰ بونوس با واریز از طریق تتر و ترون 🪑 📱 آدرس جدید بت تایم نود 🟠 📱Android App 📱 Instagram 🎥 Youtube 💙 Telegram

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

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

گلف بت GOLFBET
@Golfbetoriginal · 41,099
Telegram ranks this channel #24 of 59 here — alongside 58 others — read 30 August 2026
BetForward بت فوروارد
@betforward · 871,531
Telegram ranks this channel #24 of 84 here — alongside 83 others — read 17 August 2026
BerryBet IR Official
@BerryBetOfficial · 22,657
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 30 September 2026
تک‌بت | Takbet
@takbetiran · 40,380
Telegram ranks this channel #39 of 85 here — alongside 84 others — read 30 August 2026
سایت جهانی Maf Bet
@mafbetoriginal · 17,600
Telegram ranks this channel #46 of 70 here — alongside 69 others — read 5 September 2026
PMXchange | پی ام ایکس چنج
@pmxchangee · 50,027
Telegram ranks this channel #71 of 72 here — alongside 71 others — read 15 September 2026

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

“Bettime90 | بت تایم ۹۰” (@bettime90), 9,920 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bettime90.

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.