Telegram RegisterThe public register of Telegram
Telegram profile photo for Persiandicator ™

Channel

Persiandicator ™

@persiandicator

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

748subscribers

-22 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001284810832
TypeChannel
Username@persiandicator
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/persiandicator

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

7487707596 August 2026 — 770 subscribers6 August 2026 — 770 subscribers16 August 2026 — 764 subscribers24 August 2026 — 762 subscribers30 August 2026 — 758 subscribers9 September 2026 — 757 subscribers18 September 2026 — 752 subscribers2 October 2026 — 750 subscribers12 October 2026 — 748 subscribers6 August 202612 October 2026
9 measurements spanning 67 days, net -22. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 745–773 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 21:38748-2
2 Oct 2026, 21:16750-2
18 Sept 2026, 08:39752-5
9 Sept 2026, 22:19757-1
30 Aug 2026, 21:03758-4
24 Aug 2026, 14:49762-2
16 Aug 2026, 02:13764-6
6 Aug 2026, 18:15770no change
6 Aug 2026, 18:07770first reading

Engagement

13 posts held, back to 28 July 2023 — 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 13 posts for this entry, the most recent from 8 August 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2023, 06:45 UTC≈1,270 viewsread 6 August 2026
Video

10 پوزیشن آخر همگی با سود بسته شدند✅ و برآیند ۷ روز گذشته ۱۰ درصد کل سرمایه مثبت بوده 😊 که عالیه ، چرا ؟ چون بیشتر از دو پوزیشن همزمان باز نداشتیم و اهرم بالای ۱۰ هم نداشتیم👍 ، یعنی چی ؟ یعنی مدیریت ریسک، یعنی سود کم ولی ممتد چون نمیخوایم با سرمایه کاربر بازی کنیم وگرنه که همین پوزیشن ها با لوریج های بیشتر دوبرابر سود هم میداد 😉

5 Aug 2023, 10:38 UTC≈1,230 viewsread 6 August 2026
Photo

و نکته آخر که پرسیده شده ، اگر برآیند مثبته چرا اینجا منفیه ؟ والا خودمونم نمیدونیم از شاهکار های بینگ ایکس هست این مورد 😕

5 Aug 2023, 10:32 UTC≈1,110 viewsread 6 August 2026
Photo

دوستانی که میخوان حساب پرشیندیکاتور رو فالو کنن حتماً حساب استاندارد رو کپی کنند ، قسمت پرپچوال به دلیل مشکلاتی که داشت با ربات دیگه استفاده نمیکنیم پس حتما استاندارد رو فالو داشته باشید ، و سوالی که میپرسید اکثرا ، برآیند قسمت پرپچوال تقریبا ۲۰ درصد مثبت بود که مجبور به انتقال به استاندارد شدیم و برآیند قسمت کپی ترید استاندارد طی ۷ روز گذشته ۷ درصد کل سرمایه مثبت بوده‌ یعنی روزی تقریبا ۱ درصد کل مارجین ✅ هر سوالی د…

5 Aug 2023, 06:54 UTC≈1,010 viewsread 6 August 2026
Video

2⃣ در ادامه چهار تا معامله استاپ خوردیم که مجموع درصد هاش شد ۷۰ درصد 😱 ولی چون که تریدر حرفه ایی روی حساب ها کار میکنه در ۵ معامله بعدی تونستیم ۱۴۰٪ در مجموع سود کسب کنیم 🤯🤯 📌 نکته مهم در طول این مسیر به هیچ عنوان از اهرم بالاتر از ۱۰ استفاده نشد ، به هیچ عنوان drawdown (میزان ضرر وارد شده به حساب کاربر ) بیشتر از ۱۰ درصد کل مارجین نشد ، این یعنی بهترین مدیریت ریسک و سرمایه 🤩😎

5 Aug 2023, 06:47 UTC940 viewsread 6 August 2026

1⃣ این چهار تا پوزیشن بالا رو یادتونه (پست قبل رو ببینید ) ؟ آخریش شورت بیتکوین بود که 10/3% سود بهمون داد ، حالا ادامه پوزیشن ها رو ببینم با هم 😉👇🏻

2 Aug 2023, 14:13 UTC965 viewsread 6 August 2026
Photo

4 تا پوزیشن سیستم کپی ترید پرشیندیکاتور که دیروز و امروز باز شدند ، حدودا ۵ درصد سرمایه کاربر نسبت به کل سرمایشون سود گرفتند ✅ همگی هم شورت 😂 @Persiandicator_admin

30 Jul 2023, 22:23 UTC≈1,330 viewsread 6 August 2026
Photo

2⃣ حالا برآیند سیستم کپی ترید از ۷ روز پیش که راه اندازی هم شده رو ببینید 😱

30 Jul 2023, 22:22 UTC≈1,220 viewsread 6 August 2026
Photo

1⃣ چهار تا پوزیشن جدید سیستم کپی ترید رو ببینید 😎

28 Jul 2023, 11:00 UTC980 viewsread 6 August 2026
Photo

مهم : دوستانی که لینک کپی ترید گرفتن از ادمین حتما باید این قسمت حداقل ۱۰۰ دلار رو وارد کنن ، حالا یا منتقل بشه به کپی ترید یا دیپوزیت کنید وگرنه با فالو کردن تنها معاملات برای شما باز نخواهد شد 🚨🚨🚨

28 Jul 2023, 10:50 UTC961 viewsread 6 August 2026
Photo

توی سه روز گذشته برآیند ربات ۲۰ درصد روی کل سرمایه مثبت بوده ، توی تصاویر بالا ۴ پوزیشن بسته شده ارز ada و تک پوزیشن لانگ بیتکوین و برآیند سه روز گذشته رو میبینید

Showing the 12 most recent of 13 posts we hold for @persiandicator. 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.

Forward network

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.

Mentions

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.

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.

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Persiandicator ™” (@persiandicator), 748 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/persiandicator.

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.