Telegram RegisterThe public register of Telegram
Telegram profile photo for Постигаем ICT | SMPA trading

Channel

Постигаем ICT | SMPA trading

@smartmoneypriceaction

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

30subscribers

-1 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-1001846356306
TypeChannel
Username@smartmoneypriceaction
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 October 2026
Measurements held3
Confirmed unchanged4 times, most recently 13 October 2026
On Telegramt.me/smartmoneypriceaction

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

303130.57 August 2026 — 31 subscribers11 August 2026 — 31 subscribers10 September 2026 — 30 subscribers7 August 202610 September 2026
3 measurements spanning 34 days, net -1. 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 30–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 10:1730-1
11 Aug 2026, 03:3231no change
7 Aug 2026, 17:4131first reading

Engagement

17 posts held, back to 13 May 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 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 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

32 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1340.6%
❤1237.5%
👍26.25%
👏26.25%
👀13.13%
👨‍💻13.13%
🤡13.13%

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

Measured over the 17 most recent posts we hold, published 13 May 2026 to 5 August 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

5 Aug 2026, 12:53 UTC16 views1 reactionsread 11 August 2026
Photo

Я думаю это очень красивая ловушка для быков, и пробоя не будет. Жду вниз за стопами, и уже в вверх. Гипотеза до 10 часовых новостей по Евро.

🔥1

4 Aug 2026, 12:09 UTC20 views4 reactionsread 11 August 2026
Photo

Я очень рад приветствовать, возвращаюсь к трейдингу, за это лето я закончил ремонт и переехал в новую кв. Вхожу в рынок, до этого следил пару недель за рынком, просто раздавал на смарт тв и смотрел за уровнями, делая дела. Начал кидать ордера в пропе, и на демо на этой неделе.

❤4

8 Jun 2026, 14:16 UTC84 views1 reactionsread 11 August 2026
Photo

Это может быть как сделка с низким риском, 1 к 1 так цена после резкого роста, должна сходить за стопами, и пойти на OTE коррекцию. Отыгрыш на 7-10 пунктах

👨‍💻1

8 Jun 2026, 14:14 UTC76 viewsread 11 August 2026
Photo

Один из сценариев того, когда цена на м1-м5 на падающем рынке, выше сесси AM NY прошлого дня. Это сетап почти сетап Лари вильямса. Со стороны SM - это откат от верхней границы FVG и разрыв который цена не смогла преодалеть. + до зоны отката еще далеко.

6 Jun 2026, 16:48 UTC61 views4 reactionsread 11 August 2026

Отучил за весну 5 человек. Я не прошу обратную связь по профиту специально. Только 1 сам сказал, что увеличил свои показатели WR на 20%. Это самое важное. Я очень рад за тебя. По опыту обучения могу сказать одно за все года, ошибка одна. «Знаю как, но на рынке делаю другое». То есть трейдер в момент входа входит импульсивно, игнорируя анализ. Или же!!! Анализ сделан, но цена его загипнотизировала и он вошел по друго…

👍2🔥1🤡1

5 Jun 2026, 21:48 UTC52 views2 reactionsread 11 August 2026

Всех с достигнутой целью. Страшный день был сегодня. Хороших выходных

❤2

2 Jun 2026, 07:13 UTC64 views3 reactionsread 11 August 2026
Photo

Биткоин не преодалел этот последний рубеж обороны для медведей, и идет в сторону 60 000

❤3

27 May 2026, 15:00 UTC74 views1 reactionsread 11 August 2026
Photo

Жадничал в бу. Логика входа

❤1

26 May 2026, 14:01 UTC52 views2 reactionsread 11 August 2026
Photo

В итоге да, ошибка есть, спешка. Не в OTE не в FVG. Это моя проблема. Но переворот был бы губительнее для психики и счета. Но я в плюсе. После его слов, я поднял старые дневники и увидел, что я как полный идиот делал перевороты.

👏2

26 May 2026, 13:58 UTC40 views2 reactionsread 11 August 2026
Photo

Один раз ошибся по евре - поторопился. Главное не перевораичваться сделку, если провел анализ и получил стоп, то не коем случаее нельзя вставать наоборот. Несовершенство удваивает счет, говорил Майлкл. Если ошибся при входе в sibi, и тебя закрыло, перезаходи в ту же сторону. Это нормально! Я был в шоке когда он это сказал, я думал что надо после стопа прекращать торговлю, но смотря его стримы, я слышал что он сказа…

🔥2

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

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

“Постигаем ICT | SMPA trading” (@smartmoneypriceaction), 30 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/smartmoneypriceaction.

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.