Telegram RegisterThe public register of Telegram

Channel

Cora ai

@coraaivault

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

10,988subscribers

-678 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003938378967
TypeChannel
Username@coraaivault
Created15 May 2026measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/coraaivault

Growth

10,98811,66611,3277 August 2026 — 11,666 subscribers8 August 2026 — 11,518 subscribers9 August 2026 — 11,423 subscribers10 August 2026 — 11,263 subscribers11 August 2026 — 11,150 subscribers12 August 2026 — 11,001 subscribers13 August 2026 — 10,988 subscribers7 August 202613 August 2026
7 measurements spanning 6 days, net -678. 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 10,886–11,768 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:0410,988-13
12 Aug 2026, 05:1811,001-149
11 Aug 2026, 06:4211,150-113
10 Aug 2026, 09:3011,263-160
9 Aug 2026, 07:1211,423-95
8 Aug 2026, 10:1511,518-148
7 Aug 2026, 12:3111,666first reading

Engagement

17 posts held, back to 15 May 2026the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
51.0%
avg views ÷ 10,988 subscribers
Avg views / post
5,610
2 posts measured
Reaction rate
2.78%
reactions ÷ views · ER floor
Posts in window
2
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 July 2026
Posts held17 (15 May 202630 July 2026)
Views total11,210
Reactions total312
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 04:28 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
16s
Average length
16s

Measured directly from 1 video 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

15,720 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 17.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2,73217.4%
👍2,69017.1%
🤩2,62516.7%
🔥2,53416.1%
🎉2,45915.6%
🥰7024.47%
❤‍🔥6704.26%
💯6584.19%
😍6504.13%

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 16 of the 17 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 15,720reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 15 May 2026 to 30 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

30 Jul 2026, 11:22 UTC≈2,430 views66 reactionsread 13 August 2026
Forwarded from @KuCoin_Web3WalletPhoto

🎉 KuCoin Web3 Wallet x Cora AI #Airdrop 🏆 Up to 1,000,000 $CRVT | 3,000 winners 🗓 2026/07/23 08:00 - 2026/08/23 08:00 UTC 🔥Hold ≥ 10 USD worth of assets on BSC via KuCoin Web3 1⃣️Join now here:https://www.kucoin.com/web3/starter-task?activityId=143 2⃣️Learn More: https://www.kucoin.com/web3/support/48142946142306

55😍6👍5

17 Jul 2026, 10:26 UTC≈8,780 views246 reactionsread 13 August 2026
Forwarded from @Bitget_Wallet_AnnouncementPhoto

🔥 1,000,000 CRVT giveaway is here! 🔥 🕙 Jul 17 - Jul 29 18:00 UTC+8 1️⃣ Download Bitget Wallet 2️⃣ Reward Hub > Join event & complete tasks, and share a total prize pool of 1,000,000 CRVT!

👍12382🔥41

22 Jun 2026, 14:45 UTC≈14,300 views607 reactionsread 13 August 2026

https://x.com/i/status/2069045269631467946 Coraaivault among the top 10 fundraised project by coinmarketcap

🤩13199🥰72😍59👍56🎉54💯53❤‍🔥47

21 Jun 2026, 18:24 UTC≈13,700 views2,094 reactionsread 13 August 2026
Video

Every great Web3 project begins with one decision: Choose transparency over promises. CoraAiVault empowers builders to lock tokens, secure liquidity, and prove long-term commitment through immutable smart contracts. 🔒 Trust isn't a marketing strategy. It's infrastructure. Build with confidence. Build with CoraAiVault. #CoraAiVault #Web3 #BNBChain #Crypto #Blockchain #BuildInPublic

🥰251❤‍🔥249🔥240💯237🤩229🎉226225😍219

20 Jun 2026, 19:02 UTC≈8,570 views537 reactionsread 13 August 2026
Photo

The future of Web3 isn't built on promises; it's built on proof. CoraAiVault is creating a world where every project can demonstrate trust through transparent, immutable, and verifiable smart contracts. 🔒 Trust enforced by code. ⚡ Verification in seconds. 🚀 Infrastructure for the next generation of builders. The trust layer for Web3 starts here. #CoraAiVault #Web3 #BNBChain #Crypto #BuildInPublic #Blockchain

👍77🔥76❤‍🔥64💯5957😍56🤩53🎉50

16 Jun 2026, 16:52 UTC≈4,640 views1,053 reactionsread 13 August 2026
Photo

Trust isn't something that should be claimed—it should be proven. We shared why we built CoraAiVault, our vision for Web3, and how we're creating infrastructure that helps projects earn credibility through transparent on-chain verification. Read the full article on Paragraph: https://paragraph.com/@publication-1781627007418/building-the-trust-layer-for-web3-with-coraaivault?referrer=0x1EDb1C265208d9c2C105Fd0c254c3

👍127🔥123🎉120🤩117❤‍🔥116🥰116😍113💯111

16 Jun 2026, 16:52 UTC≈3,400 views518 reactionsread 13 August 2026
Photo

We're excited to announce that CoraAiVault has successfully raised $2.5M across our Angel and Strategic Rounds This milestone accelerates our mission to build trusted Web3 infrastructure through token locking, liquidity locking, vesting, and transparent onchain verification. A huge thank you to our investors, partners, and community for believing in the vision. This is just the beginning

👍69🤩66🥰64🔥61🎉60😍55💯5150

28 May 2026, 14:04 UTC≈2,730 views849 reactionsread 13 August 2026
Photo

🎙️ Cora Ai AMA Tomorrow • 8 AM • X Spaces Ask the team anything about: 🔒 Token Locks ⏳ Vesting 🌐 On-chain Trust 🚀 Future Plans Your questions. Our answers. See you there 👀 #Web3 #Crypto #BNBChain

👍114🤩99🥰99🔥93💯92😍92🎉89❤‍🔥87

24 May 2026, 05:24 UTC≈2,000 views529 reactionsread 13 August 2026
Photo

The future of Web3 will belong to projects that prioritize transparency over hype. 🔒 Cora Ai is building infrastructure where trust is verifiable on-chain through token locks, vesting, and liquidity security. Secure. Transparent. Decentralized. #Web3 #Crypto #BNBChain

🎉70❤‍🔥65🔥6360🤩56👍55💯55🥰55

18 May 2026, 11:49 UTC≈2,350 views2,032 reactionsread 13 August 2026
Photo

Web3 doesn’t survive on hype alone. It survives on transparency, security, and trust. CoraAiLocker is building the infrastructure that helps projects prove all three. 🔒 #CoraAiLocker #Crypto #Web3

433🤩412👍407🎉399🔥381

18 May 2026, 08:59 UTC≈1,420 views1,111 reactionsread 13 August 2026
Photo

A token lock is more than security. It’s a public signal that a project is committed long term. CoraAiLocker is building the infrastructure behind that trust. 🔒 #CoraAiLocker #DeFi #Web3

237🔥233🤩228🎉207👍206

18 May 2026, 02:51 UTC≈1,790 views1,259 reactionsread 13 August 2026
Photo

Investors don’t trust promises. They trust locked liquidity, transparent vesting, and secure smart contracts. That’s the future CoraAiLocker is building. 🔒 #CoraAiLocker #Crypto #Web3

🤩266👍263259🎉239🔥232

Showing the 12 most recent of 17 posts we hold for @coraaivault. 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 — 446,470 of 1,336,469entries 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

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.

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.

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.

“Cora ai” (@coraaivault), 10,988 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/coraaivault.

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.