Channel
@TradingwithfunUS
On this record: Topic · Growth · Engagement · Posts · Cite this entry
698subscribers
-7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001282683833 |
|---|---|
| Type | Channel |
| Username | @TradingwithfunUS |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/TradingwithfunUS |
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 91% 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 |
|---|---|---|
| 10 Oct 2026, 17:16 | 698 | +1 |
| 30 Sept 2026, 18:20 | 697 | -1 |
| 12 Sept 2026, 21:59 | 698 | -4 |
| 4 Sept 2026, 21:56 | 702 | -2 |
| 29 Aug 2026, 05:06 | 704 | +1 |
| 14 Aug 2026, 20:26 | 703 | -2 |
| 6 Aug 2026, 19:01 | 705 | no change |
| 6 Aug 2026, 18:58 | 705 | first reading |
20 posts held, back to 28 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 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 17 July 2026. An engagement rate over an empty window would be a number about nothing.
Only for NRIs Many of you know about GIFT NIFTY, but don’t know how to actually trade it. In this video, I explain: • How to trade GIFT NIFTY Futures • Who can trade it • Tax, leverage & after-hours trading advantages Watch here 👇 https://www.instagram.com/reel/Da284tbStSB/?igsh=bjJib2JpeXB0Mnoz
Hope SLS gave premium members a 10 year fee in return 😃😃
8.5 to 11.7 40% gain in SLS
SLS 8.5 to 11 so far https://cosmofeed.com/vig/69faf0fee6bec90013a3361b
Alert shared on June 15 👍🏻
Sharing another trade today.
#PENG 59 to 65. Gave on Friday 👍🏻 https://cosmofeed.com/vig/69faf0fee6bec90013a3361b
#LLY going towards target in this crash 😃
Shared a possible 3-4X stock let’s see how it goes! Up 12% today
1080 to 1140 #LLY shared yesterday https://cosmofeed.com/vig/69faf0fee6bec90013a3361b
#AMKR 79
#UMAC 27 to 34 🔥
Showing the 12 most recent of 20 posts we hold for @TradingwithfunUS. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“Trading with Fun- US EQUITIES” (@TradingwithfunUS), 698 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/TradingwithfunUS.
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.