Channel
Malaysian Crypto Community🇲🇾
@malaysiancryptocommunity
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,408subscribers
-31 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 | -1001750586112 |
|---|---|
| Type | Channel |
| Username | @malaysiancryptocommunity |
| 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 | 3 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 2 times, most recently 3 November 2026 |
| On Telegram | t.me/malaysiancryptocommunity |
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 96% 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 |
|---|---|---|
| 31 Oct 2026, 01:28 | 1,408 | -1 |
| 28 Oct 2026, 00:44 | 1,409 | +1 |
| 22 Oct 2026, 01:37 | 1,408 | -6 |
| 18 Oct 2026, 10:05 | 1,414 | -4 |
| 15 Oct 2026, 00:09 | 1,418 | +1 |
| 12 Oct 2026, 03:21 | 1,417 | -1 |
| 29 Sept 2026, 17:08 | 1,418 | no change |
| 27 Sept 2026, 07:17 | 1,418 | -9 |
| 18 Sept 2026, 04:56 | 1,427 | -1 |
| 14 Sept 2026, 04:19 | 1,428 | -3 |
| 10 Sept 2026, 01:40 | 1,431 | -3 |
| 5 Sept 2026, 03:00 | 1,434 | +2 |
| 1 Sept 2026, 10:47 | 1,432 | -1 |
| 26 Aug 2026, 12:49 | 1,433 | -2 |
| 23 Aug 2026, 07:11 | 1,435 | -3 |
| 16 Aug 2026, 19:06 | 1,438 | +3 |
| 13 Aug 2026, 15:08 | 1,435 | -4 |
| 10 Aug 2026, 06:53 | 1,439 | +1 |
| 7 Aug 2026, 16:54 | 1,438 | -1 |
| 7 Aug 2026, 04:07 | 1,439 | 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.
@channelmurasx · 21,555
Telegram ranks this channel #10 of 75 here — alongside 74 others — read 23 September 2026
@jawatan · 90,567
Telegram ranks this channel #11 of 76 here — alongside 75 others — read 16 August 2026
@mydoa_hq · 27,210
Telegram ranks this channel #22 of 70 here — alongside 69 others — read 11 September 2026
@hrgms · 54,878
Telegram ranks this channel #51 of 60 here — alongside 59 others — read 21 September 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“Malaysian Crypto Community🇲🇾” (@malaysiancryptocommunity), 1,408 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/malaysiancryptocommunity.
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.