Channel
@r_algotrading
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
58subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001515057158 |
|---|---|
| Type | Channel |
| Username | @r_algotrading |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 2 October 2026 |
| On Telegram | t.me/r_algotrading |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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, 17:01 | 58 | +1 |
| 9 Sept 2026, 04:00 | 57 | +1 |
| 29 Aug 2026, 22:53 | 56 | +1 |
| 10 Aug 2026, 08:30 | 55 | no change |
| 7 Aug 2026, 04:11 | 55 | first reading |
15 posts held, back to 6 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 15 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
What are the common mistakes in systematic models and infra that people make? Hey so I've recently been working on a backtesting engine for a personal project and I've been reading up on survivorship bias, fees, slippage, taxes, margin rules, regulations (Reg T) etc to try and get a very precise result on my strategies. Currently the workflows start with you doing some research, then testing out strategies, then la…
White’s reality check crapped all over 1.4 million models Finally ran white’s reality check on my big mean reversion parameter sweep. The adjusted reality check p value for the entire run is 0.58. This is very disappointing. I used 0% return for the null. I tried running Hansen’s superior predictive ability. The p value was 0.65. Filtering out low returns and high drawdowns improved the p to 0.47. I clearly haven’…
Photo, posted without a caption
Various high performing switchboards OOS last year https://redd.it/1vjuk5b @r_algotrading
It works but not sure why! https://redd.it/1vjruzc @r_algotrading
Anyone created a successful EA? Hi all, just a genuine question. Iv been doing market research using python and the more I test the more im discovering how random the market is. I’ve been researching market structure but also testing simple strategies and common ones that some people swear by such as ORB for one example. All of which fail over multiple years. It just makes me curios if anyone here has genuinely been…
Alpaca historical IEX data missing for SPY on March 10, 2025, anyone else seeing this or know why? I’m building a local historical dataset for SPY/0DTE backtesting using Alpaca, and I ran into a strange hole in their historical IEX stock data. For SPY on March 10, 2025, querying 1-minute bars with: `feed=iex` timeframe=1Min regular market session SPY returns zero bars. I initially found it because my backtest…
IBKR paper API unreliable and inconsistent https://preview.redd.it/4aq6a2ajmzhh1.png?width=2992&format=png&auto=webp&s=0b1c71a15ad6128ddc1cae677177afee942af6a3 Anyone else running into stuff like this? I'm finding the IBKR API to be completely unusable for any algo trading, it just cannot be trusted. https://redd.it/1vi7087 @r_algotrading
how many strategies did you kill before the one you posted ok so this bugs me about basically every writeup here. we get the sharpe, the max DD, the cost assumptions. we never get the graveyard. went back through my notes and actually counted. 61 configs, \~5 months. kept 2. and like... if I had zero edge and just rolled 61 times, best of 61 still looks fine? so I genuinely can't tell if my two are real or if I jus…
I backtested the Powell 10am strategy on NQ... the results were surprising. https://redd.it/1vhl6d0 @r_algotrading
How has your strategy held up post-2020 vs. pre-2020 I'm doing a sanity check on strategy performance across different market regimes and wanted to check in with the community Also how your max dd compare? Please only answer if you traded your strategy live for a good time (compared to sample size) https://redd.it/1vhe9v7 @r_algotrading
Photo, posted without a caption
Showing the 12 most recent of 15 posts we hold for @r_algotrading. 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 6 registered channels — 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“/r/algotrading” (@r_algotrading), 58 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/r_algotrading.
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.