Telegram RegisterThe public register of Telegram
Telegram profile photo for @_๐—ป๐—ผ๐˜๐—ฏ๐—ฎ๐—ฟ๐—ป๐—ฒ๐˜†๐Ÿต๐Ÿต

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.

Register entry

Telegram ID-1002115863254
TypeChannel
Username@technicalthoughts
DescriptionEllia's Trading Journey Ask Barney : https://t.me/m/YR0BXZalY2Rl
CreatedBetween 1 November 2023 and 31 May 2024 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live5 October 2026
Measurements held2
On Telegramt.me/technicalthoughts

Growth

7795 Oct 2026, 04:47 โ€” 779 subscribers5 Oct 2026, 05:22 โ€” 779 subscribers5 Oct 2026, 04:475 Oct 2026, 05:22
2 measurements taken within a single day. 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 778โ€“780 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 05:22779no change
5 Oct 2026, 04:47779first reading

Engagement

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.

What this channel posts

Photos
72
Videos
7
Links
4

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.

Video runtime
56m 46s
Average length
9m 28s

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.

Reaction mix

899 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 69.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
โค62669.6%
๐Ÿ”ฅ16818.7%
customย 5411197345968701560495.45%
๐Ÿ•Š293.23%
๐Ÿฅฐ161.78%
๐Ÿ’ฏ101.11%
customย 541607632144277782810.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.

Recent posts

13 Oct 2025, 13:46 UTCโ‰ˆ2,290 views28 reactionsread 5 October 2026

Posted without readable text

โค22customย 54111973459687015604๐Ÿ•Š2

13 Oct 2025, 13:19 UTCโ‰ˆ2,130 views27 reactionsread 5 October 2026
Photo

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

13 Oct 2025, 11:55 UTCโ‰ˆ1,970 views27 reactionsread 5 October 2026
Video

Video, posted without a caption

โค21๐Ÿ’ฏ3๐Ÿ”ฅ3

10 Oct 2025, 15:07 UTCโ‰ˆ1,950 views37 reactionsread 5 October 2026
Photo

Target hit . Goodnight โœˆ๏ธโœˆ๏ธโœˆ๏ธ ๐Ÿ˜ด๐Ÿ˜ด

โค24๐Ÿ”ฅ7๐Ÿ•Š3๐Ÿ’ฏ2customย 54111973459687015601

10 Oct 2025, 15:05 UTCโ‰ˆ1,590 views16 reactionsread 5 October 2026
Photo

Quick update: Currently Iโ€™m over halfway to the 270-pip target.

โค11๐Ÿ•Š3๐Ÿ”ฅ2

10 Oct 2025, 14:50 UTCโ‰ˆ1,360 views15 reactionsread 5 October 2026
Photo

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

10 Oct 2025, 11:15 UTCโ‰ˆ1,280 views24 reactionsread 5 October 2026
Photo

๐Ÿ“Š 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

3 Oct 2025, 14:01 UTCโ‰ˆ1,540 views33 reactionsread 5 October 2026
Photo

๐Ÿ“Š 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

3 Oct 2025, 12:44 UTCโ‰ˆ1,400 views44 reactionsread 5 October 2026
Photo

๐Ÿ“Š 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

2 Oct 2025, 15:05 UTCโ‰ˆ1,410 views78 reactionsread 5 October 2026
Photo

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

1 Oct 2025, 14:46 UTCโ‰ˆ1,170 views43 reactionsread 5 October 2026
Photo

Photo, posted without a caption

โค24๐Ÿ”ฅ15customย 54111973459687015604

1 Oct 2025, 10:54 UTCโ‰ˆ1,250 views61 reactionsread 5 October 2026
Video

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.

Appears in Telegramโ€™s recommendations for other channels

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.

Tharunโ€™s Brainery
@tharunsbrainery ยท 18,843
Telegram ranks this channel #28 of 52 here โ€” alongside 51 others โ€” read 5 October 2026

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.

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 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.