Channel
RK_Chaarts
@RK_Charts
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,309subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001443821510 |
|---|---|
| Type | Channel |
| Username | @RK_Charts |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/RK_Charts |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 |
|---|---|---|
| 4 Nov 2026, 13:06 | 2,309 | -3 |
| 1 Nov 2026, 18:19 | 2,312 | -3 |
| 26 Oct 2026, 13:46 | 2,315 | +5 |
| 23 Oct 2026, 21:16 | 2,310 | +1 |
| 21 Oct 2026, 02:07 | 2,309 | -5 |
| 15 Oct 2026, 13:56 | 2,314 | -1 |
| 12 Oct 2026, 11:44 | 2,315 | -4 |
| 5 Oct 2026, 15:15 | 2,319 | -6 |
| 18 Sept 2026, 18:59 | 2,325 | +1 |
| 17 Sept 2026, 02:07 | 2,324 | no change |
| 14 Sept 2026, 12:22 | 2,324 | -3 |
| 11 Sept 2026, 07:55 | 2,327 | -1 |
| 6 Sept 2026, 09:01 | 2,328 | +3 |
| 30 Aug 2026, 01:55 | 2,325 | -4 |
| 26 Aug 2026, 21:34 | 2,329 | -2 |
| 23 Aug 2026, 14:36 | 2,331 | -4 |
| 20 Aug 2026, 02:08 | 2,335 | +2 |
| 17 Aug 2026, 10:03 | 2,333 | -3 |
| 13 Aug 2026, 13:49 | 2,336 | -4 |
| 10 Aug 2026, 19:54 | 2,340 | 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.
@bullss · 120,778
Telegram ranks this channel #11 of 89 here — alongside 88 others — read 14 August 2026
@chartbank · 64,233
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 21 August 2026
@aatradingblog · 22,762
Telegram ranks this channel #14 of 75 here — alongside 74 others — read 18 September 2026
@umeshsharmachartanalysis · 38,264
Telegram ranks this channel #58 of 87 here — alongside 86 others — read 30 August 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“RK_Chaarts” (@RK_Charts), 2,309 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/RK_Charts.
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.