Channel
Amir crypto trade🐋
@amircryptotrade
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,142subscribers
+16 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 | -1002133044748 |
|---|---|
| Type | Channel |
| Username | @amircryptotrade |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/amircryptotrade |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 08:56 | 2,142 | -6 |
| 19 Sept 2026, 02:06 | 2,148 | no change |
| 14 Sept 2026, 12:58 | 2,148 | -8 |
| 10 Sept 2026, 18:57 | 2,156 | +6 |
| 6 Sept 2026, 02:55 | 2,150 | +4 |
| 1 Sept 2026, 12:34 | 2,146 | -8 |
| 29 Aug 2026, 14:55 | 2,154 | -9 |
| 27 Aug 2026, 01:17 | 2,163 | +6 |
| 24 Aug 2026, 03:24 | 2,157 | +20 |
| 20 Aug 2026, 18:03 | 2,137 | -20 |
| 17 Aug 2026, 11:03 | 2,157 | +4 |
| 14 Aug 2026, 07:58 | 2,153 | +23 |
| 11 Aug 2026, 00:21 | 2,130 | +2 |
| 8 Aug 2026, 09:48 | 2,128 | +2 |
| 7 Aug 2026, 12:55 | 2,126 | 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.
@ShinobiSignals · 32,532
Telegram ranks this channel #57 of 75 here — alongside 74 others — read 4 September 2026
@alexsetandforget · 213,024
Telegram ranks this channel #59 of 80 here — alongside 79 others — read 11 August 2026
@cuetipscharts · 34,339
Telegram ranks this channel #65 of 76 here — alongside 75 others — read 3 September 2026
@yoforexgold · 119,861
Telegram ranks this channel #66 of 74 here — alongside 73 others — read 12 August 2026
@planfomo · 24,610
Telegram ranks this channel #71 of 78 here — alongside 77 others — read 15 September 2026
This channel appears in 5 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Amir crypto trade🐋” (@amircryptotrade), 2,142 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/amircryptotrade.
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.