Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 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 3 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)
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
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. 10 of the 10 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 204 comparable posts for this entry, running 7 August 2026 to 9 September 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).
Recorded under the keys clone_copy · clone_source, last confirmed 11 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.
Growth
26 measurements spanning 76 days, net -49,286. 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 26
Measured (UTC)
Subscribers
Change
22 Oct 2026, 08:08
5
-1
8 Oct 2026, 15:39
6
+1
10 Sept 2026, 23:41
5
-50,748
8 Sept 2026, 02:56
50,753
-460
4 Sept 2026, 23:17
51,213
-257
3 Sept 2026, 10:17
51,470
-165
2 Sept 2026, 02:52
51,635
-165
1 Sept 2026, 03:05
51,800
-178
31 Aug 2026, 03:19
51,978
-182
30 Aug 2026, 00:13
52,160
-160
29 Aug 2026, 02:14
52,320
-201
27 Aug 2026, 23:23
52,521
-197
26 Aug 2026, 23:18
52,718
-163
25 Aug 2026, 23:24
52,881
-190
24 Aug 2026, 23:05
53,071
-541
23 Aug 2026, 09:12
53,612
-323
21 Aug 2026, 20:06
53,935
-299
20 Aug 2026, 15:25
54,234
-287
19 Aug 2026, 12:08
54,521
-303
18 Aug 2026, 10:17
54,824
first reading
Engagement
869 posts held, back to 6 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 64 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 869 posts for this entry, the most recent from 9 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
7m 49s
Average length
15s
Measured directly from 32 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.
#پیشنهاد_ویژه 🏆
رومابت ✅ بازی های اروپایی فوتبال رو پیشبینی کن و از هیجانش پول در بیار رفیق😍⚽️
ادرس ثبت نام رفقا 👇✅
https://RomaBet.Tech
https://RomaBet.Tech
ادرس کانال تلگرام 👇💠
@RomaBet_official
⚽️لیگ قهرمانان اروپا⚽️ و پیشنهاد ما رومابت
🇪🇸 #بارسلونا🆚 #فاینورد 🇳🇱
👈 رومابت دنیای آفر ها و بونوس های ورزشی و کازینویی میباشد ✅
با شرطبندی روی مسابقات 2.500.000.000 تومانی رومابت شوید 💵
💎 همین حالا وارد حساب کاربری شوید و شرط مورد نظر خود را ثبت کنید 👇
👑 https://RomaBet.Tech
✅کانال تلگرامی #رومابت 👇
r18
🔵 @RomaBet_official
تو به اندازه نور ماه قشنگی؛
تو به اندازه چارخونه های پاییز قشنگی؛
تو به اندازه برف دی ماه قشنگی؛
تو به اندازه خش خش برگ ها توی خیابون قشنگی؛
تو به اندازه کتاب نو قشنگی؛
تو به اندازه قهوه داغ قشنگی؛
تو به اندازه بوسه های یواشکی قشنگی؛
تو انقد قشنگی که نمیتونم دیگه حتی توصیفت کنم!'
Showing the 12 most recent of 869 posts we hold for @Baghalu. 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 @Baghalu 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
21 August 2026
Most recent seen missing
29 August 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
0
Polls
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 869 most recent posts we hold, published 6 August 2026 to 9 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
7
vacant every time we have ever looked
@Baghalu named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@sexlove named in 4 posts, 8 August 2026 – 3 September 2026
@asheqane named in 3 posts, 9 August 2026 – 3 September 2026
@gifsexi named in 2 posts, 8 August 2026 – 8 September 2026
@nudeart named in 1 post, 10 September 2026 – 10 September 2026
@bootikshop named in 1 post, 1 September 2026 – 1 September 2026
@hesikemide named in 1 post, 27 August 2026 – 27 August 2026
@horny named in 1 post, 21 August 2026 – 21 August 2026
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 22 October 2026 — this
entry's latest reading, not the date you are reading this.
“محافظ بغل” (@Baghalu), 5 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/Baghalu.
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.