13 Sept 2022, 08:43 UTC174 viewsread 10 August 2026
🟢 10.0 dei redemption occured. 🟢 total dei redeemed: 34,208,780.35 🔍 tx link
Channel
DEUS Notifications
@deus_notifications
On this record: Growth · Engagement · Posts · Cite this entry
54subscribers
-1 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 | -1001587808347 |
|---|---|
| Type | Channel |
| Username | @deus_notifications |
| Created | Between 1 August 2021 and 11 September 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/deus_notifications |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 22:43 | 54 | -1 |
| 10 Aug 2026, 08:15 | 55 | no change |
| 7 Aug 2026, 06:05 | 55 | first reading |
Engagement
20 posts held, back to 11 September 2022 — 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 pageof 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 September 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
13 Sept 2022, 02:56 UTC177 viewsread 10 August 2026
🟢 627.75 dei redemption occured. 🟢 total dei redeemed: 34,208,770.35 🔍 tx link
13 Sept 2022, 02:46 UTC177 viewsread 10 August 2026
🟢 6.31 dei redemption occured. 🟢 total dei redeemed: 34,208,142.6 🔍 tx link
13 Sept 2022, 01:29 UTC178 viewsread 10 August 2026
🟢 15.01 dei redemption occured. 🟢 total dei redeemed: 34,208,136.28 🔍 tx link
12 Sept 2022, 23:37 UTC176 viewsread 10 August 2026
🟢 1.0 dei redemption occured. 🟢 total dei redeemed: 34,208,121.28 🔍 tx link
12 Sept 2022, 23:04 UTC168 viewsread 10 August 2026
🟢 15.27 dei redemption occured. 🟢 total dei redeemed: 34,208,120.28 🔍 tx link
12 Sept 2022, 22:13 UTC121 viewsread 10 August 2026
🟢 4.77 dei redemption occured. 🟢 total dei redeemed: 34,208,105.0 🔍 tx link
12 Sept 2022, 22:09 UTC98 viewsread 10 August 2026
🟢 25.0 dei redemption occured. 🟢 total dei redeemed: 34,208,100.23 🔍 tx link
12 Sept 2022, 22:00 UTC89 viewsread 10 August 2026
🟢 47.64 dei redemption occured. 🟢 total dei redeemed: 34,208,075.23 🔍 tx link
12 Sept 2022, 21:54 UTC82 viewsread 10 August 2026
🟢 10.24 dei redemption occured. 🟢 total dei redeemed: 34,208,027.59 🔍 tx link
12 Sept 2022, 21:53 UTC81 viewsread 10 August 2026
🟢 1.01 dei redemption occured. 🟢 total dei redeemed: 34,208,017.35 🔍 tx link
12 Sept 2022, 18:26 UTC80 viewsread 10 August 2026
🟢 541.64 dei redemption occured. 🟢 total dei redeemed: 34,208,016.34 🔍 tx link
Showing the 12 most recent of 20 posts we hold for @deus_notifications. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“DEUS Notifications” (@deus_notifications), 54 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/deus_notifications.
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.