Channel
@Signal_Alpha
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
155,403subscribers
-431 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001290744106 |
|---|---|
| Type | Channel |
| Username | @Signal_Alpha |
| Description | ✅ تحلیل بازار ارزهای دیجیتال ✅ ارائه سیگنالهای معاملاتی ✅ معرفی سبد هولد 👤 پشتیبانی: @NiceDud3e محتوای کانال تضمین سود یا توصیه مالی شخصی محسوب نمیشود و مسئولیت تصمیمگیری بر عهده کاربر است. |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Signal_Alpha |
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 9 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 08:46 | 155,403 | -93 |
| 11 Aug 2026, 12:15 | 155,496 | -15 |
| 10 Aug 2026, 14:15 | 155,511 | -145 |
| 9 Aug 2026, 16:22 | 155,656 | -105 |
| 8 Aug 2026, 18:06 | 155,761 | -85 |
| 7 Aug 2026, 15:02 | 155,846 | +12 |
| 7 Aug 2026, 00:45 | 155,834 | no change |
| 7 Aug 2026, 00:35 | 155,834 | first reading |
46 posts held, back to 1 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 20 pagesof Telegram’s post history, 20 posts per page.
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 11 August 2026 |
|---|---|
| Posts held | 46 (1 August 2026 – 11 August 2026) |
| Views total | 665,410 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 19:11 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
نتایج 3 سال اخیر VIP+ فیوچرز که در کانال قرار داده شده همیشه مثبت و پرسود بوده. اعضای VIP+ ما در هر شرایطی از مارکت (چه صعودی و چه ریزشی)، درآمد دلاری مستمر داشتند💵 توجه داشته باشید عضوگیری با تخفیف ویژه فقط تا پایان امشب فعاله ❗️⏰ با دلار صد هزار تومانی، اگه درآمد دلاری نداشته باشی، از پس زندگی برنمیای... اگه میخوای شروع قوی داشته باشی و از بقیه عقب نمونی، این فرصت رو از دست نده💰⬇️ 🔗 @Signal_Alpha_Futures
تعداد پیام ها بالاست لطفا صبور باشید 🌹🙏🏻
عضوگیری و تخفیف ویژه VIP+ شروع شد ✔️
2 ساعت تا شروع عضوگیری VIP+ ⏰
⚜️ $GRAM/USDT 🛒 محدوده خرید: 1.25 – 1.33 ⚡️ تارگتها: 🎯T1: 1.40 🎯T2: 1.55 🎯T3: 1.75 🎯T4: 2.00 🎯T5: 2.35 🎯T6: 2.80 🔺 حد ضرر: 1.10 💵 بالانس پیشنهادی: 5 درصد سرمایه 🔥 @Signal_Alpha 🔥
⚜$MUBARAK/USDT ✅ تمام تارگت ها 🔥 📈 سود : 137.0%
⚜$PUMP/USDT ✅ تارگت چهارم 📈 سود : 109.1%
⚜$ACT/USDT ✅ تارگت سوم 📈 سود : 50.8%
⚜$MUBARAK/USDT ✅ تمام تارگت ها 🔥 📈 سود : 170.1%
⚜$TST/USDT ✅ تارگت اول 📈 سود : 12.8%
⚜️ $TST/USDT 🛒 محدوده خرید: 0.020 – 0.0218 ⚡️ تارگتها: 🎯T1: 0.0225 🎯T2: 0.027 🎯T3: 0.030 🎯T4: 0.035 🎯T5: 0.042 🎯T6: 0.050 🔺 حد ضرر: 0.018 💵 بالانس پیشنهادی: 5 درصد سرمایه 🔥 @Signal_Alpha 🔥
⚜$MUBARAK/USDT ✅ تارگت پنجم 📈 سود : 103.5%
Showing the 12 most recent of 46 posts we hold for @Signal_Alpha. 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.
Citation-graph rank — 12,006 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 5 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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 12 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 32 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“سیگنال آلفا کریپتو” (@Signal_Alpha), 155,403 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Signal_Alpha.
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.