Channel
@Vanarchain
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,187subscribers
-8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001465240060 |
|---|---|
| Type | Channel |
| Username | @Vanarchain |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/Vanarchain |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 12:31 | 3,187 | -7 |
| 7 Aug 2026, 09:13 | 3,194 | -1 |
| 6 Aug 2026, 21:00 | 3,195 | no change |
| 6 Aug 2026, 20:49 | 3,195 | first reading |
20 posts held, back to 6 July 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 3 pagesof Telegram’s post history, 20 posts per page.
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 6 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (6 July 2026 – 6 August 2026) |
| Views total | 2,372 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:43 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.
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.
28 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 14 | 50.0% | |
| ❤ | 11 | 39.3% | |
| 👏 | 3 | 10.7% |
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 11 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 28reactions 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 July 2026 to 6 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.
The $VANRY migration portal opens Tuesday, August 11 at 1 PM UTC. Self-custody holders will be able to migrate $VANRY to Base through the official Vanar swap portal: http://swap.vanarchain.com/ The migration is 1:1, and the swap window will remain open for 30 days. Supported source chains: ►Ethereum ►Vanarchain ►Polygon Destination chain: ►Base Lock your existing $VANRY and receive new $VANRY on Base at the sam…
Signed Bertzkie
To our Vanar community, As you have probably seen, Binance is delisting VANRY on 17 August as part of its own review cycle. That's Binance's call, not a verdict on what we have built or where Vanar is heading. We've spent the last year building the stack this space needed and didn't have: agent identity, memory, governance, and commerce settlement. AI Agentic orgs are on the way with a working marketplace, and its …
Signed Dav™
The folders you build in January are a graveyard by March. myNeutron groups related saves into Bundles automatically, so your knowledge stays organized without the upkeep. Save freely, stay organized: myneutron.ai https://x.com/i/status/2083135677584023645
Signed Dav™
Vanar AMA Recap: Migration, Base, AI Organisations, Foundry, Genesis, and What Comes Next Our latest AMA came at one of the most important moments in Vanar’s history. The community has seen the new narrative, the Base migration announcement, the upcoming VANRY swap process, and the first look at Foundry and Genesis. Naturally, people had questions. What is changing? What is staying the same? Why Base? What happens t…
Signed Dav™
Vanar AMA Reminder Tomorrow Jawad and Ash will join Iffy LIVE on X to answer community questions around the VANRY migration, move to Base, token swap, supply update, staking shutdown, Foundry, AI Organisations, Genesis, and what comes next. We're collecting questions now 👇 https://x.com/Vanarchain/status/2082440971120193818
❤1
Signed Bertzkie
Vanar Live AMA this Thursday. Join Jawad and Ash, hosted by Iffy, for a full community AMA covering the VANRY migration, token swap, move to Base, new supply, staking wind-down, Foundry, AI Organisations, Genesis, and what comes next. Nothing off limits. https://x.com/i/status/2082029136575357067
Signed Dav™
VANRY migration update We are slightly delaying the VANRY migration timeline to complete final coordination with supported CEXs and stakeholders. Our priority is making sure the swap is smooth for all holders, especially users holding VANRY on centralised exchanges where migration support needs to be fully aligned before anything goes live. Token migrations also attract fake links, fake portals, impersonators, and…
Signed Dav™
VANRY migration starts on Tuesday. Before then: Unstake if you are staking. Wait for the cooldown and claim your tokens. Watch for official CEX announcements. Wait for the official portal link. Do not trust DMs or reply links. The next VANRY chapter is on Base. https://x.com/i/status/2080965457616511333
Signed Dav™
A challenge, not a pitch. Do not test myNeutron with throwaway notes. Save a few things you actually care about. Ask a real question. Come back tomorrow. If it remembers where you left off, the hardest part of working with AI is solved. Try it for real: myneutron.ai https://x.com/i/status/2080612763857027510
Signed Dav™
VANRY migration update. On Tuesday, July 28, the VANRY token swap and migration process begins. Official links will be shared only through official Vanar channels. This post explains what users should prepare before the swap goes live. https://x.com/i/status/2080579500719362381
❤1
Signed Dav™
Vanar is moving to Base. Here’s what's changing for VANRY For the last year we've watched AI move faster than almost anyone building it expected. The models keep getting better. Agents can write software, analyse data, browse the web, run complex tools, hold wallets and even pay each other. Something that looked impossible a few months ago is ordinary by now. But the more we built through that year, the more we kep…
❤1
Signed Bertzkie
INTRODUCING VANAR ORGS! The chain race is no longer the game. The next era is not about who runs the rails. It is about what can be built, launched, hired, backed, and trusted on top of them. Check the video, read the thread or visit http://onvanar.com/ to learn more! https://x.com/Vanarchain/status/2079930267557372357
🔥2❤1
Signed Bertzkie
Showing the 12 most recent of 20 posts we hold for @Vanarchain. 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 — 175,002 of 1,183,361entries 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.
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.
Named by 6 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Vanar Announcements” (@Vanarchain), 3,187 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Vanarchain.
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.