XAUUSD SELL ENTRY TP 4 HITT 120+PIP'S DONE PROFIT
π¨βπ»2π2β‘1π1π₯1

Channel
@btcusdsignalofficials1
On this record: Topic Β· Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Handles named that no longer answer Β· Cite this entry
99,553subscribers
-60,834 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 31,623β100,000.
| Telegram ID | -1001588585256 |
|---|---|
| Type | Channel |
| Username | @btcusdsignalofficials1 |
| Description | βοΈBEST Technical Analysis βοΈBest Trader - Master Of Market βοΈ FREE EDUCATION ( Ebook ) βοΈ FREE SIGNAL ( 95% winning rate ) βοΈ FREE MAPPING βοΈ TP AND SL PROVIDED πππ @BTC_ADMINISTRATION |
| Created | Between 1 August 2021 and 28 February 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/btcusdsignalofficials1 |
Crypto & trading β a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channelβs own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 26 Sept 2026, 17:17 | 99,553 | -1,394 |
| 19 Sept 2026, 15:39 | 100,947 | -337 |
| 17 Sept 2026, 02:38 | 101,284 | -302 |
| 15 Sept 2026, 06:19 | 101,586 | -2,992 |
| 13 Sept 2026, 13:15 | 104,578 | -1,032 |
| 11 Sept 2026, 18:38 | 105,610 | -4,059 |
| 9 Sept 2026, 09:01 | 109,669 | -3,145 |
| 5 Sept 2026, 22:21 | 112,814 | -3,718 |
| 3 Sept 2026, 20:18 | 116,532 | -514 |
| 2 Sept 2026, 10:37 | 117,046 | -482 |
| 1 Sept 2026, 07:15 | 117,528 | -276 |
| 31 Aug 2026, 08:37 | 117,804 | -228 |
| 30 Aug 2026, 08:55 | 118,032 | -247 |
| 29 Aug 2026, 05:53 | 118,279 | -410 |
| 28 Aug 2026, 03:04 | 118,689 | -182 |
| 27 Aug 2026, 01:12 | 118,871 | -146 |
| 26 Aug 2026, 02:44 | 119,017 | -3,885 |
| 25 Aug 2026, 00:05 | 122,902 | -3,069 |
| 23 Aug 2026, 09:58 | 125,971 | -364 |
| 21 Aug 2026, 23:54 | 126,335 | first reading |
1,214 posts held, back to 7 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 114 pages of Telegramβs post history, 20 posts per page.
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. It is computed over the 273 of 711 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days Β· latest post in window 1 October 2026 |
|---|---|
| Posts held | 1,214 (7 August 2026 β 1 October 2026) |
| Views total | 341,569 |
| Reactions total | 541 |
| Forwards / comments | not exposed by the public surface β not measured, not estimated |
| Readings taken | 1 Oct 2026, 11:34 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.
Lifetime counters from Telegramβs own channel header, read 1 October 2026 β not the date at the top of this page, which is when the subscriber count was last read. A count marked β was rounded by Telegram before we ever saw it β t.me prints these counters in full below 1,000 and to three significant figures above, so β142,000 means somewhere between 141,500 and 142,499.
Measured directly from 12 videos 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.
650 reactions across 324 posts, in 29 distinct kinds. The most used accounts for 31.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 207 | 31.8% | |
| β€ | 195 | 30.0% | |
| π | 43 | 6.62% | |
| π₯ | 37 | 5.69% | |
| π― | 22 | 3.38% | |
| π | 19 | 2.92% | |
| π | 14 | 2.15% | |
| β‘ | 12 | 1.85% | |
| π | 12 | 1.85% | |
| πΎ | 9 | 1.38% | |
| π«‘ | 9 | 1.38% | |
| π³ | 8 | 1.23% | |
| π | 7 | 1.08% | |
| π¨βπ» | 7 | 1.08% | |
| β€βπ₯ | 5 | 0.769% | |
| π | 5 | 0.769% | |
| π | 5 | 0.769% | |
| π | 5 | 0.769% | |
| π₯° | 5 | 0.769% | |
| π | 3 | 0.462% | |
| 9 further kinds | 21 | 3.23% |
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 328 of the 1,000 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 650 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 1 October 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.
XAUUSD SELL ENTRY TP 4 HITT 120+PIP'S DONE PROFIT
π¨βπ»2π2β‘1π1π₯1
XAUUSD SELL ENTRY TP 3 HITT 90+PIP'S DONE PROFIT
β€1π1π1π₯1
XAUUSD SELL ENTRY TP 2 HITT 60+PIP'S DONE PROFIT
β€1π1π―1
XAUUSD SELL ENTRY TP 1 HITT 30+PIP'S DONE PROFIT
β€1π1
WOW XAUUSD AMAZING CHECK NOW 4153
π1
XAUUSD SELL 4163/4168β β β β TP 4160π TP 4157π TP 4154π TP 4151π TP 4148π TP 4145π TP 4142π SL 4179β
β€3π2π1π1π1
XAUUSD SELL 4162 πππ
β€2π1
Active πβ
π1
Active πβ
π1
Active πβ
π1
Active πβ
π1
Ready for signalβοΈ
π3β€2
Showing the 12 most recent of 1,214 posts we hold for @btcusdsignalofficials1. 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.
@btcusdsignalofficials1 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleβs history β see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today β not that anything βdiedβ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant β a genuine, evidenced change, not an inference from absence.
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 26 September 2026 β this entry's latest reading, not the date you are reading this.
βBTC/USD FOREX SIGNALS (π)β (@btcusdsignalofficials1), 99,553 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/btcusdsignalofficials1.
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.