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 8 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 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.
Views and reactions moved apart
On 2 of the 84 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0086 reactions per view.
Each interval, as we read it — views and reactions before and after
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 12 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.
Growth
9 measurements spanning 7 days, net +16,186. 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 1,085,859–1,116,080 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 15:43
1,112,593
+9,680
11 Aug 2026, 16:03
1,102,913
+13,567
10 Aug 2026, 16:01
1,089,346
-432
9 Aug 2026, 12:38
1,089,778
-3,159
8 Aug 2026, 09:03
1,092,937
-2,739
7 Aug 2026, 06:16
1,095,676
-1,320
6 Aug 2026, 09:45
1,096,996
+589
6 Aug 2026, 03:00
1,096,407
no change
6 Aug 2026, 02:53
1,096,407
first reading
Engagement
100 posts held, back to 4 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 21 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
3.21%
avg views ÷ 1,112,593 subscribers
Avg views / post
35,700
100 posts measured
Reaction rate
1.16%
reactions ÷ views · ER floor
Posts in window
100
of 100 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
Window
Rolling 30 days · latest post in window 12 August 2026
Posts held
100 (4 August 2026 – 12 August 2026)
Views total
3,572,800
Reactions total
41,299
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
13 Aug 2026, 00:50 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,310
Videos
≈293
Links
≈11,700
Lifetime counters from Telegram’s own channel header, read 12 August 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 84 of this channel’s own posts over the last 30 days: across 69of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 7.7 hours of being posted; a typical post has already reached 19.6% of its 24-hour view count within the first hour, and 64.0% within the first six; the median 24-hour reach across those posts is 26,900 views — 2.42% of this channel’s own subscriber count (90th percentile 32,050).
8 most recently posted, with a view-velocity reading
60 minutes: 7,653 interp. → 3.0 hours: 14,700 → 6.0 hours: 21,000still climbing at last reading
not yet at 24h
1.9 hoursprovisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
41,291 reactions across 98 posts, in 9 distinct kinds. The most used accounts for 39.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
16,297
39.5%
👍
12,871
31.2%
💔
5,571
13.5%
❤
2,994
7.25%
👎
2,375
5.75%
🤯
510
1.24%
👏
301
0.729%
❤🔥
285
0.69%
😁
87
0.211%
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 100 of the 100 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 41,299reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 100 most recent posts we hold, published 4 August 2026 to 12 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.
🤩🤩🤩🤩🤩🤩🤩🤩
🎲 #تختهنرد فقط یه بازی نیست، یه جنگ مغزه!
اگه فکر میکنی شانسی میبری، بیا وسط!
📱 تو وین اسپورت، پشت هر تاس یه نبرد جدیه!
💲 جایزه بزن، حریف رو بچرخون، شاه تخته شو!
🎁 شارژ هدیه بدون قید و شرط ۵٪
🎁 بونوس تقویت ضرایب ورزشی تا ۵۰٪
🎁 کش بک (برگشت پول) ۳تا ۳۵٪
🎁 ریک بک های هفتگی پوکر تا ۲۰٪
♟️ بازی کن، ببَر، پادشاه شو! 👇
http://Winspo7080.com/?registr=1
A21
⚡️کانال تلگرام و جوایز دلاری 👇
https://telegram.me/jo…
یکی از چالشهای اصلی زنان باسواد و تحصیلکرده، زندگی مشترک با مردی پولدار اما کمسواده!
این موضوع در اوایل رابطه که هردو درگیر هیجانند و سفرها آنتالیا و پاریس و ... خودشو نشون نمیده!
مشکل دقیقاً وقتی شروع میشه که فصل هیجانی تمام میشه و نوبت به همفکری و هم اندیشی میرسه.
پروکسی | پروکسی
@DiamondProxy
لطفا لطفا لطفا لطفا
در استخرهای با پوشش ژٸوممبران(استخرهای ذخیره آب کشاورزی) شنا نکنید!
احتمال غرق شدن تو این استخرا مخصوصا اگر تنها باشید خیلی خیلی خیلی زیاده!
امروز همکار جوون ما که برای نجات یک حیوون پریده بود داخل استخر غرق شد و فوت کرد😭
✍ماه آفرید
پروکسی | پروکسی
@DiamondProxy
🇩🇪آپ اندروید سایت جهانی Melbet💥
🎁بونوس ورزشی هر چهارشنبه🔥
💸واریز و برداشت متنوع💵
⭕️بدون نیاز به فیلتر شکن⭕️
🎁کد هدیه ثبت نام Melbet90 ✌️
✔https://t.me/+x60dZGAgXTUxM2U0
👀دنبال سایت معتبر برای شرطبندی میگردید⁉️
🎲سایت بین المللی و معتبر Melbet
👍😁😊🙂
🥇واریز و برداشت ارزی و ریالی‼️
🔥بونوس 100% اولین واریز‼️
⚽️بونوس ورزشی هرچهارشنبه‼️
🆗کازینو و انفجار با ضرایب جهانی‼️
🎁کد هدیه ثبت نام :Melbet90
🇩🇪دانلود اپلیکیشن MELBET👉
🔗لینک وبسایت👉
⭕️جهت استفاده از vpn از IP های آسیایی یا کانادا استفاده کنید.🇨🇦 🇹🇷
G21
✔ https://t.me/+x60dZGAgXTUxM2U0
مملکت جوری شده که
اونی که به زمانی میرفت سفر خارج، دیگه میره شمال و کیش
اونی که میرفت شمال میره رستوران،
اونی که میرفت رستوران میره کافه،
اونی که می رفت کافه میشینه خونه چایی میخوره
✍مسافر
پروکسی | پروکسی
@DiamondProxy
🆕 اپلیکیشن MelBet 🔄
🎁 کد هدیه 100 دلاری: Sport100
🤝 اسپانسر رسمی جام جهانی
🔵 کاملترین برنامه موبایل
☄️ صرافی معتبر
🤖 ربات راهنما
🇮🇷 برای تغییر زبان برنامه، زبان موبایل خود را تغییر دهید.
✅ ورود به اپلیکیشن بدون فیلترشکن
❤3👍1
Showing the 12 most recent of 100 posts we hold for @diamondproxy. 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.
Citation-graph rank
Citation-graph rank — 746,645 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
پروکسی | Proxy MTProto @mtp_roto · 1,643,491 Telegram ranks this channel #19 of 85 here — alongside 84 others — read 8 August 2026
Proxy MTProto | پروکسی @NoteProxy · 146,391 Telegram ranks this channel #30 of 88 here — alongside 87 others — read 13 August 2026
Next Gen Proxy @NextGenProxy · 172,868 Telegram ranks this channel #32 of 74 here — alongside 73 others — read 12 August 2026
Proxy MTProto | پروکسی @Chrome_Proxy · 503,741 Telegram ranks this channel #41 of 89 here — alongside 88 others — read 9 August 2026
Hotspot Proxy @hotspotproxy · 216,904 Telegram ranks this channel #44 of 79 here — alongside 78 others — read 11 August 2026
پروکسی|Hi Proxy @hi_proxi · 204,859 Telegram ranks this channel #47 of 79 here — alongside 78 others — read 11 August 2026
پروکسی ملی | Proxy MTProto @Poroximel · 280,253 Telegram ranks this channel #51 of 75 here — alongside 74 others — read 10 August 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
4 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“« Diamond MTProxy | پروکسی ایرانسل پروکسی همراه اول »” (@diamondproxy), 1,112,593 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/diamondproxy.
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.
