JAHA SE BOOK KIYA WAHA SE HI REJECTION

Channel
DISCIPLINE TRADER.
@Dicaiplinetraders
On this record: Growth · Engagement · Posts · Citations · Cite this entry
21subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003729019825 |
|---|---|
| Type | Channel |
| Username | @Dicaiplinetraders |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 15 September 2026 |
| On Telegram | t.me/Dicaiplinetraders |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 13:54 | 21 | +1 |
| 22 Aug 2026, 14:15 | 20 | +3 |
| 15 Aug 2026, 17:45 | 17 | +2 |
| 11 Aug 2026, 23:01 | 15 | no change |
| 7 Aug 2026, 19:42 | 15 | first reading |
Engagement
20 posts held, back to 3 August 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
4463 IS A STRONG RESISTANCE... PERSONALLY NOW BOOK AT 4431
4415 NOW 4330 TO 4415 NOW
https://t.me/markettalk_s
NIFTY FUTURE UPDATE 🎈 OUR MANTRA NIFTY FUTURE WILL HAVE TO BREAK 💔 24103 THEN ONLY PROBLEM FOR BULLS 🐂!! NIFTY FUTURE WILL FACE HURDLE AT 24729... CROSSOVER WILL TAKE TO 24923... SUPPORT 24592... BREAK 💔 WILL TAKE TO 24450-24393
XAUUSD UPDATE 🎈 SUPPORT 4200... 4330 ABOVE BE READY FOR 4463... STRONG HURDLE 4463 CROSS THEN 4563...
📈 Master All Trading Levels in One Group! 👉🏻Explore Equity, Options, Futures, MCX, Forex, and Bitcoin—all in one place. 👉🏻Join the Top Learning Group👇🏻 1.https://t.me/+tc6UQ9qKqI00NjE1 Join Below channel👇🏻 https://t.me/+DOL8L6WRzacyMDQ1
https://t.me/NiftyMarket
ONCE BREAK 💔 BELOW 4220 THEN MORE DOWNSIDE POSSIBLE...
1ST TARGET 🎯 ALMOST DONE
SELL XAUUSD 4270_4275 SL 4310 TARGET 🎯 4230 OR MORE
Showing the 12 most recent of 20 posts we hold for @Dicaiplinetraders. 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
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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“DISCIPLINE TRADER.” (@Dicaiplinetraders), 21 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/Dicaiplinetraders.
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.