Telegram RegisterThe public register of Telegram
Telegram profile photo for 🤖Советник для ФОРЕКС 🦾

Channel

🤖Советник для ФОРЕКС 🦾

@kompasfx

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

576subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001251083002
TypeChannel
Username@kompasfx
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/kompasfx

Growth

576579577.57 August 2026 — 579 subscribers8 August 2026 — 579 subscribers16 August 2026 — 577 subscribers23 August 2026 — 576 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -3. 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 576–579 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 08:55576-1
16 Aug 2026, 07:07577-2
8 Aug 2026, 03:21579no change
7 Aug 2026, 14:36579first reading

Engagement

9 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.84%
avg views ÷ 576 subscribers
Avg views / post
16.3
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 9 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 7 August 2026
Posts held9 (18 July 20267 August 2026)
Views total49
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:21 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
41s
Average length
41s

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.

Recent posts

7 Aug 2026, 06:11 UTC10 viewsread 8 August 2026
Photo

Статистика второго счета: +25 358% прибыли за 21 месяц торговли При очень консервативной просадке в 14.40%. Простая арифметика: 💰Вложив всего $100, сейчас вы бы имели $25 358 💰С $1 000 ваш капитал вырос бы до $253 580 🤔Почему советнику доверяют: 1. Работает с Ноября 2021 года 2. Максимальная просадка всего 15% 3. Ограничение суточного убытка до 5% 4. Не использует опасные стратегии (мартингейл, сетки) Можно продо

2 Aug 2026, 11:57 UTC21 viewsread 8 August 2026
Photo

🗓Результаты советника за 58 месяцев📈 Счет 1: +107 573% за 29 месяцев Счет 2: +25 358% за 21 месяц Счет 3): +367% за 7 месяцев С ноября 2021г мой советник с 500$ принёс более 354000$ 🗓2021 год Ноябрь +77% Декабрь +32% 🗓2022 год Январь +49% Февраль +32% Март +32% Апрель +18% Май +36% Июнь +18% Июль +31% Август +19% Сентябрь +44% Октябрь +19% Ноябрь +17% Декабрь +20% 🗓2023 год Январь +26% Февраль +34% Март +19% Апрель

1 Aug 2026, 07:50 UTC18 viewsread 8 August 2026
Photo

🚀 +379% / +18 990$ 📈 Просадка не превысила 11% 🦾 📈Общая статистика счетов: Счет №1: +107 573% (за 29 месяцев) Счет №2: +23 520% (за 21 месяц) Счет №3: +379% (с 1 Января 2026года) Автоматический советник для торговли золотом продолжает демонстрировать стабильные результаты своей торговли! Торговые параметры: 🔵Take Profit: 60.0 пунктов 🔴Stop Loss: 30.0 пунктов 🛑Максимальная просадка: 15% 📊Средняя прибыль за месяц: 3

26 Jul 2026, 10:18 UTC26 viewsread 8 August 2026
Photo

🔥Мой торговый советник разработан для обеспечения стабильного и консервативного прироста капитала 📈 🗓 Успешно торгует с ноября 2021 года. Его долгосрочная эффективность подтверждена официальными мониторингами. 🛡Встроенный алгоритм предотвращения убытков гарантирует 100% защиту от непредсказуемых рыночных ситуаций. Ограничение суточных потерь составляет не более 5% от размера счёта. 🦾 Придерживается консервативного

25 Jul 2026, 07:38 UTC21 viewsread 8 August 2026
Photo

🚀 +360% / +18 029$ 📈 с 01.01.2026г🗓 Просадка не превысила 11% 🦾 📈Общая статистика счетов: Счет №1: +107 573% (за 29 месяцев) Счет №2: +23 520% (за 21 месяц) Счет №3: +360% (с 1 Января 2026года) Можно продолжать не верить, а можно использовать инструмент, в который вложено много сил и времени. Я не обещаю чудеса 👉 я показываем реальный PROFIT, который получаем сами уже больше четырех лет 📈 ➡️ Написать разработчик

23 Jul 2026, 05:23 UTC22 viewsread 8 August 2026
Forwarded from @otz_proeafxPhoto

Почему мой советник эффективен? 🤔 У него нет нервной системы. Ему не нужно пить кофе, он не впадает в тильт и не пытается «отомстить» рынку. Он просто железно исполняет алгоритм: ✅ Строгий стоп-лосс и тейк-профит. ✅ Вход только по сигналу, а не «потому что кажется». ✅ Работа 24/5 без усталости и выгорания. Хватит бороться с собой. Позволь алгоритму делать то, что он умеет лучше всего — торговать с холодной головой

22 Jul 2026, 07:19 UTC20 viewsread 8 August 2026
Video

🎞Видео отчет торговли моего советника на двух счетах Счет 1: 🗓 За 21 месяц 🚀 С депозита 10 000$ 📈 Рост на +25 358% / +185 491$ чистой прибыли Счет 2: 🗓 За 7 месяцев 🚀 С депозита 5000$ 📈 Рост на +344% / +17 200$ чистой прибыль Почему мой советник эффективнее ручной торговли? У него нет нервной системы. Ему не нужно пить кофе, он не впадает в тильт и не пытается «отомстить» рынку. Он просто железно исполняет алгорит

21 Jul 2026, 11:47 UTC19 viewsread 8 August 2026
Photo

Зачем анализировать графики сутками и рисковать вручную, если можно доверить это профессиональному софту? Пока вы думаете, мой советник УЖЕ сделал +344% к депозиту! Реальные результаты работы моего торгового советника. Статистика говорит сама за себя, и цифры здесь вместо тысячи слов: 💰 Стартовый депозит: всего $5 000 🚀 Чистая прибыль: +$17 200$ Полностью автоматизирует процесс — торгует строго по алгоритму, без

18 Jul 2026, 13:32 UTC29 viewsread 8 August 2026
Photo

🚀 +344% / +17 200$ 📈 с 01.01.2026г🗓 На данный момент просадка не превышала 1️⃣1️⃣Процентов ‼️ 📈Общая статистика счетов: Счет №1: +107 573% (за 29 месяцев) Счет №2: +23 520% (за 21 месяц) Счет №3: +344% (с 1 Января 2026года) 🤔Почему советнику доверяют: 🔥Работает с Ноября 2021 года 🔥Максимальная просадка всего 15% 🔥Ограничение суточного убытка до 5% 🔥Не использует опасные стратегии (Мартингейл, сетки) ➡️ Написать ра

Showing the 9 most recent of 9 posts we hold for @kompasfx. 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

Citation-graph rank — 902,836 of 1,603,376entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

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

“🤖Советник для ФОРЕКС 🦾” (@kompasfx), 576 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/kompasfx.

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.