#LON is dry with no #OTE in sight. We ll wait till NY traders up at around 14.00. Otherwise #JOLTS at 17.00 may ignite some actions later in the day.

Channel
TradeFlow™
@txflo
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001608018877 |
|---|---|
| Type | Channel |
| Username | @txflo |
| Description | note all time reference are shown in ᴹᵀ ᵀᴵᴹᴱ |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/txflo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:01 | 4 | no change |
| 11 Aug 2026, 14:17 | 4 | first reading |
Engagement
19 posts held, back to 2 November 2025 — 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 55
- Videos
- 2
- Links
- 28
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Daily Recap
Lets see if the price swings lower towards NYO after failing to close above 50% of the #OB wick... #M01 closeup.
📈 New week, Lets stay composed and focused. As we step into a new week, Leave the past where it belongs — There’s Nothing to chase or recover. Last week is already settled - what counts now is how you show up and execute from here onward. 📌Allow price to reach your area — No chasing. 📌Let the setup Fully develop before Entry. 📌Avoid any forced or low-quality Trades 📌Maintain strict and consistent ris…
We just found out about this really nice feature in #MT4 lets discuss someday .. 📈
Posted without readable text
REVIEW Buy #OTE at #LON 0900 and pre #NYO 1430
#ads. Why give all your trading fees away? 🤔 With the FXStreet Cashback Program, part of your commissions comes back to you, at no cost. 1️⃣ Join in seconds: https://fxstreet.page.link/mX72NHuE2tdCNCCH6 2️⃣ Connect your broker account 3️⃣ Get cashback automatically every time you trade No changes to your strategy. Just a smarter way to trade. Start earning cashback today 💰
Seems #SL just ecaped stop hunts at #NWOG amid rising geo tensions ahead of #Fed week. we expect big drop at #JPX open
We hope the momentum reversed for the buyers following soft US data. Some respite from heavy selling is expected with return to 1.15 zone.
With so much uncertainties over Mid East conflicts, and lost chance to read London market flow, we decide to stay on the sidelines. No trade today.
As expected the price held in range and scissor clipped on the release. Rendering the session untradeable. ref. https://t.me/wnnxt/12937
Showing the 12 most recent of 19 posts we hold for @txflo. 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 2 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“TradeFlow™” (@txflo), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/txflo.
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.