⚠️Değerli Üyelerimiz; 🔥Göstermiş olduğunuz ilgiden dolayı teşekkür ederiz. Kodumuz 15 dakikada tükenmiştir🚀 Her gece yeni etkinliklerden haberdar olmak için bildirimleri açmayı unutmayınız❗️❗️
❤1

Channel
@casinratg
On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Polls · Cite this entry
1,891subscribers
-26,154 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002342440102 |
|---|---|
| Type | Channel |
| Username | @casinratg |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 November 2026 |
| Measurements held | 45 |
| Confirmed unchanged | 1 time, most recently 21 November 2026 |
| On Telegram | t.me/casinratg |
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 99% 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.
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.
Posts published here appear in near-verbatim form 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @casinratg/7544 · this entry7 Aug 2026, 11:25 UTC | @aleysulive/3867028 Aug 2026, 09:44 UTC | 1.00 | 21 days |
| @casinratg/7872 · this entry24 Aug 2026, 09:17 UTC | @aleysulive/3855824 Aug 2026, 14:50 UTC | 1.00 | 5.5 hours |
| @casinratg/7893 · this entry25 Aug 2026, 09:28 UTC | @aleysulive/3858725 Aug 2026, 14:52 UTC | 1.00 | 5.4 hours |
| @casinratg/7999 · this entry29 Aug 2026, 12:27 UTC | @aleysulive/3870929 Aug 2026, 13:41 UTC | 1.00 | 74 minutes |
| @casinratg/8036 · this entry30 Aug 2026, 21:01 UTC | @aleysulive/3878631 Aug 2026, 09:48 UTC | 1.00 | 13 hours |
| @casinratg/8066 · this entry1 Sept 2026, 10:43 UTC | @aleysulive/388361 Sept 2026, 15:52 UTC | 1.00 | 5.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @aleysulive | 8 (8/8 hand-verifiable sample passed) | 0.99 | 5.5 hours | this entry (7–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. 1 of the 1 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 807 comparable posts for this entry, running 6 August 2026 to 8 October 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.
Recorded under the key clone_source, last confirmed 22 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Nov 2026, 11:04 | 1,891 | +296 |
| 16 Nov 2026, 11:06 | 1,595 | +234 |
| 10 Nov 2026, 15:46 | 1,361 | +99 |
| 7 Nov 2026, 07:00 | 1,262 | +53 |
| 4 Nov 2026, 15:50 | 1,209 | +95 |
| 1 Nov 2026, 10:46 | 1,114 | +267 |
| 26 Oct 2026, 10:37 | 847 | +322 |
| 20 Oct 2026, 11:39 | 525 | +275 |
| 13 Oct 2026, 07:07 | 250 | -41,180 |
| 8 Oct 2026, 23:40 | 41,430 | +3,392 |
| 4 Oct 2026, 15:59 | 38,038 | +5,455 |
| 26 Sept 2026, 11:58 | 32,583 | +2,675 |
| 19 Sept 2026, 12:58 | 29,908 | +220 |
| 17 Sept 2026, 04:37 | 29,688 | +146 |
| 15 Sept 2026, 05:56 | 29,542 | +166 |
| 13 Sept 2026, 14:21 | 29,376 | +7 |
| 11 Sept 2026, 15:39 | 29,369 | +205 |
| 8 Sept 2026, 22:15 | 29,164 | +243 |
| 5 Sept 2026, 12:18 | 28,921 | +54 |
| 3 Sept 2026, 15:18 | 28,867 | first reading |
1,130 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 98 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 1,130 posts for this entry, the most recent from 8 October 2026. An engagement rate over an empty window would be a number about nothing.
7,174 reactions across 287 posts, in 31 distinct kinds. The most used accounts for 34.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,495 | 34.8% | |
| 🥰 | 1,452 | 20.2% | |
| 🎉 | 1,173 | 16.4% | |
| 👍 | 1,075 | 15.0% | |
| 🔥 | 570 | 7.95% | |
| 👏 | 173 | 2.41% | |
| 😁 | 148 | 2.06% | |
| 🤔 | 25 | 0.348% | |
| ⚡ | 9 | 0.125% | |
| 🏆 | 6 | 0.084% | |
| 👎 | 5 | 0.07% | |
| 💯 | 5 | 0.07% | |
| 😡 | 5 | 0.07% | |
| 🆒 | 4 | 0.056% | |
| 💊 | 3 | 0.042% | |
| 😈 | 3 | 0.042% | |
| 😎 | 3 | 0.042% | |
| 🍾 | 2 | 0.028% | |
| 🎃 | 2 | 0.028% | |
| 👀 | 2 | 0.028% | |
| 11 further kinds | 14 | 0.195% |
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 304 of the 1,000 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 7,174 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 13 August 2026 to 8 October 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.
⚠️Değerli Üyelerimiz; 🔥Göstermiş olduğunuz ilgiden dolayı teşekkür ederiz. Kodumuz 15 dakikada tükenmiştir🚀 Her gece yeni etkinliklerden haberdar olmak için bildirimleri açmayı unutmayınız❗️❗️
❤1
🔥Admin'in Ateşi Yükseldi ⚠️ 🕊Gece Kuşlarına Özel Kod Yolda Ama önce emojileri görelim, bakalım gece tayfası ne durumda ❗️❗️💰
❤15🔥2
CASİNRA’da fırsatlar net, oranlar yüksek! 💥 🇺🇸 NBA Sahnesinde Kazanç Çanları Çalıyor! 🔔 Favorin karşılaşman hangisi bu gece ⁉️ PARKENİN RİTMİ
Volkan Bey kazancını aldı, sıra yeni hikâyede… 720 TL → ♦️♦️🔺.🔺🔺🔺 🔺♦️ Masaya Yıldırım Gibi Düştü! ⚡️ Şimdi gir, şansını sen dene. 🎰 KAZANÇ GECESİNE KULAK VER
🌟 NAKİT ÖDÜLLERLE DONATILAN RAFELEK BAŞLIYOR! Çarkı çevir, sürpriz ödülünü yakala! 🎁 KAZANDIRAN KODLAR⬇️ 6CLM-Q928M5 Q4RK-JXFKG7 85MU-FSUW98 JAN5-T76JHM YXDK-HQX6XH 7KC9-KHALHD AKHW-QUNTP4 Q5TQ-2UNDEH LLN9-5RMEPX CND7-9RZ5E3 3BHD-6E5VVH CFCW-DNBGDM 8MUC-WLTZCB 9N7C-EKLWGU ZAR4-W4G9X8 54X2-XHVSGF PXSE-2GDEAS 5G3Z-WWQVD5 MDXB-C863DF Q5BL-ML8FLD ÇARK LİNKİ: Ra Felek
❤1
🍀 Bugün şansın peşinden koşma, bırak o sana yetişsin! 🔥 Günün radarında HOT TO BURN var! Makaraları döndür, oyunun sürprizlerini yakala; bugünün şanslı ismi neden sen olmayasın❓🥂 GÜNÜN ŞANSLILARI
🎁 CASİNRA’NIN KODU KAZANDIRMAYA HAZIR! Büyülü Kod: CSR50TG SPIN DEĞERİ —> 1️⃣0️⃣🔠🔠 Min-Max. Çekim: 🔢❎🔢🔢🔢🅰️🅰️ 🍀 Çekim için —> 500 TL yatırım yapılıp çekim emri verilmeli ardından ana para çevrimi yapılmalı 🍀 2000 TL kazancın hesaba yansıması için kazancınızın 4000 TL olması gerekli aksi halde elenirsiniz!
❤1
▶️KOD GÖZLEYEN ÜYELERİMİZ HAZIR MI ⁉️ 🎁 CASİNRA’DAN 1000 TL DEĞERİNDE FREESPIN HEDİYE! ⚡️ 🔞 Sweet Bonanza 🔞Gates of Olympus oyununda 1000₺ yaparak çekim verebilirsin! Ama önce ❤️ emojilerini alalım!
❤22
🔉 Admin araya giriyor… Yatırım yapmayı düşünüyorsan zamanlamayı iyi seç derim! 😏 Çünkü Happy Hour’da yatırımına 🔣1️⃣0️⃣0️⃣ 🅱️🔠🔠🔠🔠 ekleniyor‼️ ⭐ VipPay havale ile 250 TL yatırım Casinra’da! AVANTAJLARI YAKALA
❤1
🏹 Casinra Tahminini Yaptı! 1️⃣ ➖ 1️⃣ Sıra sende‼️🥂 ⚔️ Chat alanına kuponunu bırak puanların ile rakiplerine fark at‼️ 👑 1.000 TL Freespin zirvede sahibini bekliyor!
Sticker, posted without a caption
Sence korner sayacı nerede duracak⁉️ Yalnızca golleri saymıyoruz; korner çizgisi de masada❗️ 🔥 9.5 ÜST: 1️⃣🔣8️⃣5️⃣ ⚡️ 9.5 ALT: 1️⃣🔣8️⃣5️⃣ ZAMAN AZALDI
Showing the 12 most recent of 1,130 posts we hold for @casinratg. 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.
@casinratg edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 6 most recent of 12 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.
⏰Gol Sayacı Hangisinde Hızlanacak ⁉️
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Montella maçtan sonra istifa edecek mi ⁉️
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
KAZANAN KİM OLUR ⁉️
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Kırmızı Kart Şöleni Hangi Maçta Yaşanır ⁉️
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Hangi maçta daha çok gol olur ⁉️
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Kazandıran senaryo hangisi olacak ⁉️
Shares as published. 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 1,000 most recent posts we hold (the sample is capped at 1,000), published 13 August 2026 to 8 October 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.
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 21 November 2026 — this entry's latest reading, not the date you are reading this.
“casinratg” (@casinratg), 1,891 subscribers as measured 21 November 2026. Telegram Register, tgregister.com/channel/casinratg.
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.