Posted without readable text
โค22customย 54111973459687015604๐2

Channel
@technicalthoughts
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Telegram's recommendations ยท Cite this entry
779subscribers
+0 since we began measuring on 5 October 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002115863254 |
|---|---|
| Type | Channel |
| Username | @technicalthoughts |
| Description | Ellia's Trading Journey Ask Barney : https://t.me/m/YR0BXZalY2Rl |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/technicalthoughts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 05:22 | 779 | no change |
| 5 Oct 2026, 04:47 | 779 | first reading |
20 posts held, back to 24 September 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 13 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramโs own channel header, read 5 October 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.
Measured directly from 6 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.
899 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 69.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 626 | 69.6% | |
| ๐ฅ | 168 | 18.7% | |
| customย 5411197345968701560 | 49 | 5.45% | |
| ๐ | 29 | 3.23% | |
| ๐ฅฐ | 16 | 1.78% | |
| ๐ฏ | 10 | 1.11% | |
| customย 5416076321442777828 | 1 | 0.111% |
Custom emoji. 2 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 are Telegramโ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 19 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 899 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 24 September 2025 to 13 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.
Posted without readable text
โค22customย 54111973459687015604๐2
The outlook played out just as planned โ M30 moved exactly as studied. Truly grateful it followed the plan. Hope whoever saw it managed to take the trade and learn something from it too
โค21customย 54111973459687015605๐1
Video, posted without a caption
โค21๐ฏ3๐ฅ3
Target hit . Goodnight โ๏ธโ๏ธโ๏ธ ๐ด๐ด
โค24๐ฅ7๐3๐ฏ2customย 54111973459687015601
Quick update: Currently Iโm over halfway to the 270-pip target.
โค11๐3๐ฅ2
Quick Update: Currently holding a buy trade โ price has moved about 100 pips from my entry point (H1 SnR level). Iโm expecting at least a 270-pip continuation to the upside. Letโs see how the move develops
โค10๐ฏ2๐ฅ2๐1
๐ XAUUSD New York Session Outlook (10.10.25) The last H4 candle closed as a bullish breakout, confirming the start of Phase 3 for our daily bias. Heading into NY session, Iโll stay bullish-biased, focusing on M30 / H1 / H4 levels for potential buy setups in line with the HTF bias.
โค18๐ฅ4๐2
๐ XAUUSD So Far (NY) โ 03 Oct 2025 So far, XAUUSD has respected the plan โ the H4 breakout confirmed continuation, and after completing Phase 3, price has moved around 250 pips. But this is just how the cycle played out this time. Even tho the most likeliness is high, the market is never certain, only probable. Always keep risk management in check & stay disciplined with your plan. We learn and grow with every phaโฆ
๐ฅ20โค9customย 54111973459687015604
๐ XAUUSD Market Outlook โ 3 Oct 2025 From my perspective, the last H4 candle has closed as a bullish breakout. This signals the market has entered Phase 3 (Continuation Phase) of the cycle, where price is more likely to sustain upward movement. For the New York session, my plan is to stay biased towards buy setups in line with this continuation.
โค22๐ฅ16๐ฅฐ6
Hello everyone, Iโd like to share a story today. Itโs about my student Blankaโa Slovakian and a fan of rock just like me ๐ธ. Teaching her wasnโt always easy. Since English wasnโt her main language, we often faced misunderstandings, and at times it felt like progress was moving slowly. But what stood out most was her determination. No matter the barriers, she kept showing up and kept trying. I adjusted my approachโusโฆ
โค67๐ฅ5๐ฏ3๐3
Photo, posted without a caption
โค24๐ฅ15customย 54111973459687015604
Video, posted without a caption
โค47๐ฅ9๐4๐ฅฐ1
Showing the 12 most recent of 20 posts we hold for @technicalthoughts. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly โ each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseโs query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegramโs list for THAT channel, not this one โ see how this is measured.
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 5 October 2026 โ this entry's latest reading, not the date you are reading this.
โ@_๐ป๐ผ๐๐ฏ๐ฎ๐ฟ๐ป๐ฒ๐๐ต๐ตโ (@technicalthoughts), 779 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/technicalthoughts.
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.