8 measurements spanning 7 days, net -335. 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 32,954–33,389 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 21:15
33,004
-59
11 Aug 2026, 18:18
33,063
-84
10 Aug 2026, 15:06
33,147
-58
9 Aug 2026, 11:51
33,205
-45
8 Aug 2026, 09:51
33,250
-36
7 Aug 2026, 07:08
33,286
-53
6 Aug 2026, 01:51
33,339
no change
5 Aug 2026, 22:01
33,339
first reading
Engagement
21 posts held, back to 18 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
2.18%
avg views ÷ 33,004 subscribers
Avg views / post
719
2 posts measured
Reaction rate
5.29%
reactions ÷ views · ER floor
Posts in window
2
of 21 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
Window
Rolling 30 days · latest post in window 10 August 2026
Posts held
21 (18 November 2024 – 10 August 2026)
Views total
1,438
Reactions total
76
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 21:09 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.
Reaction mix
2,079 reactions across 21 posts, in 11 distinct kinds. The most used accounts for 36.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
765
36.8%
❤
644
31.0%
🔥
494
23.8%
😁
67
3.22%
😐
25
1.20%
❤🔥
23
1.11%
🎉
14
0.673%
🥰
14
0.673%
🤔
13
0.625%
👎
11
0.529%
👏
9
0.433%
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 21 of the 21 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 2,079reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 18 November 2024 to 10 August 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.
Telegram Stars
Stars received
42
across the posts below
Posts paid on
5
of 21 we hold a reading for · 24%
Most on one post
25
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @JVault. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 21 most recent posts we hold for this entry, published 18 November 2024 to 10 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🌐 A reminder about the referral program
In JVault, any user can create a referral wallet and earn from 0.5% of the rewards of every staker they invite. The referral program is available both on the website and in the SDK.
⚙ Key details:
⭐ The referral is recorded on-chain with the first deposit and stays bound to the user forever.
🌟 Your rewards are calculated as a percentage of what your referral earns across all …
⭐ JVault — Current Status
It's no secret that since mid-2024, DeFi on TON has been in decline — projects are shutting down one after another, and the remaining users have less and less faith in a bright future.
🖤 Nevertheless, JVault continues its work.
☑ Over the past few months, JVault has been completely overhauled: the interface has been brought up to modern standards, becoming much more responsive and intuiti…
🔥 $EVAA Staking on the JVault Platform
Last week marked a major event in the TON ecosystem — EVAA protocol held the TGE for the $EVAA token, with its market cap peaking at nearly $50 million. Alongside listings on major exchanges, the project launched staking on our platform.
⚙ Условия стейкинга:
⭐️ Initial reward pool: 10,000 $EVAA
🌟 Unstaking period: 7 days
⭐️ Instant withdrawal fee: 10%
🌟 The reward pool will b…
🔤 Have You Seen It Too? 🔤
👆 I’ve watched this movie dozens of times… but only now did I notice those strange symbols. Were they always there? Or is someone trying to send a message?
😠 Could this be connected to the new mission in WEB3 Portal? Maybe only the most observant will uncover the hidden message…
🤫 If you’ve spotted something too, try entering the secret word
A special reward awaits those who can see beyo…
⚡ Imagine a world where crypto domains become a valuable asset.
💰 A year of hard work, $150,000+ budget and the first ever .ton-domain marketplace is already a reality!
Are you ready to change the rules of the game?
WEB3 x JVault: the largest token lockup in the project's history
WEB3 is not just a member of the ecosystem, but one of its pillars. The famous project team is taking the important step of locking 90% of the total $WEB3 offering via JVault Locker with vesting for 5 years.
⚙ Locking parameters:
🌟 Amount: $73,000,000 $WEB3
⭐ Term: 5 years (until March 2030)
🪙 Token distribution:
🌟 Liquidity and listings — web3token.…
🔥 Update in dAssets: support for JVault staking pools
🚀 The dAssets project has added our staking pools to @dAssets_bot so that every user can easily track their positions across all tokens.
dAssets is a portfolio tracker from the dTON team that supports almost every possible asset on the TON blockchain, including liquid staking tokens, rewards from farming on DEX, positions in EVAA and more.
❤ We're excited to se…
🔥 Thousands of JVT are burning to light up the future of JVault
Friends, today we are launching the largest token burn in the history of the project: 777,000 $JVT have already been received by burn-jvault.ton, of which 10,000 have been bought back with funds earned from platform commissions. This is an important step to reduce emission and increase the value of $JVT.
☑ To mark the event, we are launching an unusual…
🔥 A new chapter in the development of JVault quest bot — time for tasks!
Starting today, every user can accumulate XP when the bot temporarily has no active campaigns.
⚙ What's new?
Right in @JVaultBot there are daily tasks waiting for you that can be performed at any time. Among them:
⭐ Channel subscriptions
🌟 Use of partner bots
⭐ Extra XP for staking positions
🌟 And many others!
This update is a logical contin…
🔥 Meet the staking pool from the Liquid project on the JVault platform
$LIQUID is a meme token that becomes the heart of its community. The project is built on transparency, trust and the participation of each user. It is inspired by Storm Trade СMO — Vladimir Kovalevsky.
⚙ Staking Conditions:
⭐ Initial award pool: 500 TON
🌟 Unstaking period: 30 days
⭐ Instant Withdrawal Fee: 7%
🌟 Deposit fee: 1%
💰 Stake $LIQUID t…
🔥 Launch of the referral system on JVault — earn together!
The moment has come when we are happy to introduce a brand new feature on our platform — a referral system. Now every user can not only participate in staking, but also invite friends to the JVault ecosystem.
⚙ How does it work?
⭐ Referral system is available right on our website
🌟 Each user can mint and manage a Referral Wallet
⭐ Depending on the level, y…
🔥 New BOLT campaign: uniting the community for success in 2025
The coming year presents us with great opportunities, and together we can make the ecosystem even stronger. That's why JVault is partnering with the BOLT Foundation to launch a campaign with unique rewards.
☑ Send $BOLT to the boltfoundation.ton and receive exclusive rewards by passing certain milestones:
⭐ 100+ BOLT — SBT ‘Wooden Supporter 2025’
🌟 1,0…
👍27❤20🔥12👎5
Showing the 12 most recent of 21 posts we hold for @JVault. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 203,151 of 1,151,006entries 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 10 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.
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
@JVault 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.
@jvault_chat named in 55 posts, 8 August 2026 – 12 August 2026
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.
Ton Raffles En Channel @tonraffles_en · 1,338,925 Telegram ranks this channel #49 of 87 here — alongside 86 others — read 11 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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“JVault” (@JVault), 33,004 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/JVault.
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.