Channel
ORACLE | Gold Scalper
@btc_oracless
On this record: Growth · Engagement · Cite this entry
7,181subscribers
+88 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 | -1002380219368 |
|---|---|
| Type | Channel |
| Username | @btc_oracless |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/btc_oracless |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 14:18 | 7,181 | +1 |
| 2 Sept 2026, 18:42 | 7,180 | -1 |
| 30 Aug 2026, 13:24 | 7,181 | +4 |
| 27 Aug 2026, 16:43 | 7,177 | +11 |
| 26 Aug 2026, 22:10 | 7,166 | no change |
| 24 Aug 2026, 14:54 | 7,166 | +19 |
| 20 Aug 2026, 14:47 | 7,147 | +7 |
| 17 Aug 2026, 12:08 | 7,140 | +40 |
| 13 Aug 2026, 23:17 | 7,100 | +1 |
| 10 Aug 2026, 09:01 | 7,099 | +5 |
| 7 Aug 2026, 18:26 | 7,094 | +1 |
| 7 Aug 2026, 15:32 | 7,093 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“ORACLE | Gold Scalper” (@btc_oracless), 7,181 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/btc_oracless.
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.