multi_evm alpha day 84 [31 July🌞] @t3rminalxyz terminal @Nibblinz_eth nft @ukiyo_rh robin @RoscaCredit arc @Divergents_eth nft @unvault nft

Channel
multi_evm
@multi_evm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
145subscribers
+0 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 | -1003921423379 |
|---|---|
| Type | Channel |
| Username | @multi_evm |
| Description | nft // evm alpha every day https://x.com/Multi_Evm |
| Created | Between 1 April 2026 and 12 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/multi_evm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 21:16 | 145 | no change |
| 7 Aug 2026, 19:36 | 145 | first reading |
Engagement
20 posts held, back to 12 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 48.1%
- avg views ÷ 145 subscribers
- Avg views / post
- 69.8
- 18 posts measured
- Reaction rate
- 2.31%
- reactions ÷ views · ER floor
- Posts in window
- 18
- 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 9 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 20 (12 July 2026 – 1 August 2026) |
| Views total | 1,256 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 21:16 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
- Photos
- 3
- Links
- 87
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
15 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 86.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 86.7% | |
| 👍 | 1 | 6.67% | |
| 💔 | 1 | 6.67% |
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 9 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 15reactions 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 12 July 2026 to 1 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.
Recent posts
multi_evm alpha day 83 [30 July🌞] @Arcadiansnft_ arc nft @GOErealm nft eth @IronAllies_ nft hype @StableS0ciety nft stable @Hoodbits_ nft @TamawagmiNFTs early nft @Arc_Critters arc nft @fuegonft nft @LPC_NFTS nft
multi_evm alpha day 82 [29 July🌞] @pupble_xyz nft @Promptal_eth nft @Choplingart nft @HoodTangs nft robin early
multi_evm alpha day 81 [28 July🌞] @Laarcfun arc @RobinhoodSlimes free mint @Kaatana_nft free mint @NeonNodeRH nft @KogekiPanda arc nft @donkennelclub robin @ChibiverseHood free @Arcionsnft arc @Freefloat404 nft @accordmaths aI @everyonchain free @OZZLAB_ og mint soon @peepsnfts nft @gobbozHQ nft @fourohfourexe arc @OnlyPerpetuals hyper @MotoCatRC free mint @TalentsWallet aztec @arcangelz_com nft arc @biwlsxyz early
❤1
multi_evm alpha day 80 [27 July🌞] @Puffpals_NFT nft eth early @BastarcsNFT arc nft @Archelon_NFT nft arc early @KludzNFT nft @thedoughies nft @decodedagents nft early @h00dle_ free mint robin
❤1
multi_evm alpha day 79 [26 July🌞] @Chomperz_nft nft @StabilioMaker stable @Beppo_eth free eth @Yepengs_ nft @Inscribeonarc arc @zorpians nft early @titanshood_ nft robin @TearLabsAI ai
❤2
multi_evm alpha day 78 [25 July🌞] @EthCoordinate eth @HoodedNFT nft @Veritylab secure @vault_hood rwa
❤2
multi_evm alpha day 77 [24 July🌞] @boundotfun arc @RobinpegV4 nft robin early @arcagefun arc market @DOZY_ETH nft eth free mint @Tidemark_io economy stable
multi_evm alpha day 76 [23 July🌞] <robinhood> @VERDANTROBOT robots @hyv3ai ai agents @BibosRH token + nft? @NeurocaineAI ai @jello_xyz early @ponsdotmine mine @tradingpitfun early @UseGlowAI ai @Robin_Forge mining @OkoProtocol protocol @DiceProtocolRH protocol @GenesiAgent deploy @robincorpp bird @printdotmeme launchpad @ROBINL4BS token @project_cpu agents @PLTRPairedFun stock @Evergreenproto evm @NoviqAIxyz networ…
👍1
multi_evm alpha day 75 [22 July🌞] @kitedotst kite @ProjectOperoAi trading @Longitudefi stocks @minepea_ mine @Monaris_co layer @RobinHeroesgame rpg @OpenMarket_fun launchpad @torvenfit deploy @TurtzWTF arc game @paygent_tech agents @arcetch arc @circleonarc arc @Rentopoly game @evmdotchatearly @RobinDex_fun desk @robinpotbet bet @Arcmonkeyxyz arc @Stonkscriptions robin @xprobinhood dex @machiagent city @OrchardDotGo…
multi_evm alpha day 74 [21 July🌞] @Looters_NFT nft hyper @robinnodes robin chain @Kiwidotrich launch on arc @malibuonbase base early @COALAFUN early @tengofinance card @CenturionRH agents @pept_trade trade @roodswap_ swap @4663trade launchpad @robinalsapp inscription @theinventorynft nft @dotarknet arc @Calculator_hood casc @NockBondRH early @rowanfinance finance @stonksfarm apy @iwoodcash etf @Vellichor_hood rwa @G…
❤2
multi_evm alpha day 73 [20 July🌞] @TidewaterRH robin @GranaryFarmsRH robin @SazareProtocol robin uniswap v4 @HoodpumpApp robin launchpad @useskalo agents @motionsdoto uniswap @VesperHood robin @MakiDotFinance by sushi swap @StonkSweep sweep @BrokrdotBot bot @SharcFun launch @opalrhfun robin @TheArchfun arc @Buildog9 arc @Clavisrobinhood robin @Ledgerstocks robin @rwogcoin token @Egoreai core @arclayer_ arc early @Pe…
❤4
Showing the 12 most recent of 20 posts we hold for @multi_evm. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@CatBatHatFatRat · 71 postFuego Announcements
@FuegoNFT · 1811 postGreenPad
@greenpad_xyz · 111 postHood Launcher
@hoodlauncherfun · 131 postHyper Hood Pro
@Hyperhoodtrade · 91 postLATTICE PORTAL
@latticeonhood · 91 postLaunchhood
@launchhood · 1591 postLemon.fun
@lemondotfun · 4711 postLongitude
@longitudefi · 611 postMEMESTONK | PORTAL
@memestonkio · 601 postNibor - Enter the forest (Portal)
@niborthefrog · 431 postNoxa
@NoxaDotFi · 1,4641 postOqto.fun
@oqtofun · 691 postOrchard
@OrchardDotGold · 891 postPonziCity - Portal
@PonziCity · 271 postRecurve.fi Updates
@recurvefi · 331 postScherwode (Portal)
@scherwode · 151 postSea Of Robin
@seaofrobin · 141 postSettleMarket
@SettleMarket · 81 postThruster: Announcements
@thrusterfi · 3,2011 post
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
- 300
- 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
- 300
- vacant every time we have ever looked
@multi_evm named 300 handles 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 2 posts, 9 August 2026 – 9 August 2026
named in 2 posts, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
250 more handles are in this same list but not shown individually here — capped at 50.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“multi_evm” (@multi_evm), 145 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/multi_evm.
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.