Channel
HAKIMI NUMBER ONE π
@hakimi1xbet
On this record: Previous handles Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
19,821subscribers
+41 since we began measuring on 12 August 2026
Risers and fallers across the register Β· movement among entries of 10,000β31,623.
Register entry
| Telegram ID | -1001630824520 |
|---|---|
| Type | Channel |
| Username | @hakimi1xbet |
| Created | Between 1 December 2021 and 30 April 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/hakimi1xbet |
Previous handles
@hakimi1xbet was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today β only that this channel no longer does.
held 16 August 2026 β 16 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 03:27 | 19,821 | -36 |
| 28 Aug 2026, 03:25 | 19,857 | -34 |
| 26 Aug 2026, 23:57 | 19,891 | -32 |
| 25 Aug 2026, 21:28 | 19,923 | -45 |
| 25 Aug 2026, 00:37 | 19,968 | -47 |
| 23 Aug 2026, 13:16 | 20,015 | -99 |
| 21 Aug 2026, 20:16 | 20,114 | -58 |
| 20 Aug 2026, 13:48 | 20,172 | -42 |
| 19 Aug 2026, 10:37 | 20,214 | +70 |
| 18 Aug 2026, 12:22 | 20,144 | +108 |
| 17 Aug 2026, 10:45 | 20,036 | +149 |
| 16 Aug 2026, 19:34 | 19,887 | no change |
| 15 Aug 2026, 17:24 | 19,887 | +122 |
| 14 Aug 2026, 05:17 | 19,765 | -6 |
| 12 Aug 2026, 21:08 | 19,771 | -9 |
| 12 Aug 2026, 18:45 | 19,780 | first reading |
Engagement
No public post preview. We read this entry on 16 August 2026 and Telegram serves no public post stream for it β the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
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.
@dibpomo Β· 307,187
Telegram ranks this channel #27 of 74 here β alongside 73 others β read 15 August 2026
@sogorofiiix Β· 61,241
Telegram ranks this channel #54 of 72 here β alongside 71 others β read 22 August 2026
@rafik130b Β· 107,577
Telegram ranks this channel #56 of 76 here β alongside 75 others β read 14 August 2026
@FENOMENOE Β· 80,004
Telegram ranks this channel #60 of 73 here β alongside 72 others β read 18 August 2026
@tawqo3atrafa Β· 52,494
Telegram ranks this channel #66 of 72 here β alongside 71 others β read 24 August 2026
@Arthur_PLbets Β· 57,879
Telegram ranks this channel #70 of 73 here β alongside 72 others β read 22 August 2026
@BETXBET_MOROCCO Β· 154,199
Telegram ranks this channel #71 of 84 here β alongside 83 others β read 12 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.
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 29 August 2026 β this entry's latest reading, not the date you are reading this.
βHAKIMI NUMBER ONE πβ (@hakimi1xbet), 19,821 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/hakimi1xbet.
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.