.اشتراک کانال #تکسهم 🎯 بهمراه خرید تکسهم #شهریور از شنبه اطلاع از شرایط و خرید #تکسهم 🔰 @Departeman11

Channel
دپارتمان بورس
@departeman_ir
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,332subscribers
+20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001285624891 |
|---|---|
| Type | Channel |
| Username | @departeman_ir |
| Description | admin: reza ⬇️ لینک @Departeman11 @Departeman11 دست نوشته های شخصی،مسئولیت برداشت از مطالب با خودتان،تحلیل آزمون وخطا دارد فیلتر ؛ خرید + فروش بر مبنا ؛ فیلتر شناسایی ورود ؛ ( کف حمایتی ) فیلتر شناسایی خروج ؛ (سقف مقاومتی ) |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/departeman_ir |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:58 | 16,332 | +10 |
| 13 Aug 2026, 15:08 | 16,322 | +5 |
| 12 Aug 2026, 14:15 | 16,317 | +3 |
| 11 Aug 2026, 12:42 | 16,314 | -5 |
| 10 Aug 2026, 11:55 | 16,319 | +5 |
| 9 Aug 2026, 11:32 | 16,314 | +5 |
| 8 Aug 2026, 09:04 | 16,309 | -3 |
| 7 Aug 2026, 12:46 | 16,312 | first reading |
Engagement
144 posts held, back to 5 August 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 32 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 11.8%
- avg views ÷ 16,332 subscribers
- Avg views / post
- 1,930
- 143 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 144
- of 144 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 144 (5 August 2026 – 15 August 2026) |
| Views total | 275,839 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 19:46 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈4,640
- Videos
- ≈65
- Links
- ≈2,990
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
دپارتمان بورس pinned «2 عدد ظرفیت جدید #سبدگردانی رو1میلیارد پذیرفته می شود اطلاع ازشرایط👇 @Departeman11»
#دارویی_کم_ریسک مناسب شرایط فعلی مجوز افزایش در نرخ آنتی بیوتیک سازها 💊لیست مشمولین افزایش نرخ جدید👇 #بیوتیک #دپارس #دجابر #دکوثر #دبالک #دشیمی #دفارا #ددانا 🔴 فاصله با سقف قیمتی سایر دارویی ها👇 #دتولید 76% #دعبید 18% #دسانکو 66% #دفرا 17% #برکت 58% #داوه 15% #دزهراوی 45% #پخش 14% #والبر 21% #دارزی 11% #دروز 25% #دسینا 6% 🟢ا…
🔹 شاخص سازهای که خوب میخرند 🔰 #تیپیکو #همراه #فملی #رمپنا #تاپیکو #ومعادن #اخابر #وغدیر #فزر #دی 🗓1405/05/24 @departeman_ir
#اخابر در معاملات امروز مقاومت بازه سال شکسته شد ، اهداف بعدی 🔰 کوتاه مدتی ؛ 989 ( 22%+) میانمدتی ؛ 1.140 40%+) بلند مدتی ؛ 1.340 ( 70%+) 🗓1405/05/24 @departeman_ir
#ومعادن میانگین متحرک صعودی + روند صعودی تکنیکال + تابلو خوانی = خرید مکدی + ایچموکو = صعودی ✔️ tp = 2.850 & 3.000 ( +%15) کوتاه مدتی tp = 3.850 & 4.000 ( +%50)میانمدتی 🗓1405/05/24 @departeman_ir
2 عدد ظرفیت جدید #سبدگردانی رو1میلیارد پذیرفته می شود اطلاع ازشرایط👇 @Departeman11
#ومهان ؛ صفوف خرید پیاپی✌️ تا اینجا 40%+ ✔️ #تکسهم_تیرماه کانال خصوصی با فرصت ورود روزانه و صف خرید پایانی✔️ #ومهان پدیده 1405 خواهد بود مستندات خرید ⬇️ https://t.me/departeman_ir/39872 https://t.me/departeman_ir/39971 https://t.me/departeman_ir/39760 https://t.me/departeman_ir/39396
#شفا ؛ بازده خرید این #تکسهم 180%+✔️ مستندات ورود اعضا خصوصی 👇 https://t.me/departeman_ir/37302 https://t.me/departeman_ir/37248 https://t.me/departeman_ir/37245 هدف نوسانی ؛ 51.500 ( 15%+) کوتاه مدتی ؛ 62.000 ( 40%+) 🗓1405/05/24 @departeman_ir
🔹 ورود پول هوشمند ؛ #ومعادن #اخابر #همراه #رمپنا #فزر #تیپیکو #پخش #ومهان #ورنا #فملی #بترانس #ومهان #کیسون #وگردش #شنفت #شغدیر #پکویر #حفاری 🗓1405/05/2 @departeman_ir
مصاحبه مدیر عامل #شفا : 🔹پیش بینی سود ۴.۲ همتی 🔹۲ همت شرکت مطالبات دارد 🔹 ۱۴ سال هیچ افزایش سرمایه ای ندادن ...قراره افزایش سرمایه بدن اولویت هم با سود انباشته،تجدیدارزیابی و. آورده نقدی است 🗓1405/05/24 @departeman_ir
🔹 خریدهای گروهی امروز 🔰 #دسبحان #اخابر #تاپیکو #فملی #تیپیکو #همراه #وبصادر #فزر 🗓1405/05/24 @departeman_ir
Showing the 12 most recent of 144 posts we hold for @departeman_ir. 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.
Posts edited after publishing
@departeman_ir edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 15 August 2026
- Most recent edit
- 15 August 2026
Forward network
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.
Mentions
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.
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.
@Codal360_ir · 115,521
Telegram ranks this channel #38 of 93 here — alongside 92 others — read 14 August 2026
@Akhbar_fouriyyy · 231,980
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 13 August 2026
@boltann · 118,501
Telegram ranks this channel #81 of 93 here — alongside 92 others — read 14 August 2026
This channel appears in 3 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“دپارتمان بورس” (@departeman_ir), 16,332 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/departeman_ir.
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.