Channel
@kabhifx
On this record: Topic Β· Growth Β· Engagement Β· Posts Β· Citations Β· Telegram's recommendations Β· Cite this entry
8,217subscribers
-283 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
| Telegram ID | -1001190462591 |
|---|---|
| Type | Channel |
| Username | @kabhifx |
| Created | Between 1 March 2018 and 31 July 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/kabhifx |
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 12 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 |
|---|---|---|
| 17 Sept 2026, 06:19 | 8,217 | -28 |
| 13 Sept 2026, 09:16 | 8,245 | -19 |
| 9 Sept 2026, 09:37 | 8,264 | -46 |
| 4 Sept 2026, 11:17 | 8,310 | -36 |
| 1 Sept 2026, 01:38 | 8,346 | -23 |
| 29 Aug 2026, 03:59 | 8,369 | -16 |
| 26 Aug 2026, 11:56 | 8,385 | -18 |
| 23 Aug 2026, 21:48 | 8,403 | -20 |
| 19 Aug 2026, 21:02 | 8,423 | -23 |
| 16 Aug 2026, 15:25 | 8,446 | -25 |
| 13 Aug 2026, 01:28 | 8,471 | -14 |
| 10 Aug 2026, 11:01 | 8,485 | -11 |
| 7 Aug 2026, 19:34 | 8,496 | -4 |
| 7 Aug 2026, 10:00 | 8,500 | no change |
| 7 Aug 2026, 09:58 | 8,500 | first reading |
20 posts held, back to 21 May 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 23 pages 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 3 July 2026. An engagement rate over an empty window would be a number about nothing.
π An anomaly has been detected in the ETH/USDT pair on the Bitnax.io platform. The price is inflated, and weβre currently working on increasing trading volume and locking in profits πΈ β now itβs your turn π₯ Here's how it works: Buy ETH on any trading platform β transfer it to Bitnax.io β sell at a higher price β make a profit β repeat the process β»οΈ Hurry up before the price is corrected π
ββββββββββββ JPY : INTERVENTION ZONE USD/JPY : Wait for Good Entry ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
ββββββββββββ EUR/USD : Target Reachedπ°π° ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
Photo, posted without a caption
ββββββββββββ AUD/USD : Target Reached π°π° ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
ββββββββββββ Today Free Entry : SELL EUR/USD π¦πΊπΊπΈ Tensions over Strait of Hormuz ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
This week High Impact News : ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
ββββββββββββ SELL AUD/USD π¦πΊπΊπΈ Bearish Pennant Pattern ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
This week High Impact News : ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
ββββββββββββ Today Free Entry : SELL CHF/JPY π¨ππ―π΅ Bearish Flag Pattern ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
ββββββββββββ Today Free Entry : SELL USD/CAD πΊπΈπ¨π¦ Rising Channel Breakdown ββββββββββββ β¨Contact Me @kabhidhan π π ββββββββββββ
GPB/CAD - Target Reached π°π°
Showing the 12 most recent of 20 posts we hold for @kabhifx. 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.
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 16 seed channels' Telegram-generated recommendation lists 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 17 September 2026 β this entry's latest reading, not the date you are reading this.
βπππππ_π§π_π§π₯ππππ‘π π₯β (@kabhifx), 8,217 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kabhifx.
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.