Channel
@eghtesadee_iran
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,788subscribers
+178 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001219426684 |
|---|---|
| Type | Channel |
| Username | @eghtesadee_iran |
| Created | Between 1 March 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 | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/eghtesadee_iran |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @talaye_iran/547017 Aug 2026, 15:33 UTC | @eghtesadee_iran/68019 · this entry7 Aug 2026, 15:41 UTC | 1.00 | 7 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @talaye_iran | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @talaye_iran. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 06:17 | 1,788 | +12 |
| 11 Sept 2026, 21:40 | 1,776 | +9 |
| 7 Sept 2026, 15:20 | 1,767 | +19 |
| 2 Sept 2026, 12:13 | 1,748 | +7 |
| 30 Aug 2026, 22:04 | 1,741 | +24 |
| 28 Aug 2026, 00:52 | 1,717 | +11 |
| 25 Aug 2026, 03:48 | 1,706 | +13 |
| 21 Aug 2026, 23:36 | 1,693 | +20 |
| 19 Aug 2026, 01:34 | 1,673 | +29 |
| 16 Aug 2026, 08:13 | 1,644 | +7 |
| 12 Aug 2026, 17:47 | 1,637 | +16 |
| 9 Aug 2026, 23:37 | 1,621 | +10 |
| 7 Aug 2026, 09:05 | 1,611 | +1 |
| 7 Aug 2026, 06:31 | 1,610 | first reading |
26 posts held, back to 6 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 2 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 26 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
#نقره | تایمفریم روزانه 🔹️نقره در محدوده حمایتی، واگرایی مثبتی تشکیل داده و فعلاً محدوده 54_52 دلار مهمترین حمایت آن محسوب میشود. 🔹️در صورت حفظ این سطح، اهداف 67 و سپس 89 دلار در دسترس خواهند بود. اما برای بازپسگیری سقف تاریخی 120 دلار، باید منتظر تغییر سیاستهای فدرال رزرو باشیم. ✍️ اگر فدرال رزرو وارد چرخه کاهش نرخ بهره شود، احتمال دستیابی نقره به سقف تاریخی خود در میانمدت بهمراتب بیشتر خواهد شد. در این بی…
#نقره آپدیت حواستون به کف کانال بود؟؟؟ چند درصد شد؟؟ بارها تاکید کردیم و اینکه الگوی های اصلاحی و رشد دادیم
#پندمعاملاتی بازار هیچ حافظهای ندارد. بازار نمیداند دیروز ضرر کردهای. نمیداند هفتهی قبل سود کردهای. نمیداند چهار سال از عمرت را صرف یاد گرفتن این کار کردهای. هر روز معاملاتی از یک نقطه شروع میشود. خنثی. بدون احساس. بدون ترحم. تنها کسی که دیروز را با خودش به امروز میآورد، خودِ تویی. به همین دلیل، پیشبینی بازار نبوغ میخواهد اما مهم این است که هر روز بیآنکه بارِ احساسیِ معاملات روز قبل را با خودت…
#نسبت_شاخص_کل_به_طلا این نمودار نشون میده که میانگین سهام به نسبت طلا برای سرمایه گذاری، 300تا500 درصد بیشتر توانایی سودسازی خواهد داشت @eghtesadee_iran
💥 #شوینده ✅ ابر افزایش سرمایه ۳۲۰۰٪ شوینده به تفکیک زیر به تایید #حسابرس رسید 1⃣ ۴۰٪از محل انباشه 2⃣ ۵۹۰٪ از محل اندوخته سرمایه 3⃣ ۲۵۶۰٪ از محل آورده و مطالبات ♻️ در صورت تایید سازمانبورس به هر سهم شوینده حدود ۶.۳ سهم جایزه و ۲۵.۶ حقتقدم تعلق خواهد گرفت @eghtesadee_iran
♦️«توافق مکه»؛ نام پیمان سهجانبه نظامی ترکیه-عربستان-پاکستان 🔹همزمان با برگزاری نشست سران ترکیه، عربستان سعودی و پاکستان در جده، گزارشها حاکی است که پیمان دفاعی سهجانبهای که قرار است امروز میان این سه کشور امضا شود، به طور رسمی «توافق مکه» (Mecca Agreement) نامگذاری شده است. @talaye_iran
#شاخص صنعت خودرو @eghtesadee_iran
#شاخص صنعت خودرو @eghtesadee_iran
🌸✨آدینه تون زیبا و شاد 💕✨الهے قشنگترین لحظه ها 🌸✨در انتظارتون باشه 💕✨الهے هرگز لبخند از رو 🌸✨لباتون نیفته 💕✨الهے خوشبختی، مثل سایه 🌸✨همراهتون باشه 💕✨الهے امروزتون پر باشه 🌸✨از خبرای خوب و اتفاقای زیبا 💕✨امروزتون زیبـا و در پنـاه خــدا @eghtesadee_iran
Sticker, posted without a caption
🚨ترامپ: فکر میکنم جنگ به زودی تموم میشه، بعیده بتونن این وضعیت رو مدت زیادی ادامه بدن، من در مذاکرات با ایران مشارکت دارم، توافق میتونه به زودی حاصل بشه @eghtesadee_iran
رسانه آمریکایی MS NOW: عمان با چارچوب یک توافق موقت با ایران برای بازگشایی تنگه هرمز موافقت کرده است. هدف از این توافق، فراهم کردن زمینه برای برقراری آتشبس جدید و ازسرگیری مذاکرات هستهای میان آمریکا و ایران عنوان شده است. @talaye_iran
Showing the 12 most recent of 26 posts we hold for @eghtesadee_iran. 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.
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.
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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“💰اقتصاد ایران” (@eghtesadee_iran), 1,788 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/eghtesadee_iran.
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.