Today's Premium Cash BAJFINANCEπ 1087 to 1076 = 11 points profitπ₯π₯π₯

Channel
π§ππππ‘ππππ πππππ¦ (cash performance)
@technicalcashperformance
On this record: Topic Β· Growth Β· Engagement Β· Posts Β· Citations Β· Telegram's recommendations Β· Cite this entry
927subscribers
-12 since we began measuring on 9 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001403631544 |
|---|---|
| Type | Channel |
| Username | @technicalcashperformance |
| Created | Between 1 December 2018 and 30 November 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/technicalcashperformance |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 00:21 | 927 | -1 |
| 17 Sept 2026, 01:19 | 928 | -4 |
| 9 Sept 2026, 09:59 | 932 | -10 |
| 31 Aug 2026, 18:12 | 942 | -2 |
| 25 Aug 2026, 05:36 | 944 | -4 |
| 18 Aug 2026, 06:02 | 948 | +6 |
| 10 Aug 2026, 11:01 | 942 | +3 |
| 9 Aug 2026, 19:17 | 939 | first reading |
Engagement
20 posts held, back to 7 July 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Today's Premium Cash AUBANKπ 1088 to 1099 = 11 points profitπ₯π₯
Today's Premium Cash KALYANKJILπ 574 to 568 = 6 points profitπ₯π₯π₯
Today's Premium Cash DABURπ 410.50 to 406 = 4.5 points profitπ₯π₯π₯
Today's Premium Cash INFYπ 1159 to 1171 = 12 points profitπ₯π₯π₯
Today's Premium Cash BAJFINANCEπ 1127 to 1139 = 12 points profitπ₯π₯π₯
Today's Premium Cash SONACOMSπ 752 to 760 = 8 points profitπ₯π₯π₯
Today's Premium Cash PGELπ 598 to 604 = 6 points profitπ₯π₯π₯
Today's Premium Cash ETERNALπ 305 to 309 = 4 points profitπ₯π₯π₯
Today's Premium Cash KFINTECHπ 936 to 946 = 10 points profitπ₯π₯π₯
Today's Premium Cash KPITTECHπ 564 to 570 = 6 points profitπ₯π₯π₯
Today's Premium Cash CGPOWERπ 896 to 887 = 9 points profitπ₯π₯π₯
Showing the 12 most recent of 20 posts we hold for @technicalcashperformance. 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.
Mentions
Named by 1 registered channel β every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched β that handle may belong to someone else now, and crediting todayβs namer to yesterdayβs owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
@Call_Technical Β· 33,216
Telegram ranks this channel #1 of 60 here β alongside 59 others β read 26 August 2026
@Market_ResearchDesk Β· 19,648
Telegram ranks this channel #33 of 44 here β alongside 43 others β read 26 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 1 October 2026 β this entry's latest reading, not the date you are reading this.
βπ§ππππ‘ππππ πππππ¦ (cash performance)β (@technicalcashperformance), 927 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/technicalcashperformance.
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.