Channel
@MMDLeecher
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
32,673subscribers
-576 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001251145169 |
|---|---|
| Type | Channel |
| Username | @MMDLeecher |
| Description | 📢 @MMDLeecher | کانال اصلی 💡 @MMDLeecherHelp | کانال آموزش 👥 @MMDLeecherGroup | گروه 🤖 @MMDLeecherbot | ربات لیچر 🇮🇷 @MMDLeecherNimBot | ربات سرور نیم بها 👨🏻💻 @MMDLeecher_Admin | پشتیبانی 💳 @MMDLeecher_Payment | امورمالی |
| Created | 5 September 2021 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/MMDLeecher |
Software piracy — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:41 | 32,673 | -26 |
| 16 Sept 2026, 13:55 | 32,699 | -19 |
| 14 Sept 2026, 17:01 | 32,718 | -14 |
| 13 Sept 2026, 05:37 | 32,732 | -30 |
| 11 Sept 2026, 06:57 | 32,762 | -36 |
| 8 Sept 2026, 12:35 | 32,798 | -28 |
| 5 Sept 2026, 04:17 | 32,826 | -26 |
| 3 Sept 2026, 11:01 | 32,852 | -11 |
| 2 Sept 2026, 04:53 | 32,863 | -15 |
| 1 Sept 2026, 02:39 | 32,878 | -13 |
| 30 Aug 2026, 23:35 | 32,891 | -19 |
| 30 Aug 2026, 00:08 | 32,910 | -10 |
| 29 Aug 2026, 03:03 | 32,920 | -11 |
| 28 Aug 2026, 01:25 | 32,931 | -13 |
| 27 Aug 2026, 01:24 | 32,944 | -14 |
| 26 Aug 2026, 02:13 | 32,958 | -11 |
| 25 Aug 2026, 04:05 | 32,969 | -14 |
| 23 Aug 2026, 21:47 | 32,983 | -30 |
| 22 Aug 2026, 09:08 | 33,013 | -23 |
| 20 Aug 2026, 20:05 | 33,036 | first reading |
4 posts held, back to 5 September 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 74 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 23 May 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
📌 آموزش خرید سرور نیم بها 1. شارژ کیف پول از طریق درگاه ریالی 2. خرید مستقیم و شارژ کیف پول از طریق ووچر پرفکت مانی 3. شارژ کیف پول از طریق ارز ترون (اعتبار هدیه با توجه به تعداد اشتراکهای فعالتان به شما تعلق خواهد گرفت) ⭐️ تعرفه های سرور نیم بها را در ربات از قسمت خرید سرور نیم بها مشاهده کنید. ⬇️ آموزش تمدید 👁 معرفی و آموزش برنامه مورد نیاز جهت استفاده و راه اندازی سرور های نیم بها ممد لیچر در اندروید، آیفون، و…
📌 کاربران عزیز اینجا کانال پشتیبان می باشد و برای استفاده از ربات سرور نیم بها و ربات لیچر باید داخل کانال اصلی و عضو بشید. ⭐️ لینک عضویت کانال اصلی 📢 @MMDLeecher | کانال اصلی 💡 @MMDLeecherHelp | کانال آموزش 👥 @MMDLeecherGroup | گروه 🤖 @MMDLeecherbot | ربات لیچر 🇮🇷 @MMDLeecherNimBot | ربات سرور نیم بها 🇮🇷 @MMDLeecherNimBot | ربات سرور نیم بها (کمکی) 👨🏻💻 @MMDLeecher_Admin | پشتیبانی 💳 @MMDLeecher_Payment | امورمالی
📍محافظ تگ کانال ممد لیچر 🔥 برای ورود به کانال اصلی کلیک کنید
Channel created
Showing the 4 most recent of 4 posts we hold for @MMDLeecher. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ممد لیچر | MMDLeecher | ممدلیچر | MMD Leecher” (@MMDLeecher), 32,673 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/MMDLeecher.
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.