Channel
SAS ZIN13 || CASINOS🎲🎰 / PARIS SPORTIF ⚽️🏀🥎
@sasbotluckyjet
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
5,608subscribers
-290 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001834563712 |
|---|---|
| Type | Channel |
| Username | @sasbotluckyjet |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/sasbotluckyjet |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 01:20 | 5,608 | -31 |
| 7 Sept 2026, 14:16 | 5,639 | -35 |
| 2 Sept 2026, 12:04 | 5,674 | -27 |
| 30 Aug 2026, 19:12 | 5,701 | -29 |
| 30 Aug 2026, 11:56 | 5,730 | no change |
| 27 Aug 2026, 17:45 | 5,730 | -12 |
| 24 Aug 2026, 17:38 | 5,742 | -35 |
| 21 Aug 2026, 00:24 | 5,777 | -25 |
| 18 Aug 2026, 03:11 | 5,802 | -27 |
| 14 Aug 2026, 20:19 | 5,829 | -30 |
| 11 Aug 2026, 12:26 | 5,859 | -29 |
| 8 Aug 2026, 07:23 | 5,888 | -10 |
| 7 Aug 2026, 11:09 | 5,898 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@jeuxcasino2 · 34,543
Telegram ranks this channel #14 of 53 here — alongside 52 others — read 2 September 2026
@marcodinero · 43,573
Telegram ranks this channel #14 of 50 here — alongside 49 others — read 28 August 2026
@ROVASOFFICIEL · 63,086
Telegram ranks this channel #17 of 58 here — alongside 57 others — read 21 August 2026
@tavoprono01 · 32,566
Telegram ranks this channel #19 of 59 here — alongside 58 others — read 5 September 2026
@YANNPCSOFFICIELLE · 37,037
Telegram ranks this channel #20 of 58 here — alongside 57 others — read 1 September 2026
@Chez20KK · 34,417
Telegram ranks this channel #21 of 53 here — alongside 52 others — read 3 September 2026
@GHOSTOFFI54 · 83,604
Telegram ranks this channel #23 of 62 here — alongside 61 others — read 18 August 2026
@yoanpromax · 36,337
Telegram ranks this channel #27 of 61 here — alongside 60 others — read 1 September 2026
@bobochylor · 85,825
Telegram ranks this channel #33 of 66 here — alongside 65 others — read 17 August 2026
@walleroff · 56,396
Telegram ranks this channel #42 of 69 here — alongside 68 others — read 22 August 2026
@lionel_pcsofficiel1 · 636,322
Telegram ranks this channel #43 of 74 here — alongside 73 others — read 14 August 2026
This channel appears in 11 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 September 2026 — this entry's latest reading, not the date you are reading this.
“SAS ZIN13 || CASINOS🎲🎰 / PARIS SPORTIF ⚽️🏀🥎” (@sasbotluckyjet), 5,608 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/sasbotluckyjet.
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.