Telegram RegisterThe public register of Telegram
Telegram profile photo for حسن حامدی

Channel

حسن حامدی

@signal_AT

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

15,112subscribers

-143 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-1001235571849
TypeChannel
Username@signal_AT
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held52
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/signal_AT

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.

Growth

15,11215,25515,183.56 August 2026 — 15,255 subscribers6 August 2026 — 15,255 subscribers8 August 2026 — 15,252 subscribers11 August 2026 — 15,250 subscribers12 August 2026 — 15,245 subscribers13 August 2026 — 15,244 subscribers15 August 2026 — 15,239 subscribers16 August 2026 — 15,235 subscribers17 August 2026 — 15,237 subscribers18 August 2026 — 15,236 subscribers19 August 2026 — 15,228 subscribers20 August 2026 — 15,223 subscribers21 August 2026 — 15,222 subscribers23 August 2026 — 15,224 subscribers24 August 2026 — 15,227 subscribers26 August 2026 — 15,225 subscribers27 August 2026 — 15,223 subscribers28 August 2026 — 15,219 subscribers29 August 2026 — 15,217 subscribers30 August 2026 — 15,221 subscribers30 August 2026 — 15,218 subscribers1 September 2026 — 15,214 subscribers1 September 2026 — 15,216 subscribers4 September 2026 — 15,217 subscribers7 September 2026 — 15,219 subscribers10 September 2026 — 15,213 subscribers14 September 2026 — 15,210 subscribers15 September 2026 — 15,209 subscribers18 September 2026 — 15,207 subscribers30 September 2026 — 15,189 subscribers5 October 2026 — 15,188 subscribers9 October 2026 — 15,181 subscribers13 October 2026 — 15,180 subscribers16 October 2026 — 15,179 subscribers17 October 2026 — 15,177 subscribers18 October 2026 — 15,172 subscribers19 October 2026 — 15,167 subscribers21 October 2026 — 15,162 subscribers22 October 2026 — 15,157 subscribers23 October 2026 — 15,153 subscribers24 October 2026 — 15,148 subscribers25 October 2026 — 15,143 subscribers26 October 2026 — 15,144 subscribers27 October 2026 — 15,142 subscribers28 October 2026 — 15,135 subscribers30 October 2026 — 15,131 subscribers31 October 2026 — 15,127 subscribers31 October 2026 — 15,125 subscribers1 November 2026 — 15,121 subscribers2 November 2026 — 15,116 subscribers3 November 2026 — 15,115 subscribers4 November 2026 — 15,112 subscribers6 August 20264 November 2026
52 measurements spanning 90 days, net -143. 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 15,091–15,276 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
4 Nov 2026, 18:0415,112-3
3 Nov 2026, 17:2715,115-1
2 Nov 2026, 18:5915,116-5
1 Nov 2026, 22:1115,121-4
31 Oct 2026, 22:4015,125-2
31 Oct 2026, 02:0815,127-4
30 Oct 2026, 04:2615,131-4
28 Oct 2026, 03:2915,135-7
27 Oct 2026, 03:2715,142-2
26 Oct 2026, 05:2715,144+1
25 Oct 2026, 07:5115,143-5
24 Oct 2026, 08:5815,148-5
23 Oct 2026, 08:5615,153-4
22 Oct 2026, 09:1015,157-5
21 Oct 2026, 00:2615,162-5
19 Oct 2026, 23:2115,167-5
18 Oct 2026, 21:5515,172-5
17 Oct 2026, 00:3815,177-2
16 Oct 2026, 01:3715,179-1
13 Oct 2026, 17:3915,180first reading

Engagement

48 posts held, back to 8 June 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 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
47.9%
avg views ÷ 15,112 subscribers
Avg views / post
7,240
7 posts measured
Reaction rate
1.53%
reactions ÷ views · ER floor
Posts in window
7
of 48 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held48 (8 June 2026 – 30 October 2026)
Views total50,670
Reactions total774
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 16:58 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
14s
Average length
14s

Measured directly from 1 video 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

8,631 reactions across 48 posts, in 11 distinct kinds. The most used accounts for 56.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4,86456.4%
👍2,62530.4%
👎5936.87%
😁1531.77%
🔥1281.48%
👏971.12%
🤔730.846%
🤯390.452%
😱240.278%
⚡200.232%
🥰150.174%

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

Measured over the 48 most recent posts we hold, published 8 June 2026 to 30 October 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

Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

30 Oct 2026, 15:06 UTC≈3,420 views79 reactionsread 4 November 2026
Photo

🚙چیزی که از خساپا دیده میشه، و در صورتی که این محدوده ها رو از دست بده ، وضعیت صعود فعلا تاخیر خواهد افتاد @Signal_AT این میتونه بعد از چندین گام استراحت و جابجایی خریدار و فروشنده باشه

👍50❤11👎8😱7⚡2😁1

24 Oct 2026, 07:32 UTC≈6,830 views97 reactionsread 4 November 2026

امیدوارم در مورد طلا حداقل اشتباه کرده باشم و با جون و دل بپذیرم این اشتباه رو و مثل برخی ها تارگت های زیر 20 میلیون برسیم به طلا😔 یا ریت العُمر یتوقف

👍62❤19😁9👎6🤔1

24 Oct 2026, 07:28 UTC≈6,380 views85 reactionsread 4 November 2026

👆#نفت دقیقا مطابق مسیر ترسیمی حرکت کرد یک اصلاح و بعد هم تارگت 120 دلاری ♨️بزارید هفته آتی واکنشش به 120 رو ببینم و بعد مسیر بعدی رو ترسیم میکنم

❤75👎5🥰5

21 Oct 2026, 05:47 UTC≈8,350 views89 reactionsread 4 November 2026

👆خساپا هم دیگه به محدوده 60 داره نزدیک میشه 🚗

👍64❤17👎8

21 Oct 2026, 05:47 UTC≈8,050 views81 reactionsread 4 November 2026

👆امروز به وضوح ، ارزش این نصیحت دوستانه رو متوجه میشید😉❤️

👍50👎16❤15

18 Oct 2026, 09:06 UTC≈8,980 views210 reactionsread 4 November 2026

🔆مثلا روی نماد مثقال از همینجا که هست متاسفانه در رشد میان مدتی +25 درصد دیده میشه @Signal_AT ❇️البته امیدوارم اتفاقات مهم رخ بده، اوضاع اقتصاد به یکباره تغییر کنه ولی با اصلاح طلب ها و ناواردانی مثل ناصر؟! این خیلی شانسش کمه

❤103👍62👎31😁12🤔2

18 Oct 2026, 09:03 UTC≈8,660 views133 reactionsread 4 November 2026

👆نظرم در مورد طلا اینه و بعید میدونم ریزش وحشتناکی که عده ای وعده میدن رخ بده! ⚠️البته این از اون مواردی است که از صمیم قلب آرزو میکنم اشتباه کنم

❤101👍26👎6

5 Oct 2026, 07:47 UTC≈12,600 views117 reactionsread 4 November 2026

با حفظ محدوده 60 ت به عنوان استاپ در تایم هفتگی، تارگت حداقل 90 ت خواهد بود

❤93👎10🔥8👍6

5 Oct 2026, 07:46 UTC≈11,900 views126 reactionsread 4 November 2026
Photo

#خساپا این رهایی چندین ساله با حفظ محدوده 60 ت ، نوید یک رشد خوب تکنیکالی رو میده @Signal_AT 🔆البته همونطور که قبلا هم گفتم باید ریسک های فاندی رو هم بپذرید و مطابق جو فعلی تصمیم بگیرید چقدر سرمایه وارد کنید

❤89👍27👎8👏2

4 Oct 2026, 14:08 UTC≈10,800 views188 reactionsread 4 November 2026
Photo

👆این کندل های سه ماهه طلا است (مثقال) یعنی هر کندل معادل سه ماه @Signal_AT 🔅میدونید یعنی چی؟ یعنی هر زمان و هر قیمتی حتی در نوک قله هم اگر خرید کرده باشید بین ۳ تا ۶ ماه زمان برده تا به سود برسید! ⚠️پس نگاهتون به طلا در ایران متاسفانه باید به چشم پس انداز بلند مدت باشه و دیگه کاری به چارت نداشته باشید، بخرید و بخرید و بخرید تا روزی که لازم دارید ❌هیچ‌کندلی این روند رو تغییر نمیدهد و تکنیکالی نیست مگر سیاست های کلان…

❤128🤯30👍19👎6👏5

3 Oct 2026, 08:02 UTC≈7,820 views175 reactionsread 4 November 2026

یک نکته رو مجدد تاکید میکنم: بورس همچنان از نظر ریسکی خیلی درجه بالاتری از طلا قرار داره و باید ورود بهش با سه شرط باشه: 1. اول پله پله و آرام آرام 2. ورود مقداری سرمایه که اگر بلوکه شد، جنگ شد و ... به خاک نشینید 3. حتما در کنارش طلا و یا صندوق طلا رو به عنوان پشتوانه بگیرید تا ذهنتون آروم باشه مثلا اگر 100 میلیون صندوق طلا میگیرید ، مجاز هستید نزدیک به 40 میلیون رو وارد بورس کنید

❤121👍46👎8

3 Oct 2026, 07:59 UTC≈7,650 views219 reactionsread 4 November 2026

❇️سعی میکنم اگر سهم خوبی به چشمم خورد که ریسک کمتری رو داشته باشه با توضیحات اینجا قرار بدم

❤173👍41👎3😁2

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

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.

سیگنال رایگان (آفاق)
@SignalRaygan_Afagh · 30,061
Telegram ranks this channel #52 of 94 here — alongside 93 others — read 7 September 2026
سلطان بورس
@soltanboure · 25,446
Telegram ranks this channel #59 of 90 here — alongside 89 others — read 13 September 2026
تحلیل برتر بورس
@tahlillbartar · 28,387
Telegram ranks this channel #60 of 93 here — alongside 92 others — read 9 September 2026
کانال VIP بورس
@VIPBOORSS · 37,716
Telegram ranks this channel #69 of 86 here — alongside 85 others — read 30 August 2026
کانال عرضه اولیه
@arzeh1avalieha · 99,567
Telegram ranks this channel #83 of 95 here — alongside 94 others — read 21 August 2026

This channel appears in 5 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“حسن حامدی” (@signal_AT), 15,112 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/signal_AT.

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.