Telegram RegisterThe public register of Telegram
Telegram profile photo for کانال ویژه

Channel

کانال ویژه

@Vigheh1373

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

10,789subscribers

-312 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001288735702
TypeChannel
Username@Vigheh1373
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 live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Vigheh1373

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 11 September 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.

Growth

10,78911,10110,9456 August 2026 — 11,101 subscribers7 August 2026 — 11,096 subscribers8 August 2026 — 11,087 subscribers9 August 2026 — 11,080 subscribers10 August 2026 — 11,064 subscribers11 August 2026 — 11,054 subscribers12 August 2026 — 11,044 subscribers13 August 2026 — 11,023 subscribers14 August 2026 — 11,012 subscribers16 August 2026 — 11,003 subscribers17 August 2026 — 10,979 subscribers18 August 2026 — 10,975 subscribers19 August 2026 — 10,969 subscribers20 August 2026 — 10,963 subscribers21 August 2026 — 10,957 subscribers22 August 2026 — 10,948 subscribers24 August 2026 — 10,943 subscribers25 August 2026 — 10,935 subscribers26 August 2026 — 10,925 subscribers27 August 2026 — 10,921 subscribers28 August 2026 — 10,920 subscribers29 August 2026 — 10,913 subscribers30 August 2026 — 10,903 subscribers31 August 2026 — 10,892 subscribers1 September 2026 — 10,887 subscribers3 September 2026 — 10,885 subscribers5 September 2026 — 10,877 subscribers8 September 2026 — 10,856 subscribers11 September 2026 — 10,849 subscribers13 September 2026 — 10,828 subscribers15 September 2026 — 10,810 subscribers16 September 2026 — 10,800 subscribers19 September 2026 — 10,789 subscribers6 August 202619 September 2026
33 measurements spanning 44 days, net -312. 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 10,742–11,148 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 10:1510,789-11
16 Sept 2026, 21:3810,800-10
15 Sept 2026, 01:3610,810-18
13 Sept 2026, 08:2010,828-21
11 Sept 2026, 09:1910,849-7
8 Sept 2026, 11:5910,856-21
5 Sept 2026, 08:4010,877-8
3 Sept 2026, 09:2310,885-2
1 Sept 2026, 08:2810,887-5
31 Aug 2026, 11:4610,892-11
30 Aug 2026, 09:2710,903-10
29 Aug 2026, 07:4710,913-7
28 Aug 2026, 09:3710,920-1
27 Aug 2026, 06:0810,921-4
26 Aug 2026, 08:1510,925-10
25 Aug 2026, 05:3710,935-8
24 Aug 2026, 02:4410,943-5
22 Aug 2026, 13:5210,948-9
21 Aug 2026, 05:4810,957-6
20 Aug 2026, 08:3410,963first reading

Engagement

265 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 41 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.08%
avg views ÷ 10,789 subscribers
Avg views / post
764
88 posts measured
Reaction rate
0.393%
reactions ÷ views · ER floor
Posts in window
88
of 265 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. It is computed over the 43 of 88 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held265 (3 August 20261 September 2026)
Views total67,238
Reactions total145
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 19:59 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

Video runtime
1m 14s
Average length
37s

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.

Reaction mix

503 reactions across 127 posts, in 5 distinct kinds. The most used accounts for 72.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
36272.0%
👍10621.1%
🙏173.38%
😢132.58%
👌50.994%

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 130 of the 265 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 503 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 265 most recent posts we hold, published 3 August 2026 to 1 September 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.

Recent posts

1 Sept 2026, 10:23 UTC636 viewsread 1 September 2026

نهال از منفی ها میتونین بخرین قیمت 70200 رو به پایین دادنم چه بهتر به دید نوسان چند روزه

1 Sept 2026, 10:20 UTC646 viewsread 1 September 2026
Photo

▫️ورود و خروج پول حقیقی به سهام در روز جاری

1 Sept 2026, 08:42 UTC778 views2 reactionsread 1 September 2026

از منفی ۳ سبهان به دید نوسانی میتونین بخرین

2

1 Sept 2026, 07:05 UTC825 views2 reactionsread 1 September 2026
Photo

کاسپین از صفر تابلو میتونین بخرین به دید نگهداری هفتگی

2

1 Sept 2026, 07:02 UTC783 views2 reactionsread 1 September 2026
Photo

شپدیس ۲۱ درصدی شد🤲🤲

👍2

1 Sept 2026, 06:16 UTC737 viewsread 1 September 2026

خداروشمر امروزم با مثبت و صف‌ خرید باز شد بهترین جا از منفی ها براتون سیگنال دادیم پر برکت باشین

1 Sept 2026, 06:16 UTC227 viewsread 1 September 2026

هر ۳ تا نماد امروز بهترین فرصت خرید دادن از منفی ها رفت صف خرید هر کی دیشب عضو کانال خداروشکر همین امروز تونستین سود بهشون برسونیم 🤲🤲🤲 سهم های هفته پیشمونم در این بازار پر عرضه خداروشکر صف خرید و مثبت دارن معامله میشن

31 Aug 2026, 18:56 UTC964 views0 reactionsread 1 September 2026
Photo

▫️میزان ورود و خروج نقدینگی حقیقی ها بین صندوق‌های سرمایه گذاری در روز جاری بیشترین ورود نقدینگی حقیقی: "صندوق های طلا" بیشترین خروج نقدینگی حقیقی: "صندوق های درآمد ثابت"

31 Aug 2026, 14:51 UTC≈1,080 viewsread 1 September 2026
Video

دامنه نوسان بورس تغییر می‌کند؟ مدیرعامل بورس تهران: یک ایده‌ را در خصوص دامنه نوسان تقدیم سازمان بورس کردیم اما نمی‌توانم جزئیات آن را بگویم.

31 Aug 2026, 12:52 UTC≈1,140 views4 reactionsread 1 September 2026

#تابان به هر کد شرکت کننده در عرضه اولیه #تابان تعداد 3,697 سهم معادل 4 میلیون و 700 هزار تومان تخصیص یافت

👍2😢2

31 Aug 2026, 08:19 UTC≈1,150 viewsread 1 September 2026
Photo

#از_بازار_چه_خبر ۹ شهریور ۱۴۰۵ 🚨 قیمت تتر به ۲۰۷ هزار تومان رسید ➖➖➖➖

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

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.

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

“کانال ویژه” (@Vigheh1373), 10,789 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Vigheh1373.

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.