Channel
Drkarimibitcoin
@drkarimibitcoin
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,131subscribers
+696 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001772360869 |
|---|---|
| Type | Channel |
| Username | @drkarimibitcoin |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/drkarimibitcoin |
Topic
Crypto & trading — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 00:15 | 5,131 | +269 |
| 2 Nov 2026, 14:35 | 4,862 | -41 |
| 30 Oct 2026, 13:18 | 4,903 | -44 |
| 27 Oct 2026, 11:04 | 4,947 | -54 |
| 24 Oct 2026, 07:01 | 5,001 | +22 |
| 20 Oct 2026, 22:06 | 4,979 | -46 |
| 17 Oct 2026, 23:05 | 5,025 | +274 |
| 14 Oct 2026, 20:57 | 4,751 | +132 |
| 11 Oct 2026, 18:42 | 4,619 | -48 |
| 4 Oct 2026, 23:57 | 4,667 | +70 |
| 25 Sept 2026, 22:59 | 4,597 | -45 |
| 17 Sept 2026, 12:20 | 4,642 | -13 |
| 13 Sept 2026, 14:00 | 4,655 | +43 |
| 9 Sept 2026, 19:40 | 4,612 | -21 |
| 4 Sept 2026, 05:21 | 4,633 | +55 |
| 2 Sept 2026, 23:12 | 4,578 | no change |
| 31 Aug 2026, 08:24 | 4,578 | +31 |
| 28 Aug 2026, 09:12 | 4,547 | +45 |
| 24 Aug 2026, 23:57 | 4,502 | +11 |
| 21 Aug 2026, 05:37 | 4,491 | 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.
@ariatraderofficial · 20,290
Telegram ranks this channel #42 of 87 here — alongside 86 others — read 26 September 2026
@holding_negin · 101,972
Telegram ranks this channel #53 of 89 here — alongside 88 others — read 15 August 2026
@arman_futures · 99,690
Telegram ranks this channel #65 of 79 here — alongside 78 others — read 13 August 2026
@samsamitrading · 19,462
Telegram ranks this channel #68 of 92 here — alongside 91 others — read 4 October 2026
This channel appears in 4 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Drkarimibitcoin” (@drkarimibitcoin), 5,131 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/drkarimibitcoin.
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.