9 May 2022, 06:33 UTC≈1,000 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1523551519647223808
Channel
CRYPTO NINJA Channel Announcements
@cryptoninjaupdates
On this record: Growth · Engagement · Posts · Cite this entry
228subscribers
-2 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 | -1001359730209 |
|---|---|
| Type | Channel |
| Username | @cryptoninjaupdates |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/cryptoninjaupdates |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 09:14 | 228 | -1 |
| 14 Aug 2026, 09:28 | 229 | -1 |
| 7 Aug 2026, 02:48 | 230 | no change |
| 7 Aug 2026, 00:20 | 230 | first reading |
Engagement
20 posts held, back to 15 April 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 9 May 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 May 2022, 02:21 UTC974 viewsread 7 August 2026
We pushed the backup version of the updated front end with all the mainnet contracts deployed to it and gave access to the DAO to check it out. The migration and everything went perfect 🐷🚀 There was a discrepancy which caused us to wait until tomorrow to look at everything with fresh eyes, before we start the countdown, to be extra careful. Turns out it was due to the person reporting the discrepancy looking at th…
7 May 2022, 08:18 UTC693 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1522853212583129089
6 May 2022, 03:05 UTC602 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1522412110667345920
2 May 2022, 02:24 UTC641 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1520952151203229696
1 May 2022, 01:23 UTC524 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1520574361568088064
27 Apr 2022, 15:25 UTC537 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1519336636299247616
27 Apr 2022, 02:56 UTC504 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1519148455398342656
27 Apr 2022, 02:02 UTC448 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1519128519439454208
26 Apr 2022, 09:44 UTC358 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1518888579107532801
22 Apr 2022, 16:25 UTC396 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1517517183718662145
21 Apr 2022, 14:23 UTC404 viewsread 7 August 2026
https://twitter.com/cryptoninjaz/status/1517084712162164736
Showing the 12 most recent of 20 posts we hold for @cryptoninjaupdates. 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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“CRYPTO NINJA Channel Announcements” (@cryptoninjaupdates), 228 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/cryptoninjaupdates.
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.