📌 Dear stakeholders, We would like to provide a measured update on recent developments affecting DigiCorp Labs. Our legal representative summarises the judgment in the DigiCorp Labs AG / LCX AG case as follows: On 7 May 2026, the Princely Court of Liechtenstein (Fürstliches Landgericht) ruled substantially in favour of DigiCorp Labs AG in its proceedings against LCX AG. The Court ordered LCX AG to pay USD 2.5 mil…

Channel
DigiCorp Labs
@DigiCorpLabs
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
484subscribers
-19 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 | -1001518630288 |
|---|---|
| Type | Channel |
| Username | @DigiCorpLabs |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/DigiCorpLabs |
Topic
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 12 Oct 2026, 21:49 | 484 | -2 |
| 1 Oct 2026, 11:35 | 486 | -4 |
| 13 Sept 2026, 10:01 | 490 | -2 |
| 5 Sept 2026, 00:42 | 492 | -3 |
| 29 Aug 2026, 07:54 | 495 | +1 |
| 23 Aug 2026, 06:38 | 494 | -6 |
| 15 Aug 2026, 10:25 | 500 | -3 |
| 7 Aug 2026, 01:28 | 503 | no change |
| 7 Aug 2026, 01:17 | 503 | first reading |
Engagement
20 posts held, back to 15 June 2025 — 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
📢 Official Reminder As announced this morning, our AMA has been postponed to 21st July. Thank you for your patience and support. We're putting the final touches in place; stay tuned!
Hey Metanauts! The news we hinted at is finally here — our DigiCorp Labs x HSD Premium Partnership announcement (plus interview!) is now live! This is a major catalyst for our mission to build a more secure, sovereign digital Europe — and we’d truly appreciate your support. 👉 Read the full story here: https://www.linkedin.com/posts/security-delta-hsd_we-are-excited-to-announce-that-digicorp-activity-73486219925871…
💡At DigiCorp Labs, we've always believed: Hype gets attention. Trust earns adoption. This video reinforces exactly why we built the DGMV token around verifiable true utility—not manufactured metrics: https://www.linkedin.com/feed/update/urn:li:activity:7347227181321732096
https://x.com/DigiCorpLabs/status/1941066949276185045
💡Questions about how DGMV-ID Password keeps your accounts safe? Drop them below! Let’s build a safer internet together: https://www.linkedin.com/posts/jan-muyldermans-aid5e2818231b63a_16-billion-apple-facebook-google-and-other-activity-7341797578524569600-fb-3?utm_source=share&utm_medium=member_desktop&rcm=ACoAACdfazcBxLaWNez07l2nAnx1FCBlEC-mWT4
DigiCorp Labs pinned «Let us make some things clear… 1. We are not a scam project but a serious company with seasoned professionals developing technology and solutions in line with our vision. We provide updates about our project here: https://www.digicorplabs.com/blog/ 2. We’re…»
DigiCorp Labs pinned «https://twitter.com/DigiCorpLabs/status/1473388138924056582?s=20»
DigiCorp Labs pinned «https://twitter.com/DigiCorpLabs/status/1473341015406878724?s=20»
DigiCorp Labs pinned «https://twitter.com/digicorplabs/status/1473318586391400453?s=21»
DigiCorp Labs pinned «https://twitter.com/DigiCorpLabs/status/1473297798535823360?s=20»
DigiCorp Labs pinned «https://twitter.com/DigiCorpLabs/status/1473246965970395140?s=20»
Showing the 12 most recent of 20 posts we hold for @DigiCorpLabs. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@DigiCorpLabs named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“DigiCorp Labs” (@DigiCorpLabs), 484 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/DigiCorpLabs.
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.