Channel
Trade with Anmol
@hedgekingofficial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,104subscribers
-177 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001728317973 |
|---|---|
| Type | Channel |
| Username | @hedgekingofficial |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/hedgekingofficial |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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 |
|---|---|---|
| 3 Nov 2026, 22:58 | 2,104 | -3 |
| 31 Oct 2026, 17:20 | 2,107 | -1 |
| 28 Oct 2026, 09:48 | 2,108 | -11 |
| 25 Oct 2026, 20:30 | 2,119 | -7 |
| 23 Oct 2026, 01:25 | 2,126 | -11 |
| 19 Oct 2026, 16:55 | 2,137 | -11 |
| 16 Oct 2026, 09:30 | 2,148 | -10 |
| 13 Oct 2026, 00:41 | 2,158 | +7 |
| 6 Oct 2026, 13:57 | 2,151 | -11 |
| 29 Sept 2026, 22:55 | 2,162 | -22 |
| 19 Sept 2026, 09:39 | 2,184 | -17 |
| 18 Sept 2026, 21:47 | 2,201 | no change |
| 14 Sept 2026, 21:20 | 2,201 | -4 |
| 11 Sept 2026, 07:38 | 2,205 | -15 |
| 6 Sept 2026, 07:21 | 2,220 | -8 |
| 2 Sept 2026, 05:47 | 2,228 | -7 |
| 30 Aug 2026, 11:48 | 2,235 | -3 |
| 27 Aug 2026, 11:15 | 2,238 | -8 |
| 24 Aug 2026, 17:38 | 2,246 | -7 |
| 20 Aug 2026, 19:27 | 2,253 | 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.
@skyeducationofficial · 41,850
Telegram ranks this channel #24 of 42 here — alongside 41 others — read 10 September 2026
@zertrade · 179,221
Telegram ranks this channel #32 of 50 here — alongside 49 others — read 11 August 2026
@hjparamiltrian · 39,276
Telegram ranks this channel #34 of 47 here — alongside 46 others — read 30 August 2026
@UPSC_SSC_BPSC_GK_GS_QUIZ · 148,239
Telegram ranks this channel #63 of 71 here — alongside 70 others — read 12 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Trade with Anmol” (@hedgekingofficial), 2,104 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/hedgekingofficial.
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.