5 Aug 2026, 11:32 UTC221 viewsread 7 August 2026
Photo
https://x.com/myalgomate/status/2084965547729617076?s=46
Channel
MyAlgoMate
@myalgomate
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,842subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001209307518 |
|---|---|
| Type | Channel |
| Username | @myalgomate |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/myalgomate |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 03:57 | 1,842 | -3 |
| 2 Sept 2026, 02:33 | 1,845 | -1 |
| 30 Aug 2026, 06:19 | 1,846 | -3 |
| 27 Aug 2026, 06:33 | 1,849 | -2 |
| 24 Aug 2026, 01:03 | 1,851 | -1 |
| 17 Aug 2026, 17:35 | 1,852 | -6 |
| 14 Aug 2026, 19:09 | 1,858 | -3 |
| 8 Aug 2026, 08:01 | 1,861 | -1 |
| 7 Aug 2026, 15:32 | 1,862 | no change |
| 7 Aug 2026, 12:54 | 1,862 | first reading |
Engagement
20 posts held, back to 22 October 2024 — 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
12 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 83.3% | |
| 👍 | 1 | 8.33% | |
| 🤩 | 1 | 8.33% |
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 8 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 12 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 22 October 2024 to 5 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.
Recent posts
31 Mar 2026, 14:31 UTC≈2,140 views1 reactionsread 7 August 2026
Photo
📌 Service Support Update Due to increased query volume related to recent regulatory changes, response times may be slightly longer than usual over the next few days. For any assistance, please share your query on WhatsApp at +91-8866122446. This helps us track and address each request properly. We request you to avoid direct calls, as this may delay the process. Please be assured that every query will be attended…
❤1
18 Oct 2025, 10:03 UTC≈1,220 viewsread 7 August 2026
https://x.com/myalgomate/status/1979078798487306418?s=46
18 Oct 2025, 10:03 UTCviews —
MyAlgoMate pinned a photo
10 Oct 2025, 05:39 UTC≈1,510 views3 reactionsread 7 August 2026
Photo
Photo, posted without a caption
❤2🤩1
27 Aug 2025, 06:55 UTC≈1,790 views2 reactionsread 7 August 2026
Photo
⚖️ TBSS V3 Update – Advanced RMS Settings 🔹 Control your risk with powerful features: Max Profit & Max Loss Trail Max Loss to dynamically secure gains Protect Profit to lock profits as they rise ⏰ Configure how often these checks run: on live price or candle closing basis. 🚨 Choose your exit modes: Delayed Exit: Exit after a configured delay time in seconds Consecutive Ticks Exit: Exit only if Max Profit or M…
❤2
27 Aug 2025, 06:47 UTC≈1,090 views1 reactionsread 7 August 2026
Photo
♻️ TBSS V3 Update – Re-Entry & Re-Execute on Combined SL/Target! 🔹 You can now configure re-entry and re-execute settings on the combined Stoploss (SL) or Target, just like you do for individual legs. 🔹 This allows portfolio-level risk management with fresh entries triggered on combined SL or Target conditions. Customize combined portfolio re-entries with the same flexibility and control as single leg strategies! …
❤1
27 Aug 2025, 06:46 UTC905 viewsread 7 August 2026
Photo
🔄 TBSS V3 Update – Re-Execute Portfolio Settings! ▪️ If any one leg of your multi-leg strategy exits due to Stoploss or Target, all legs exit together. ▪️ Then, the system re-enters all legs simultaneously with fresh contract selection to restart the portfolio. ⏱️ Choose how re-execution happens: Immediate – Re-enter as soon as all legs exit Next Candle Close – Wait for the next candle close before re-entry 🔢 Yo…
27 Aug 2025, 06:41 UTC645 viewsread 7 August 2026
🛡 TBSS V3 Update – Hedge Configuration for Main Legs! 🔹 Configure smart hedge execution for all your main strategy legs. 🔹 Choose when to execute hedge: Execute hedge first, then enter the main leg (useful when margin is limited) Place hedge and main leg orders simultaneously (when you have free margin), for faster start-of-day execution 🔹 During re-entry/re-execute, hedge leg automatically exits and re-enters a…
27 Aug 2025, 06:38 UTC567 views1 reactionsread 7 August 2026
🔄 TBSS V3 Update – Re-Entry Options: 1️⃣ Re-Entry @ Cost 2️⃣ Re-Execute 3️⃣ Re-Execute Reverse ⚙️ You can configure different settings for exit on Stoploss (SL) or exit on Target. 📊 If SL or Target is based on the underlying price, re-entry will also work based on the underlying price. ⏳ For LTP-based re-entry, you have the option to place the re-entry order in advance or wait to place it only on trigger—giving …
❤1
27 Aug 2025, 06:35 UTC556 viewsread 7 August 2026
🛑🎯 TBSS V3 Update – Flexible SL & Target Settings + Re-Entry & Re-Execute! 🔹 Choose to set Stoploss (SL) and Target based on either Option Price or Underlying Price. 🔹 You can also configure separate re-entry and re-execute settings for both Stop loss and Target conditions. Customize your risk management and re-entry strategy individually for each leg with advanced control! ⚙️🔄📈 💬 WhatsApp inquiry: https://wa.link…
27 Aug 2025, 06:31 UTC575 viewsread 7 August 2026
🎯 TBSS V3 Update – More Control with Advanced Strike Selection! 🔹 Configure different strikes for each leg with precise control. Choose the strike selection method that fits your strategy: 1️⃣ ATM Points – Select strikes based on steps away from ATM 2️⃣ ATM % – Select by percentage distance from ATM price 3️⃣ Direct Strike Input – Manually enter exact strike price 4️⃣ Closest Premium – Pick options closest to your …
Showing the 12 most recent of 20 posts we hold for @myalgomate. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“MyAlgoMate” (@myalgomate), 1,842 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/myalgomate.
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.