The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 8 days, that account will self-destruct and this channel may no longer have an owner.

Channel
DC Oracle
@DCOracle
On this record: Growth · Engagement · Posts · Cite this entry
101subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001222966182 |
|---|---|
| Type | Channel |
| Username | @DCOracle |
| Created | 29 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/DCOracle |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 00:32 | 101 | -1 |
| 27 Aug 2026, 04:17 | 102 | -1 |
| 13 Aug 2026, 18:27 | 103 | -1 |
| 9 Aug 2026, 09:17 | 104 | no change |
| 6 Aug 2026, 21:30 | 104 | first reading |
Engagement
20 posts held, back to 4 July 2021 — 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 13 March 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
https://twitter.com/oracle_dc/status/1439397523421081602
https://twitter.com/oracle_dc/status/1439302685799419905?s=20
https://twitter.com/oracle_dc/status/1439300153324810240?s=20
https://twitter.com/oracle_dc/status/1439288233691582469
https://twitter.com/oracle_dc/status/1439283588462223361
https://twitter.com/oracle_dc/status/1439281792104677384
https://twitter.com/oracle_dc/status/1439271877067878402
https://twitter.com/oracle_dc/status/1439267454929313807
https://twitter.com/oracle_dc/status/1439259269715595264
https://twitter.com/oracle_dc/status/1439249423092027399
Showing the 12 most recent of 20 posts we hold for @DCOracle. 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“DC Oracle” (@DCOracle), 101 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/DCOracle.
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.