Telegram RegisterThe public register of Telegram

Channel

Delysium - Announcement

@DelysiumOfficial

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

6,015subscribers

-22 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001741219122
TypeChannel
Username@DelysiumOfficial
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/DelysiumOfficial

Growth

6,0156,0376,0267 August 2026 — 6,037 subscribers7 August 2026 — 6,037 subscribers10 August 2026 — 6,024 subscribers13 August 2026 — 6,015 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -22. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6,012–6,040 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:176,015-9
10 Aug 2026, 02:336,024-13
7 Aug 2026, 09:306,037no change
7 Aug 2026, 09:216,037first reading

Engagement

20 posts held, back to 6 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.44%
avg views ÷ 6,015 subscribers
Avg views / post
327
2 posts measured
Reaction rate
1.71%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held20 (6 January 202628 July 2026)
Views total654
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:37 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 11s
Average length
36s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

52 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 42.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2242.3%
1426.9%
👍815.4%
❤‍🔥59.62%
💯35.77%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 18 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 52reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 January 2026 to 28 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Jul 2026, 14:55 UTC304 viewsread 12 August 2026
Photo

The future of Agent Economy just got a speed boost. We’ve optimized Lucy’s intent-parsing engine to better understand the nuances of your voice. Whether it’s complex trading or creative automation, the new "Skill Orchestrator" ensures everything runs like clockwork. More precision. Less waiting. Total intelligence. Try the updated Lucy: https://www.lucyos.ai

22 Jul 2026, 13:06 UTC350 views6 reactionsread 12 August 2026
Photo

Agents can already move money. The next evolution? Enabling them to decide when and if they should move it. Through our strategic partnership with @InSoBlokAI, Lucy will be integrated with a sophisticated "Trust Layer." By leveraging TasteScore’s real-time behavioral evaluation across 100M+ wallets, Lucy will soon be able to: · Identify malicious counterparties & compromised wallets before interaction. · Evaluate o

👍3🔥21

10 Jul 2026, 17:00 UTC432 viewsread 12 August 2026
Photo

The future of the Agent Economy requires more than static apps, it demands a seamless execution layer. We are thrilled to partner with @ClusterProtocol, an Orchestration layer and open infra of private AI for autonomous workflows on Base. Together, we are bridging Lucy’s positioning as the Crypto Agentic Operating System with Cluster's robust compute, confidential payment frameworks , and developer ecosystems. From

29 Jun 2026, 12:26 UTC545 views3 reactionsread 12 August 2026
Video

Text-only AI is a bottleneck. When you ask @LucyOSAI for macro data, you don't just get raw text, you get a custom, reactive micro-agent compiled on the fly. By bridging @Nasdaq feeds and crypto inputs via MCP, Lucy compiles a fully responsive macro dashboard directly in your workspace. Drag the timeline, watch the gauge recalculate the alignment, and manipulate the data yourself. No raw text. Just elegant orchestr

3

24 Jun 2026, 13:41 UTC532 views4 reactionsread 12 August 2026
Photo

Intelligence needs proof. Lucy is joining forces with @layeredge to bridge the gap between AI execution and decentralized trust. From recursive proofs to multi-L1 anchoring, we’re ensuring that every step Lucy takes is backed by the most advanced verification infrastructure in crypto. The future is autonomous. The future is verified.

👍4

22 May 2026, 06:13 UTC553 views4 reactionsread 12 August 2026
Photo

Lucy x @APRO_Oracle: Powering AI Agent Autonomy with Real-time Verifiable Data The rise of the AI Agent economy demands systems capable of extracting value from real-time data and executing sophisticated strategies. The collaboration between @LucyOSAI and APRO provides precision navigation for large-scale Agent coordination. With APRO’s 1400+ data feeds and rapid response times, Lucy ensures that AI Agents have acce

🔥31

13 May 2026, 15:21 UTC451 views3 reactionsread 12 August 2026
Photo

Empower your Hermes Agent @NousResearch with @LucyOSAI Beyond static execution. The updated Lucy Token Analysis Skill for Hermes Agent introduces a strategic persistence layer. By leveraging a reflective reasoning loop, the skill no longer just processes data: it learns from it, refining evaluation strategies through persistent file updates to ensure peak accuracy for deep market synthesis. Advanced infrastructure

🔥3

7 May 2026, 10:22 UTC488 views4 reactionsread 12 August 2026
Photo

Lucyos.ai x 4AI: Simplifying the Future of AI Integration. This collaboration marks a significant step in our mission to create a versatile and developer-friendly environment for Agents. By integrating 4AI’s cutting-edge tools into Lucy’s ecosystem, we are accelerating the transition toward a future where sophisticated AI integration requires minimal effort. Streamlining intelligence, one integration at a time.

🔥4

4 May 2026, 04:42 UTC425 views2 reactionsread 12 August 2026
Photo

Delysium’s May Event Calendar What’s scheduled: 🔹Early May: Lucy Partnership Announcement 🔹May 13: Launch Lucy Token Analysis Skills for Hermes 🔹Mid May: Lucy Partnership Announcement 🔹May 19: Lucy use case showcase 🔹May 20: Lucy product update and experience optimization 🔹Late May: Update Skill upload interface for Lucy Skillhub 🔹May 29: Community AMA

🔥2

4 May 2026, 04:40 UTC337 views1 reactionsread 12 August 2026
Photo

Lucy x Nebulai: A new synergy in AI infrastructure. We are excited to announce our partnership with Nebulai.network, the OpenCompute infrastructure for AI. By integrating LucyOS.AI’s intuitive agent interface with Nebulai’s decentralized compute network, we are ensuring that every Agent has the high-performance fuel it needs to execute complex tasks with unprecedented efficiency. Building a more robust foundation f

🔥1

1 Apr 2026, 16:06 UTC466 views2 reactionsread 12 August 2026
Photo

Delysium's April Event Calendar What’s scheduled: 🔹 April 2 - Release: Delysium Roadmap Article 🔹 Early April - Lucy Partnership Announcement #1 🔹 April 14 - Lucy Skills Marketplace Launch 🔹 Mid April - Lucy Partnership Announcement #2 🔹 April 20 - Lucy Partnership Use Case 🔹 Late April - Lucy Product Update and Experience Optimization 🔹 April 30 - Community AMA

2

30 Mar 2026, 16:52 UTC478 views1 reactionsread 12 August 2026
Video

Lucy & APRO Oracle Integration Announcement The future of AI-driven social insights is here. Lucy just integrated with APRO Oracle to bring you LIVE social sentiment and prediction market trends. From $DOGE hype to Kalshi odds, Lucy’s got the alpha you need, when you need it. Check out the usecase!

🔥1

Showing the 12 most recent of 20 posts we hold for @DelysiumOfficial. 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.

Citation-graph rank

Citation-graph rank — 550,483 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Bridge Oracle
@Bridge_Oracle · 131,265
Telegram ranks this channel #31 of 72 here — alongside 71 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Delysium - Announcement” (@DelysiumOfficial), 6,015 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DelysiumOfficial.

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.