Photo, posted without a caption
Channel
MissionFX Trading
@OBdicasLucrativas
On this record: Previous handles · Growth · Engagement · Posts · Cite this entry
7,808subscribers
+6,598 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002430017538 |
|---|---|
| Type | Channel |
| Username | @OBdicasLucrativas |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/OBdicasLucrativas |
Previous handles
@OBdicasLucrativas was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 7 August 2026 – 7 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 21:44 | 7,808 | -172 |
| 22 Aug 2026, 16:33 | 7,980 | +6,992 |
| 15 Aug 2026, 18:37 | 988 | -64 |
| 11 Aug 2026, 23:53 | 1,052 | -109 |
| 8 Aug 2026, 18:38 | 1,161 | -49 |
| 7 Aug 2026, 23:17 | 1,210 | no change |
| 7 Aug 2026, 19:38 | 1,210 | first reading |
Engagement
19 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.015%
- avg views ÷ 7,808 subscribers
- Avg views / post
- 1.2
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 19
- of 19 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (6 August 2026 – 7 August 2026) |
| Views total | 22 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
Round 5, Hold? No Problem H4 Setup Still Valid & Still Strong Zone GOLD RUNNING 200+ PIPS Let's collect partial PROFITS and set the rest at BREAKEVEN for a zero-risk trade
Photo, posted without a caption
Gold Sell Now: 4365 - 4370 SL: 4375 TP1: 4360 TP2: 4355
Gold Sell Now High Risk Setup
Gold buy now @ 4284 - 4279 sl : 4274 tp1 : 4289 tp2 : 4294
Gold buy now
📉 MASTERING THE RISING WEDGE BREAKDOWN! 📊 Rising wedges often indicate trend reversals or bearish continuations when the support level breaks. Traders should wait for confirmation (such as structure breaks and retest) before entering trades. A rising wedge can be a ticking time bomb! 💣 📌 Price starts slowing down inside the wedge 📌 Structure breaks, confirming a shift in momentum 📌 A corrective pullback before a st…
There We Go, Recovery Done Quick! GOLD RUNNING 100+ PIPS Let's collect partial PROFITS and set the rest at BREAKEVEN for a zero-risk trade
Gold sell @4264.5 - 4269.5 Sl : 4279.5 tp1 : 4259.5 tp2 : 4254.5
Gold sell now
Hit risk! M5 Engulf failed 😮💨
Showing the 12 most recent of 19 posts we hold for @OBdicasLucrativas. 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“MissionFX Trading” (@OBdicasLucrativas), 7,808 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/OBdicasLucrativas.
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.