XAUUSD BUY 4053.46 SL: 4045.34 TP: 4077.34

Channel
BTCUSD FOREX SIGNALS
@BTCUSDFOREXSIGNALI
On this record: Topic · Growth · Engagement · Posts · Cite this entry
213subscribers
-225 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002743461639 |
|---|---|
| Type | Channel |
| Username | @BTCUSDFOREXSIGNALI |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/BTCUSDFOREXSIGNALI |
Topic
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 06:15 | 213 | -53 |
| 19 Sept 2026, 13:40 | 266 | -37 |
| 11 Sept 2026, 02:17 | 303 | -46 |
| 2 Sept 2026, 16:44 | 349 | -59 |
| 27 Aug 2026, 06:55 | 408 | -14 |
| 21 Aug 2026, 02:47 | 422 | -10 |
| 14 Aug 2026, 21:55 | 432 | -6 |
| 8 Aug 2026, 05:15 | 438 | no change |
| 7 Aug 2026, 16:33 | 438 | first reading |
Engagement
20 posts held, back to 31 October 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 20 posts for this entry, the most recent from 10 November 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
⏩GET READY FOR SIGNAL TAP TAP 💫💫
💫Good morning traders! ☀️ It's a new week, and that means new opportunities for us 🪙 Trading isn't just about numbers and charts, it's about patience, resilience and belief in your strategy 📈 Here's to making smart decisions, staying focused, and achieving our trading goals this week. Let's conquer
WEEKLY OUTLOOKS👀
~USDCAD HTF Analysis📉
~EURUSD HTF Analysis📈
~USDCHF HTF Analysis📉
~XAUUSD HTF Analysis📉
GBPJPY H4 SETUP👀
#XAUUSD flying non-stop🔥🔥 Smashed tp1💰💯 +250 pips gained💰😆 sniperrr always🤩🤩
👍🏻👍🏻
#GBPJPY BUY LIMIT @ 201.780 STOPLOSS @ 201.070 TP @ 202.350 TP @ 202.950 TP @ 203.600
Showing the 12 most recent of 20 posts we hold for @BTCUSDFOREXSIGNALI. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“BTCUSD FOREX SIGNALS” (@BTCUSDFOREXSIGNALI), 213 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/BTCUSDFOREXSIGNALI.
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.