Channel

گروه بت | گپ بت | گروه همفکری بت | گپ همفکری بت | گروه شرطبندی بت | گروه پیشبینی بت | گپ شرطبندی بت | گپ پیشبینی بت | گروه همفکر

@iran_top_bet

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

1,143subscribers

-30,949 since we began measuring on 18 August 2026

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

Register entry

Topic

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 10 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.

Growth

Engagement

62 posts held, back to 26 November 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 35 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 62 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime

3m 45s

Average length

32s

Measured directly from 7 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.

Recent posts

Showing the 12 most recent of 62 posts we hold for @iran_top_bet. 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 3 posts on @iran_top_bet 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

22 August 2026

Most recent seen missing

1 September 2026

Median time before seen missing

3 days

Seen missing in the last 30 days

0

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

“گروه بت | گپ بت | گروه همفکری بت | گپ همفکری بت | گروه شرطبندی بت | گروه پیشبینی بت | گپ شرطبندی بت | گپ پیشبینی بت | گروه همفکر” (@iran_top_bet), 1,143 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/iran_top_bet.

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.