Channel
@phantom_algorithmic
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
31subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001719488909 |
|---|---|
| Type | Channel |
| Username | @phantom_algorithmic |
| Created | 30 March 2022 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/phantom_algorithmic |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:31 | 31 | no change |
| 7 Aug 2026, 05:17 | 31 | first reading |
7 posts held, back to 30 March 2022 — 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 7 posts for this entry, the most recent from 3 June 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
7 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 6 | 85.7% | |
| ❤ | 1 | 14.3% |
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 2 of the 7 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 30 March 2022 to 3 June 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Привет👋 Робот за май дал 7% прибыли без значительной просадки баланса, т.е. риск 2% оказался достаточно маленьким и вероятно мы сможем его увеличить до 5-10%(постепенно). По первому месяцу какие ли выводы делать не верно, тем более что первая неделя была стоповой из за не настроенной маржи, НО, исходя из всего этого, ожидаемая цель в 20% к депозиту это вполне реальная задача. Для ручной торговли, поднимать или нет ри…
🔥4❤1
Хотел бы на пару вопросов по алго ответить: 1️⃣Да, робот торгует, все нормально. Пока все так же на тестовом депозите, ещё точно неделю подержим. Потом будем подключать уже АПИ клиентов. 2️⃣Сейчас тестируем уже второй алгоритм, по которому так же будут доступны сигналы и робот. Дополнительные алгоритмы нужны для диверсификации рисков. Запускать планируем в течении двух недель. 3️⃣Да, мы можем разработать индикатор ил…
Photo, posted without a caption
❇️Обычно апдейты по алгоритму даю в конце месяца, в этот раз решил немного раньше, так как есть достаточно важные вещи, которые хотел бы рассказать. 1. Работа алгоритма стартовала 3 января, и за почти 4 месяца прошла несколько серьезных видоизменений логики (т.к. алгоритм создавался изначально под рынок СМЕ для торгов внутри дня). И вот наконец то, финальный вариант полностью настроен. На скрине, мы можете наблюдать…
🔥2
Тех. работы окончены.
Сегодня будут небольшие технические обновления. График range X, как оказалось, на крипте иногда даёт пробелы в графике, из за этого были пропуски в лонг по монете AVAX. Если будете получать сигналы, сверяйте их с трансляцией, т.к. с технического графика могут улетать ложные уведомления.
Channel created
Showing the 7 most recent of 7 posts we hold for @phantom_algorithmic. 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“PhA INFO” (@phantom_algorithmic), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/phantom_algorithmic.
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.