Channel
@mafahimcrypto
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001722100613 |
|---|---|
| Type | Channel |
| Username | @mafahimcrypto |
| Description | ایردراپهای رایگان و مفاهیم اولیه کریپتو |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mafahimcrypto |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 11:48 | 9 | no change |
| 7 Aug 2026, 04:33 | 9 | first reading |
20 posts held, back to 14 July 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
🧨🧨 من یه رباتم برای پیدا کردن اشخاص 🧨🧨 🔴اگه دنبال کسی میگردین فقط کافیه اسم و فامیل یا شماره تلفن یا کد ملی بزنید تا پیداش کنم☕️ 📡علاوه بر این شما این امکان رو دارین که مشخصات خودتون رو چک کنید و ببینید چه اطلاعاتی ازتون لو رفته🦦 با استفاده ازین لینک ۱۰ سرچ رایگان دریافت کنید👇🏼👇🏼👇🏼 👉🏻 t.me/Check_data1bot?start=5040425668
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
https://t.me/owldatabot?start=6135961327 شماره تلفن بده همه اطلاعات صاحب خط را بدست بیاور حتی سوابق کیفری و ...... کد ملی، آدرس و ..........
Signed JAVlD SHAH
Say hello to TTcoin, the cryptocurrency of the future. join your friend now https://play.google.com/store/apps/details?id=com.ttcoin.network&referrer=sQkOuBJNiVbUEjBVzkl5ecYX8ko2
Signed JAVlD SHAH
Showing the 12 most recent of 20 posts we hold for @mafahimcrypto. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ایردراپ و سیگنال” (@mafahimcrypto), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mafahimcrypto.
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.