Channel
@Reza_ghanipur
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,412subscribers
+68 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001180175648 |
|---|---|
| Type | Channel |
| Username | @Reza_ghanipur |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Reza_ghanipur |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 16 Sept 2026, 17:22 | 5,412 | +12 |
| 12 Sept 2026, 10:20 | 5,400 | -5 |
| 8 Sept 2026, 12:16 | 5,405 | +7 |
| 3 Sept 2026, 15:38 | 5,398 | +4 |
| 31 Aug 2026, 04:04 | 5,394 | +19 |
| 27 Aug 2026, 21:17 | 5,375 | +5 |
| 24 Aug 2026, 20:24 | 5,370 | +10 |
| 21 Aug 2026, 07:56 | 5,360 | -9 |
| 18 Aug 2026, 06:03 | 5,369 | -1 |
| 15 Aug 2026, 05:19 | 5,370 | +12 |
| 12 Aug 2026, 05:22 | 5,358 | -1 |
| 8 Aug 2026, 23:00 | 5,359 | +15 |
| 6 Aug 2026, 04:01 | 5,344 | no change |
| 6 Aug 2026, 03:52 | 5,344 | first reading |
21 posts held, back to 21 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 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 21 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
616 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 68.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 424 | 68.8% | |
| ❤ | 128 | 20.8% | |
| 🤣 | 32 | 5.19% | |
| 👏 | 14 | 2.27% | |
| 👎 | 6 | 0.974% | |
| 😭 | 4 | 0.649% | |
| 🤔 | 3 | 0.487% | |
| 😁 | 2 | 0.325% | |
| 🍾 | 1 | 0.162% | |
| 💩 | 1 | 0.162% | |
| 🫡 | 1 | 0.162% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 21 of the 21 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 645 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 21 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#بیت_کوین ۲۰ مرداد ۱۴۰۵ با وجود سطح حمایتی قوی، ساختار فعلی بازار از دید من همچنان پتانسیل نزولی داره. سناریوی اصلی، ادامهی اصلاح و حرکت به سمت سطوح پایینتر هست؛ مگر اینکه قیمت با شکست و تثبیت بالای محدودهی ابطال، این سناریو رو بیاعتبار کنه. ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍17😭3
Signed Re Za
فولادی که به علت جنگ آسیب زیادی بهش وارد شده و نیاز به ۳ تا ۶ میلیارد دلار برای بازسازی داره، بودجه مسئولیت اجتماعی ۴.۵ همتی تصویب کرده! ذوب با زیان انباشته ۱۶ همتی ۱۵۰ میلیارد و ایرانخودرو با ۱۲۰ همت زیان انباشته ۱۰۰ میلیارد بودجه مسئولیت اجتماعی تصویب کردن. خیلی جالبه که این شرکتها خودشون نیاز به کمک دارن ولی مدیران این شرکتها بجای این که دنبال حق و حقوق شرکت و سهامداراش باشن دنبال خوش رقصی برای دولت هستن. روی …
👍49👏8❤6👎1😁1
Signed Re Za
#نهال ۱۶ مرداد ۱۴۰۵ تحلیل قبلی که در سال گذشته انجام شد (بهش ریپلای شده) حدودا بازدهی ۱۰۰ درصدی داشت. به نظر یک گام صعودی دیگه در این موج حرکتی خواهیم داشت. ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍19❤4
Signed Re Za
اگه یه سهم ۳۰۰ درصد رشد کرده باشه، جرأت خریدنش رو دارید؟ احتمالاً خیلیها میگن: «نه، دیگه دیر شده.» ولی این طرز فکر همیشه درست نیست. اگه یک شرکت از نظر بنیادی متحول شده باشه، سودش رشد کرده باشه و بازار تازه ارزش واقعی اون تغییرات رو درک کرده باشه، اصلاً عجیب نیست که سهم چند صد درصد رشد کنه؛ حتی بعد از اون هم به رشدش ادامه بده. بعضی از بزرگترین برندههای بازار، قبل از اینکه چند هزار درصد رشد کنن، اول چند صد درصد رشد…
👍25❤6👎1🤔1
Signed Re Za
#وبملت ۱۱ مرداد ۱۴۰۵ به دید بلند مدت هم فعلا نظرم روی اینه. البته این چارت، ارزش معاملاتی خاصی نداره. ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍15❤4
Signed Re Za
#وبملت 10 مرداد ۱۴۰۵ اول باید وضعیت ساختار موج دی مشخص بشه. ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍24❤11👎2
Signed Re Za
هر چند وقت یکبار یکی با ماشینحساب میاد و با هیجان کشف میکنه که: «بنزین تو ایران خیلی ارزونه!» درسته. فقط یه سؤال... اون ماشینی که تو امارات ۲۵ هزار دلاره، چرا اینجا ۵۰ هزار دلاره؟ یعنی قبل از اینکه حتی اولین لیتر بنزین رو بسوزونی، حدود ۲۵ هزار دلار اضافه پرداخت کردی. بعد هم با حقوقی که برای بخش بزرگی از مردم بین ۱۵۰ تا ۲۵۰ دلار در ماهه (یک پنجم درآمد مردم منطقه)، بهت میگن: «بنزینت یارانهایه». جدی؟ چقدر قشنگه. …
👍64❤9👎2
Signed Re Za
#خرینگ ۵ مرداد ۱۴۰۵ ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
❤29👍8
Signed Re Za
#وگستر ۵ مرداد ۱۴۰۵ ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
❤17👍9
Signed Re Za
#آسیاتک ۵ مرداد ۱۴۰۵ ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍13❤3
Signed Re Za
عملا اقداماتی که در #فملی انجام شده, دزدی حساب میشه. جالب اینه که طرف محکوم به 10 سال حبس به خاطر اختلاس بوده و الان پست و مقام بالای مدیریتی در این مجموعه بهش دادن. ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍24❤3😁1
Signed Re Za
#غبهنوش ۴ مرداد ۱۴۰۵ ➖➖➖➖➖➖➖➖ @Reza_Ghanipur
👍10
Signed Re Za
Showing the 12 most recent of 21 posts we hold for @Reza_ghanipur. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 registered channels — 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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“رضا غنی پور (بازارهای مالی)” (@Reza_ghanipur), 5,412 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Reza_ghanipur.
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.