#XAU … https://www.tradingview.com/x/2ipYffzO/
custom 535747117915624535379

Channel
@slaysmcus
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
1,244subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002088485411 |
|---|---|
| Type | Channel |
| Username | @slaysmcus |
| Created | Between 1 November 2023 and 30 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/slaysmcus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 12:54 | 1,244 | -6 |
| 18 Aug 2026, 04:12 | 1,250 | -2 |
| 14 Aug 2026, 18:05 | 1,252 | -4 |
| 11 Aug 2026, 07:26 | 1,256 | -2 |
| 7 Aug 2026, 22:48 | 1,258 | no change |
| 7 Aug 2026, 12:29 | 1,258 | first reading |
20 posts held, back to 30 May 2024 — 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 pageof 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 20 posts for this entry, the most recent from 16 October 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos 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.
1,384 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 25.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5465587037983761101 | 356 | 25.7% | |
| custom 5357471179156245353 | 342 | 24.7% | |
| ❤ | 242 | 17.5% | |
| custom 5465506464397281279 | 190 | 13.7% | |
| 👍 | 144 | 10.4% | |
| 🔥 | 75 | 5.42% | |
| ❤🔥 | 15 | 1.08% | |
| ⚡ | 7 | 0.506% | |
| 🏆 | 4 | 0.289% | |
| 🤯 | 3 | 0.217% | |
| 🆒 | 2 | 0.145% | |
| 🤗 | 2 | 0.145% | |
| 🐳 | 1 | 0.072% | |
| 👎 | 1 | 0.072% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 20 of the 20 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 1,384reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 May 2024 to 16 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#XAU … https://www.tradingview.com/x/2ipYffzO/
custom 535747117915624535379
#XAU Контекст на день был абсолютно простым и понятным. Красивая позиция, но со своими приколами. Некоторых оставили в без убытке. Entry - https://www.tradingview.com/x/fVTTOpKv/ 1H - https://www.tradingview.com/x/dFYVAwLF/ 1D - https://www.tradingview.com/x/Aj7CunSD/
custom 535747117915624535354
#GER40 https://www.tradingview.com/x/0tNrQ4cP/ #XAU https://www.tradingview.com/x/7tLtwzXV/
custom 535747117915624535360
Всем привет! Разобрал две позиции, которые набирал на этой неделе. GER40 & XAU. Попытался объяснить их логику, то как смотрел на контекст и на какие важные факторы обращал внимание. Рекомендуемая скорость просмотра 1.3х. Так же ниже прикреплю сами позиции, которые не публиковал ранее. P.S. Немного выпал с соц.сетей, но это все в силу загружености по работе. Все же, буду стараться как можно чаще выпускать для ва…
custom 535747117915624535376
#EUR 💅🏻 https://www.tradingview.com/x/BSQcMRZG/
custom 535747117915624535373
Все ближайшие цели по трем активам достигнуты, без возможности их монетизации. Продолжать рассматривать лонги по евро желания нету. Против снятого пдх, от которого получили сильную реакцию и инвертирование ближайших опорных зон. https://www.tradingview.com/x/IsvjQEz6/ На этом закончим торговую неделю и желаю Вам хороших выходных. Увидимся!
custom 546558703798376110159
Pre-review 20.09 Доброе утро. Составил план на сегодняшний день по евро/фунту и золоту. Как оказалось, в 9:00 вышли red news по гу и соответственно сняли все потенциальные таргеты. Поэтому анализ по гу уже не актуальный. Все остальное еще в силе и готов работать в точности с тем, о чем говорил в видео. Всем удачного торгового дня.
custom 546558703798376110152
UPD: По евро таргеты достигнуты. Ушли раньше и потянули за собой гу, что является не самым приятным сценарием. Фунт выглядел сегодня куда приятней, но имеем что имеем. Повторюсь, работаем с фактами а не с желаниями. Придерживался плана. Итог -1R 1H: https://www.tradingview.com/x/KXwpuKQV/ 3m: https://www.tradingview.com/x/L6PorxNq/
custom 546550646439728127947custom 546558703798376110119
Pre-review 29.08 План на еу/гу/голд составлен. Отталкиваться от него особо желания нету. Работаем с фактами, а не с нашими желаниями. Рекомендуемая скорость просмотра 1.5х (чтобы успели взять тейк) Всем хорошего дня, обнял
custom 546558703798376110160custom 546550646439728127910
Обзор сегодняшней позиции #XAU +2.3R 🏌🏽
custom 546550646439728127966custom 546558703798376110119
#GBP 🏌🏽 Красивейшая. https://www.tradingview.com/x/gHWnPYqa/
custom 546558703798376110174custom 546550646439728127913
#XAU Так же сегодня очень хорошо смотрелось золото. Но, к сожалению, пропустил эту позицию. 5m: https://www.tradingview.com/x/5XsVYTws/ 30m: https://www.tradingview.com/x/uEnfYYi4/ 4h: https://www.tradingview.com/x/VJ5b4ndr/
custom 546550646439728127940custom 546558703798376110120
Showing the 12 most recent of 20 posts we hold for @slaysmcus. 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“slay” (@slaysmcus), 1,244 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/slaysmcus.
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.