30 Jul 2026, 14:02 UTC18 viewsread 7 August 2026
Photo
We just finished the Audit for BigTr ($BIGTR)! https://github.com/cyberscope-io/audits/blob/main/bigtr/audit.pdf https://cyberscope.io/audits/bigtr
Channel
Cyberscope Official Announcements
@cyberscope_announce
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
310subscribers
-238 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 | -1001209255902 |
|---|---|
| Type | Channel |
| Username | @cyberscope_announce |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/cyberscope_announce |
Topic
Technology — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 07:20 | 310 | -26 |
| 7 Sept 2026, 10:40 | 336 | -22 |
| 30 Aug 2026, 12:13 | 358 | -27 |
| 24 Aug 2026, 06:54 | 385 | -47 |
| 15 Aug 2026, 19:03 | 432 | -115 |
| 7 Aug 2026, 13:44 | 547 | -1 |
| 7 Aug 2026, 11:02 | 548 | no change |
| 7 Aug 2026, 08:25 | 548 | first reading |
Engagement
20 posts held, back to 3 June 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
29 Jul 2026, 13:31 UTC20 viewsread 7 August 2026
Photo
We just finished the Audit for VaultedMetrics ($VM888)! https://github.com/cyberscope-io/audits/blob/main/vm888/auditReserves.pdf https://cyberscope.io/audits/vm888 https://twitter.com/cyberscope_io/status/2082458921558565100
28 Jul 2026, 14:04 UTC18 viewsread 7 August 2026
Photo
We just finished the Audit for smartvault.ai ($SVT)! https://github.com/cyberscope-io/audits/blob/main/1-svt/audit.pdf https://cyberscope.io/audits/1-svt https://twitter.com/cyberscope_io/status/2082105033609359693
28 Jul 2026, 10:14 UTC16 viewsread 7 August 2026
Photo
We just finished the Audit for Hydranet ($HDN)! https://github.com/cyberscope-io/audits/blob/main/2-hdn/audit.pdf https://cyberscope.io/audits/2-hdn https://twitter.com/cyberscope_io/status/2082046988552450264
21 Jul 2026, 09:53 UTC29 viewsread 7 August 2026
Photo
We just finished the Audit for NUMMUS Community ($NUMMUS)! https://github.com/cyberscope-io/audits/blob/main/nummus/audit.pdf https://cyberscope.io/audits/nummus
21 Jul 2026, 07:19 UTC23 viewsread 7 August 2026
Photo
We just finished the Audit for SNVR ($SNVR)! https://github.com/cyberscope-io/audits/blob/main/snvr/audit.pdf https://cyberscope.io/audits/snvr https://twitter.com/cyberscope_io/status/2079466315002019918
20 Jul 2026, 13:55 UTC19 viewsread 7 August 2026
Photo
We just finished the Audit for RobinFlow ($FLOW)! https://github.com/cyberscope-io/audits/blob/main/2-flow/audit.pdf https://cyberscope.io/audits/2-flow https://twitter.com/cyberscope_io/status/2079203649377403259
16 Jul 2026, 11:32 UTC27 viewsread 7 August 2026
Photo
We just finished the Audit for Crush ($CRUSH)! https://github.com/cyberscope-io/audits/blob/main/1-crush/Source_Code_Review.pdf https://cyberscope.io/audits/1-crush https://twitter.com/cyberscope_io/status/2077717787028373822
10 Jul 2026, 17:17 UTC32 viewsread 7 August 2026
Photo
We just finished KYC verification for ChessChain ($CCHN)! https://github.com/cyberscope-io/kyc/blob/main/cchn/kyc.png https://www.coinscope.co/coin/cchn/kyc https://twitter.com/cyberscope_io/status/2075630533350982100
10 Jul 2026, 16:50 UTC24 viewsread 7 August 2026
Photo
We just finished the Audit for ChessChain ($CCHN)! https://github.com/cyberscope-io/audits/blob/main/cchn/audit.pdf https://cyberscope.io/audits/cchn https://twitter.com/cyberscope_io/status/2075623590808961352
10 Jul 2026, 09:46 UTC25 viewsread 7 August 2026
Photo
We just finished the Audit for Kamirai ($KAMIRAI)! https://github.com/cyberscope-io/audits/blob/main/kamirai/audit.pdf https://cyberscope.io/audits/kamirai https://twitter.com/cyberscope_io/status/2075516950780813318
6 Jul 2026, 10:39 UTC32 viewsread 7 August 2026
Photo
We just finished the Audit for CRYMADX Ecosystem / CRYMAD Chain ($CMX-R)! https://github.com/cyberscope-io/audits/blob/main/cmx-r/audit.pdf https://cyberscope.io/audits/cmx-r https://twitter.com/cyberscope_io/status/2074080670104670260
Showing the 12 most recent of 20 posts we hold for @cyberscope_announce. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Cyberscope Official Announcements” (@cyberscope_announce), 310 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/cyberscope_announce.
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.