Channel
@SANCHO_DTSLIV1
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
616subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002324419031 |
|---|---|
| Type | Channel |
| Username | @SANCHO_DTSLIV1 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/SANCHO_DTSLIV1 |
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 20 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:36 | 616 | -5 |
| 7 Sept 2026, 18:35 | 621 | -4 |
| 29 Aug 2026, 10:33 | 625 | -2 |
| 21 Aug 2026, 15:38 | 627 | -3 |
| 14 Aug 2026, 15:34 | 630 | -6 |
| 8 Aug 2026, 02:49 | 636 | no change |
| 7 Aug 2026, 15:19 | 636 | first reading |
20 posts held, back to 22 July 2025 — 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 20 posts for this entry, the most recent from 24 October 2025. An engagement rate over an empty window would be a number about nothing.
85 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 45.9% | |
| 🔥 | 24 | 28.2% | |
| 👍 | 12 | 14.1% | |
| 🎃 | 4 | 4.71% | |
| 🌭 | 3 | 3.53% | |
| 😘 | 1 | 1.18% | |
| 🙏 | 1 | 1.18% | |
| 🤝 | 1 | 1.18% |
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 18 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 85 reactions 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 22 July 2025 to 24 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
👤 Junction Bot DOUBLETOP SQUAD Актуальное 20 - 24 октября Каждую пятницу мы публикуем подборку, которая включает в себя: - идеи/кейсы с максимальным приоритетом - апдейты сквада - актуальные активности по всем направлениям - обзоры рынка - все записи созвонов и стримов за неделю Все, что важно не пропустить в DOUBLETOP SQUAD! Подборка доступна по ссылке. @squad member @summary
🔥3❤1👍1
👤 Junction Bot $TRX🪑4H Текущая динамика актива демонстрирует относительную слабость по сравнению с другими инструментами. Наблюдаются признаки ре-дистрибуции🐰, что может быть использовано для открытия шорт позиции при достижении обозначенной POI. 🍄Цели: $0.3046, $0.2977 https://www.tradingview.com/x/tFCRDCRn/
❤5
👤 Junction Bot $XRP🚀4H Актив показывает локальные признаки силы🐰, и в случае коррекции к обозначенной зоне интереса (POI) ожидается начало агрессивного роста, что будет использовано для открытия лонг позиции. 🚀Цели: $2.5529, $2.5975, $2.6460, $2.6980 https://www.tradingview.com/x/8RJ5IryM/
❤4
👤 Junction Bot $ALGO🧱4H 🐰В случае дополнительной манипуляции и достижения обозначенной зоны интереса (POI) будет рассматриваться открытие шорт позиции. 👀Цели: $0.1748, $0.1697, $0.1654 https://www.tradingview.com/x/FbwWhrtA/
❤1🔥1
👤 Junction Bot $BNB🎂1H В рамках локального ренджа рассматриваю возможность открытия шорт позиции🎁 при ребалансировке обозначенной неэффективности (POI). 🎯Цели: $1052.46, $1021.00 https://www.tradingview.com/x/iymDHGIY/
🤝1
👤 Junction Bot $ENA❤️4H Локально актив демонстрирует относительную силу🎁, и в случае коррекции к обозначенному Ордер Блоку появится отличная возможность для открытия лонг позиции🐰 🚀Цели: $0.5077, $0.5165 https://www.tradingview.com/x/bJShzEQf/
🎃4❤1
👤 Junction Bot Сделка закрылась по стопу, -1.5%
👤 Junction Bot upd по локальной ситуации BTC h4:https://www.tradingview.com/x/oitXEOzf/ -мы сейчас видим как цена реагирует и показывает реакцию от нижней границы торгового диапазона (107 250), что является хорошим признаком, особенно на фоне рекордного дневного снижения золота за последние 10 лет. Однако всё не так просто. Или может просто, сейчас постараюсь объяснить. В целом, локально у нас сформирован тренд, o…
👍6
👤 Junction Bot Вторую позицию по #brent тоже в бу
👤 Junction Bot $BCH🧦4H Актив показывает локальные признаки разворота🐰, что позволяет предположить завершение текущей коррекции и возобновление ранее сформировавшегося нисходящего тренда. 🐰При ребалансировке обозначенной неэффективности (POI) буду рассматривать открытие шорт позиции. Цели: $456.6, $443.2, $436.9 https://www.tradingview.com/x/PLMH3oYX/
❤6🔥2
👤 Junction Bot SWAP уже на ваших кошельках. Заходим в декс и сразу меняем SWAP на HYPE (или стейблы) @drops
❤1
ЗАВТРА НАЧНЕТ РАБОТАТЬ
🔥15😘1🙏1
Showing the 12 most recent of 20 posts we hold for @SANCHO_DTSLIV1. 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“SANCHO D.T.” (@SANCHO_DTSLIV1), 616 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/SANCHO_DTSLIV1.
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.