Channel
@mtquantbt
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
450subscribers
+48 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001999579918 |
|---|---|
| Type | Channel |
| Username | @mtquantbt |
| Created | Between 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/mtquantbt |
Technology — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 3 Oct 2026, 21:20 | 450 | +15 |
| 18 Sept 2026, 12:56 | 435 | +15 |
| 9 Sept 2026, 21:39 | 420 | +6 |
| 30 Aug 2026, 18:36 | 414 | +2 |
| 23 Aug 2026, 16:27 | 412 | +3 |
| 15 Aug 2026, 15:27 | 409 | +7 |
| 6 Aug 2026, 19:50 | 402 | no change |
| 6 Aug 2026, 19:47 | 402 | first reading |
20 posts held, back to 10 March 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
59 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 81.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 48 | 81.4% | |
| ❤ | 4 | 6.78% | |
| 🔥 | 4 | 6.78% | |
| 👏 | 3 | 5.08% |
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 13 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 59 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 10 March 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
!!Attention!!, NSE 15:40 changes were already there from the version 1.0.2.97. You can set the Portfolio SqOff / End times accordingly. For the older days tests will run till 15:30 and on and after 03 Aug 2026, tests will run until 15:40.
A new update of mtQuant version 1.0.2.98 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. Backtest Performance is slightly improved. 2. Now the Parallel would start faster and perform backtest much faster than before. Update version you can see at the left bottom of Login Screen.
A new update of mtQuant version 1.0.2.97 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. A few fixes w.r.t the Last Update a) ReEntry wasn’t working as expected due to the newly introduced fields of ReEntry Monitoring Times, it's fixed now. b) In some cases, Positional Portfolios were not executing as expected, fixed now. If you observe any other issues, feel free to DM us …
A new update of mtQuant version 1.0.2.95 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. DTE Based Intraday Port Execution: While creating / modifying the portfolio(s) user can select the Run On Days based on their requirements. However, only in the case of Intraday Portfolio(s), we have now added an option to select either 'Run On Days' or 'DTE'. Now you can see a radio but…
👍4
premium of 60 (30 % of 200)”. It is important to note that it will always use the current straddle premium, whatever premium going on at the time of leg execution. 8. Slightly better speed: Now in case of a backtest, you will get slightly better speed. If you observe any other issues with BTST / TradingView import, feel free to DM us @mtquantsup. Update version you can see at the left bottom of Login Screen.
👍2
A new update of mtQuant version 1.0.2.94 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. Few fixes rolled in this update 1. In a very peculiar situation, where the user was testing where some portfolios having SqOff time set and he has also selected a few ports where SqOff time was set as 00:00:00 moreover User SqOff and Strategy SqOff wasset as 00:00:00 or after the trading ses…
❤1👍1
A new update of mtQuant version 1.0.2.92 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. Import of Multiple .Port files in one go : Now while importing the portfolio files, you can select multiple files and can import all of them in a single click. 2. Dynamic Hedge: In some rare cases of dynamic hedge, double dynamic hedge legs were getting created and executed. It's fixed …
👍5❤2
A new update of mtQuant version 1.0.2.91 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. Changes in the BTST Logic : As already mentioned in the previous posts, In the case of BTST there can be 2 types of Ports, one which can have Start Time greater than the SqOff Time and Ports where SqOff time is greater than Start Time. Lets understand with an example. a) Start Time Great…
👍5👏1
!!Attention!!, Some Users are facing issues for SENSEX for the 11th June Expiry, those All Users are requested to follow the below steps. 1. Click Settings > Cache Manager. 2. Enter -4179-4179 and the click Clean 3. Restart the mtQuant.
!!Attention!!, We allow Max One Change computer requests on a Calendar day. To change the computer, at the login screen, just enter the correct User ID and Password and then click “Need to change computer?”. We won’t be able to entertain any second computer change request if the one change is already done for the day. Thanks
A new update of mtQuant version 1.0.2.90 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. CSV / Excel Import: In the case of TradingView based Excel / CSV Import, a few entries were getting missed from the backtest. It's fixed now. If you observe any other issues with TradingView import, feel free to DM us @mtquantsup. Update version you can see at the left bottom of Login S…
A new update of mtQuant version 1.0.2.89 was rolled out. When you restart the mtQuant, click ‘Yes’ to update the application. 1. Add Dynamic Slippage: mtQuant was already having a functionality to add the Dynamic slippage, However that was implemented for the Market Orders only. Now the dynamic slippage will work for LIMIT and SL Orders as well. If ticked, the System will add a slight slippage as per the dynamics …
👍8
Showing the 12 most recent of 20 posts we hold for @mtquantbt. 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“mt QUANT - Advanced Options Analytics / Backtesting Platform” (@mtquantbt), 450 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/mtquantbt.
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.