Channel
MD.
@mer_id1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,406subscribers
-80 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002179147496 |
|---|---|
| Type | Channel |
| Username | @mer_id1 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 September 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/mer_id1 |
Topic
Other / unclassifiable — 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 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 |
|---|---|---|
| 5 Oct 2026, 05:01 | 1,406 | -21 |
| 29 Sept 2026, 03:54 | 1,427 | no change |
| 26 Sept 2026, 15:19 | 1,427 | -16 |
| 15 Sept 2026, 12:16 | 1,443 | -5 |
| 11 Sept 2026, 12:56 | 1,448 | -4 |
| 6 Sept 2026, 17:39 | 1,452 | -3 |
| 2 Sept 2026, 09:35 | 1,455 | -3 |
| 30 Aug 2026, 03:37 | 1,458 | +1 |
| 27 Aug 2026, 07:19 | 1,457 | -4 |
| 24 Aug 2026, 11:05 | 1,461 | -2 |
| 20 Aug 2026, 13:11 | 1,463 | -2 |
| 17 Aug 2026, 14:24 | 1,465 | -6 |
| 13 Aug 2026, 23:27 | 1,471 | -6 |
| 10 Aug 2026, 22:01 | 1,477 | -8 |
| 8 Aug 2026, 06:40 | 1,485 | -1 |
| 8 Aug 2026, 00:45 | 1,486 | 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.
@lordcryptovipbot · 25,675
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 13 September 2026
@cryptokiilerr · 30,705
Telegram ranks this channel #13 of 81 here — alongside 80 others — read 6 September 2026
@AlvandCrypto · 33,113
Telegram ranks this channel #13 of 61 here — alongside 60 others — read 2 September 2026
@Wall_Team · 36,755
Telegram ranks this channel #16 of 78 here — alongside 77 others — read 31 August 2026
@aliakbari_trade · 25,692
Telegram ranks this channel #21 of 58 here — alongside 57 others — read 25 September 2026
@solevrage11 · 50,972
Telegram ranks this channel #21 of 87 here — alongside 86 others — read 26 August 2026
@khabarfour1 · 114,506
Telegram ranks this channel #21 of 56 here — alongside 55 others — read 13 August 2026
@BitunixxPersian · 20,651
Telegram ranks this channel #23 of 71 here — alongside 70 others — read 25 September 2026
@MawtinCrypto_vip · 4,412,018
Telegram ranks this channel #23 of 81 here — alongside 80 others — read 8 August 2026
@tarotfalle · 29,479
Telegram ranks this channel #24 of 43 here — alongside 42 others — read 8 September 2026
@lordcryptovip · 793,020
Telegram ranks this channel #33 of 85 here — alongside 84 others — read 8 August 2026
@sntr_cry · 34,455
Telegram ranks this channel #34 of 69 here — alongside 68 others — read 17 September 2026
@WhAleir_fx · 636,124
Telegram ranks this channel #35 of 80 here — alongside 79 others — read 8 August 2026
@Dar_Saye · 33,827
Telegram ranks this channel #38 of 62 here — alongside 61 others — read 4 September 2026
@TheGodZil · 33,064
Telegram ranks this channel #41 of 80 here — alongside 79 others — read 4 September 2026
@bit_1ch · 86,585
Telegram ranks this channel #43 of 81 here — alongside 80 others — read 17 August 2026
@TrustTraade · 105,279
Telegram ranks this channel #44 of 85 here — alongside 84 others — read 14 August 2026
@trade_hadi · 563,099
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 10 August 2026
@cip_cry · 272,099
Telegram ranks this channel #48 of 80 here — alongside 79 others — read 19 August 2026
@Wave_Chanel · 567,507
Telegram ranks this channel #49 of 79 here — alongside 78 others — read 8 August 2026
@Leverage_125 · 88,132
Telegram ranks this channel #51 of 81 here — alongside 80 others — read 16 August 2026
@GoldSignalBtc · 249,783
Telegram ranks this channel #51 of 78 here — alongside 77 others — read 13 August 2026
@YeganeCrypto · 325,776
Telegram ranks this channel #51 of 87 here — alongside 86 others — read 10 August 2026
@RstCrypto · 388,911
Telegram ranks this channel #51 of 89 here — alongside 88 others — read 10 August 2026
This channel appears in 36 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“MD.” (@mer_id1), 1,406 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/mer_id1.
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.