Channel
Shahraadcoin
@shahraadcoin
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,454subscribers
-46 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 | -1001789975296 |
|---|---|
| Type | Channel |
| Username | @shahraadcoin |
| Description | کانال کریپتوکارنسی، تحلیل و اخبار https://shekareravand.com/ |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 September 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 15 |
| On Telegram | t.me/shahraadcoin |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 29 Sept 2026, 02:07 | 1,454 | no change |
| 25 Sept 2026, 22:35 | 1,454 | -6 |
| 17 Sept 2026, 01:39 | 1,460 | -3 |
| 13 Sept 2026, 02:41 | 1,463 | -5 |
| 8 Sept 2026, 21:22 | 1,468 | -5 |
| 3 Sept 2026, 09:28 | 1,473 | -1 |
| 31 Aug 2026, 04:48 | 1,474 | -1 |
| 28 Aug 2026, 10:06 | 1,475 | -1 |
| 25 Aug 2026, 03:44 | 1,476 | -2 |
| 21 Aug 2026, 11:04 | 1,478 | -5 |
| 18 Aug 2026, 05:22 | 1,483 | -4 |
| 15 Aug 2026, 03:26 | 1,487 | -6 |
| 11 Aug 2026, 18:21 | 1,493 | -6 |
| 8 Aug 2026, 08:32 | 1,499 | -1 |
| 7 Aug 2026, 23:28 | 1,500 | 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.
@cryptofarzad · 20,142
Telegram ranks this channel #7 of 82 here — alongside 81 others — read 28 September 2026
@nayabnet_vip · 30,538
Telegram ranks this channel #23 of 50 here — alongside 49 others — read 11 September 2026
@naeem_trader · 117,322
Telegram ranks this channel #28 of 87 here — alongside 86 others — read 15 August 2026
@ariatraderofficial · 20,623
Telegram ranks this channel #65 of 87 here — alongside 86 others — read 26 September 2026
@moinsl · 22,516
Telegram ranks this channel #70 of 86 here — alongside 85 others — read 20 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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“Shahraadcoin” (@shahraadcoin), 1,454 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/shahraadcoin.
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.