Channel
@Goldsclapnigmaster
On this record: Topic · Growth · Engagement · Posts · Cite this entry
98subscribers
-15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004353568034 |
|---|---|
| Type | Channel |
| Username | @Goldsclapnigmaster |
| Created | Between 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/Goldsclapnigmaster |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 13 Oct 2026, 08:27 | 98 | -2 |
| 2 Oct 2026, 19:58 | 100 | -1 |
| 10 Sept 2026, 10:40 | 101 | -2 |
| 31 Aug 2026, 17:11 | 103 | -1 |
| 24 Aug 2026, 13:17 | 104 | -5 |
| 16 Aug 2026, 20:09 | 109 | -4 |
| 9 Aug 2026, 06:31 | 113 | no change |
| 7 Aug 2026, 19:42 | 113 | first reading |
20 posts held, back to 5 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Happy Weekend, Guy's! 💥💥 We secured good profits and captured solid pips this week. Big thanks to everyone for staying disciplined and sticking to the plan. Enjoy your weekend — next week, we aim even higher! Discipline and consistency lead to results.➡️🕯✅✅
📊READY FOR XAUUSD NEW SIGNAL VIP TRADE GUYS↗️📉✅
↗️ #XAUUSD_SeLL ↗️ DONE 200+ PIP'S💥 COMPLETED ALL TARGET ENJOY PROFIT MY LOYAL MEMBERS 💸💸💯 📊📊💥💥💥💥💥💥📊📊
#XAUUSD_SELL📈 TP_6 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD_SELL📈 TP_5 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD_SELL📈 TP_4 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD_SELL📈 TP_3 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD_SELL📈 TP_2 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD_SELL📈 TP_1 HIT WITH BOOM PROFITS✅✅🔥
#XAUUSD SELL 4261/4258 💠Sl 4288 TP¹ 4258✅ TP² 4255✅ TP³ 4252✅ TP⁴ 4249✅ TP⁵ 4247✅ TP⁶ 4245✅ Follow guys money management💯
Good morning dear memebers
#𝗫𝗔𝗨𝗨𝗦𝗗 BUY 🤑 TP1𝐇𝐈𝐓 50+ PIPS PROFIT DONE ✅✌️
Showing the 12 most recent of 20 posts we hold for @Goldsclapnigmaster. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Gold Scalping Master” (@Goldsclapnigmaster), 98 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/Goldsclapnigmaster.
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.