Telegram RegisterThe public register of Telegram
Telegram profile photo for Waves 🌊

Channel

Waves 🌊

@wavesnews

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry

943,891subscribers

-224,741 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001050702615
TypeChannel
Username@wavesnews
DescriptionThe L1 for real builders: Fast. DAO-powered. Made for dApps, DeFi & RWA Making Waves in Web3 since 2016 🌊 Website: https://waves.tech/
Created15 July 2016 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/wavesnews

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 58% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 11 other registered channels. This entry also sits inside a group of 18 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@unitsnews/39327 Oct 2025, 13:10 UTC@wavesnews/4333 · this entry27 Oct 2025, 13:26 UTC1.0016 minutes
@KeeperWallet/953 Aug 2023, 13:44 UTC@wavesnews/3175 · this entry3 Aug 2023, 14:01 UTC1.0017 minutes
@KeeperWallet/1008 Aug 2023, 12:25 UTC@wavesnews/3183 · this entry8 Aug 2023, 12:26 UTC1.00under a minute
@KeeperWallet/10310 Aug 2023, 13:43 UTC@wavesnews/3188 · this entry10 Aug 2023, 13:58 UTC1.0014 minutes
@KeeperWallet/10410 Aug 2023, 15:31 UTC@wavesnews/3190 · this entry10 Aug 2023, 15:54 UTC1.0023 minutes
@KeeperWallet/10824 Aug 2023, 13:32 UTC@wavesnews/3208 · this entry24 Aug 2023, 13:33 UTC1.0072 seconds
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@unitsnews235 (8/8 hand-verifiable sample passed)1.002 minutes@unitsnews (198–37)
@KeeperWallet10 (8/8 hand-verifiable sample passed)1.005 minutes@KeeperWallet (10–0)
@east_finance10 (8/8 hand-verifiable sample passed)1.0022 minutes@east_finance (10–0)
@neutrino_protocol_news9 (8/8 hand-verifiable sample passed)1.0010 minutes@neutrino_protocol_news (9–0)
@TurkiyeDAO8 (8/8 hand-verifiable sample passed)1.00under a minute@TurkiyeDAO (7–1)
@unilendnews12 (8/8 hand-verifiable sample passed)1.0020 minutes@unilendnews (8–4)
@petetokennews10 (8/8 hand-verifiable sample passed)1.0010 minutes@petetokennews (8–2)
@wavesfunnynodenews7 (7/7 hand-verifiable sample passed)1.0022 minutes@wavesfunnynodenews (7–0)
@tsunami_exchange8 (8/8 hand-verifiable sample passed)1.0013 minutes@tsunami_exchange (7–1)
@wavesenterprise7 (7/7 hand-verifiable sample passed)1.0020 minutes@wavesenterprise (6–1)
@binance_announcements7 (7/7 hand-verifiable sample passed)1.0026 minutes@binance_announcements (7–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 146 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 3,363 comparable posts for this entry, running 8 August 2016 to 9 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 18 channels, the one whose matching posts we hold earliest is @WavesDomainsNews. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 18 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

1 more channel is in this same group but not listed individually here.

Growth

943,8911,168,6321,056,261.56 August 202610 November 2026
64 measurements spanning 96 days, net -224,741. 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 910,180–1,202,343 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 10:05943,891-2,922
8 Nov 2026, 21:58946,813-2,379
7 Nov 2026, 17:47949,192-2,031
6 Nov 2026, 14:25951,223-2,522
5 Nov 2026, 14:35953,745-2,220
4 Nov 2026, 11:06955,965-2,178
3 Nov 2026, 10:59958,143-2,081
2 Nov 2026, 08:47960,224-1,802
1 Nov 2026, 11:16962,026-2,465
31 Oct 2026, 10:10964,491-3,186
30 Oct 2026, 11:10967,677-1,531
29 Oct 2026, 13:55969,208-2,647
28 Oct 2026, 10:31971,855-1,398
27 Oct 2026, 12:46973,253-3,065
26 Oct 2026, 12:48976,318-1,104
25 Oct 2026, 14:00977,422-1,118
24 Oct 2026, 16:20978,540-2,348
23 Oct 2026, 18:07980,888-2,207
22 Oct 2026, 16:07983,095-3,242
21 Oct 2026, 07:16986,337first reading

Engagement

4,312 posts held, back to 15 July 2016 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 426 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.098%
avg views ÷ 943,891 subscribers
Avg views / post
921
18 posts measured
Reaction rate
0.917%
reactions ÷ views · ER floor
Posts in window
24
of 4,312 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 17 of 18 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 9 November 2026
Posts held4,312 (15 July 2016 – 9 November 2026)
Views total16,581
Reactions total147
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 01:32 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
≈1,830
Videos
≈96
Links
≈3,450

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 05s
Average length
33s

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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 11 of this channel’s own posts over the last 30 days: across 10 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2 days of being posted; a typical post has already reached 30.8% of its 24-hour view count within the first hour, and 63.8% within the first six; the median 24-hour reach across those posts is 234 views — 0.022% of this channel’s own subscriber count (90th percentile 436).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/45741 Oct 2026, 11:21 UTC1839 minutes – 18 hours old189 views13 reactions60 minutes: 70 interp. → 3.0 hours: 107 → 6.0 hours: 143 → 12 hours: 178still climbing at last readingnot yet at 24h2.3 hoursprovisional — final view count still climbing
/457328 Sept 2026, 11:02 UTC8149 minutes – 4 days old413 views8 reactions60 minutes: 61 interp. → 3.0 hours: 99 → 6.0 hours: 129 → 12 hours: 163 → 24 hours: 206 → 2 days: 253still climbing at last reading206measured24 hours
/456615 Sept 2026, 14:58 UTC937 minutes – 9 days old681 views8 reactions60 minutes: 71 interp. → 3.0 hours: 99 → 6.0 hours: 129 → 12 hours: 140 → 24 hours: 191 → 2 days: 240 → 7 days: 569still climbing at last reading191measured5 days
/456515 Sept 2026, 14:28 UTC11036 minutes – 9 days old855 views9 reactions60 minutes: 99 interp. → 3.0 hours: 158 interp. → 6.0 hours: 200 → 12 hours: 224 → 24 hours: 300 → 2 days: 359 → 7 days: 744still climbing at last reading300measured3 days
/456410 Sept 2026, 15:32 UTC1444 minutes – 7 days old581 views10 reactions60 minutes: 63 interp. → 3.0 hours: 106 → 6.0 hours: 130 interp. → 12 hours: 150 → 24 hours: 200 → 2 days: 261 → 7 days: 581still climbing at last reading200measured3 days
/456210 Sept 2026, 13:33 UTC15229 minutes – 7 days old792 views6 reactions60 minutes: 134 → 3.0 hours: 220 → 6.0 hours: 277 → 12 hours: 320 → 24 hours: 383 → 2 days: 462 → 7 days: 792still climbing at last reading383measured27 hours
/45618 Sept 2026, 11:55 UTC13421 minutes – 7 days old471 views7 reactions60 minutes: 63 interp. → 3.0 hours: 99 → 6.0 hours: 127 → 12 hours: 154 → 24 hours: 185 → 2 days: 236 → 7 days: 471still climbing at last reading185measured48 hours
/45607 Sept 2026, 12:12 UTC13519 minutes – 7 days old525 views7 reactions60 minutes: 65 interp. → 3.0 hours: 106 → 6.0 hours: 141 → 12 hours: 178 → 24 hours: 239 → 2 days: 310 → 7 days: 525still climbing at last reading239measured27 hours

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

548 reactions across 59 posts, in 13 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤23743.2%
🔥13524.6%
👍6612.0%
👌539.67%
👏132.37%
🤔112.01%
👀101.82%
🙏61.09%
🐳50.912%
🎉40.73%
🏆40.73%
⚡30.547%
🥰10.182%

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 922 of the 1,000 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 25,286 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 22 February 2024 to 9 November 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

Telegram’s own ‘edited’ marker: 1 of 24 posts held from the last 30 days (4.17%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 13:37 UTC520 views10 reactionsread 11 November 2026

🔄 Incident summary: why the network was rolled back On 9 November, third parties produced blocks on the Waves network with abnormally inflated fees. As a result, several addresses were credited with WAVES that never actually existed. What we did ✅ Rolled the network back to block 5,481,020 (8 Nov 23:55 UTC). The WAVES that never existed are gone. ✅ The network now runs on a new chain from block 5,481,021. ✅ Release…

🤔5👌3👏2

9 Nov 2026, 09:48 UTC546 viewsread 11 November 2026
Photo

🔄 Mandatory network update (v1.6.5) For security reasons, all Waves node operators need to move to the latest version ⚠️ Please follow the release notes 👉 https://github.com/wavesplatform/Waves/releases/tag/v1.6.5

6 Nov 2026, 19:21 UTC468 views3 reactionsread 11 November 2026
Forwarded from @pix11newsVideo

⚽️ Two mints. Two new signings. See how to mint your first football player NFT on PIX11, from connecting your wallet to the reveal, in our 60-second walkthrough. Your turn. Who will you get? 👀 👉 https://pix11.club/mint

🔥3

3 Nov 2026, 11:57 UTC≈1,120 views5 reactionsread 11 November 2026
Photo

⚠️ Important WavesBridge Announcement WavesBridge is closing. All withdrawals will be discontinued after November 30. ⏳ Withdrawals will remain available until November 30 across all supported blockchains and tokens. Please make sure to withdraw your assets before the deadline here 👉 https://wavesbridge.io/bridge

❤2👌2👍1

2 Nov 2026, 12:03 UTC595 views4 reactionsread 11 November 2026
Forwarded from @pix11newsPhoto

⚽️ Who’s your dream PIX11 player? We’re giving away 50 $WAVES in our contest on X! Tell us which footballer you’d love to receive in a PIX11 mint for a chance to win. To enter: 🔢 Reply to the contest post with your pick. 🔢 Follow PIX11 on X. 🔢 Repost the contest post & Tag 3 friends. 🎁 One winner will be selected at random from participants who complete all three steps. ⏳ Entries close: November 9, 12:00 UTC …

🔥3👀1

2 Nov 2026, 11:12 UTC813 views9 reactionsread 11 November 2026
Photo

Halfway to 3M! 🌊 Every new stake brings the 50,000 $WAVES bonus closer 🚀 Who’s in: new and old stakers Rule for all: hold 3+ weeks ⌛️ Why the Core Team Node: ✅ 100% of staking income ✅ Extra PWR tokens ✅ Extra UNIT0 tokens Still on the shore? There’s room for you in this wave 🏄 📍 Node Address: 3PPfYtEw8dSNdmw2pV18BySmTZrTEaMNQDE Join the new wave 👈

❤6👍2👌1

2 Nov 2026, 08:25 UTC433 views8 reactionsread 11 November 2026
Forwarded from @predictorium_ioPhoto

🚀 Predictorium is now on Zealy! We’re launching a new quest for new Predictorium users 🆕 How it works: 1️⃣ Join the Predictorium quest on Zealy 2️⃣ Trade on Predictorium until your total volume reaches at least $20 3️⃣ Get your $USDC reward 💡 Total volume means the combined amount of all your trades. It doesn’t matter whether you win or lose. Join the quest 👈

❤5👍2🔥1

28 Oct 2026, 13:21 UTC647 views12 reactionsread 11 November 2026
Forwarded from @pix11newsPhoto

🥾Introducing PIX11 — fantasy football meets DeFi. Collect player NFTs linked to real-world footballers and put your football knowledge to work. Play with individual players or build squads of 5 or 11. Their performances on the pitch determine player scores and their share of weekly rewards, with scoring bonuses for complete teams. 🚀 It starts with the mint, planned for the first week of November. Team building and…

❤6👍3🔥2🏆1

27 Oct 2026, 12:19 UTC≈1,350 views11 reactionsread 11 November 2026
Photo

Wave two is here, and here comes another bonus for $WAVES stakers! 💰 Our new goal: 3M WAVES staked on the Waves Core Team Node 🚀 Who takes part: ✅New stakers ✅Everyone already on the node, old stakes included ✅Wave one winners: keep your WAVES on the node for 3 more weeks and you’re in again 💙 The one rule for all participants: ⌛️ Hold for at least 3 weeks 📍 Node Address: 3PPfYtEw8dSNdmw2pV18BySmTZrTEaMNQDE Join…

🔥6❤5

Showing the 12 most recent of 4,312 posts we hold for @wavesnews. 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.

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 22 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

WX Network Announcements
@wx_network · 3,420
#1
Waves (Ru) 🌊
@WavesNewsRU · 3,048
#2
Arkimals Announcements
@wavesducksrounds · 4,563
#3
Units.Network Announcements
@unitsnews · 658,491
#4
DEGO Official Announcement
@DEGO_Announcement · 13,810
#5
The Bull
@thebull_crypto · 170,635
#6
CoinMarketCap Announcements
@CoinMarketCapAnnouncements · 235,121
#7
Lumia News
@lumia_news · 98,320
#8
Curve Finance
@curvefiann · 1,519
#9
Stalwart AI
@stalwartai · 1,608
#10
Crypto Ambassador Programs
@CryptoAmbassadorPrograms · 805 (as read 15 August 2026)
#11
DeXe Protocol - Announcements
@Dexe_network · 7,049
#12
Drop - Announcements
@DropAnnouncements · 564
#13
TapDaDoge ANN
@TapDDoge_ANN · 1,763
#14
Crypto Waves
@BinanceWaves · 20,803
#15
TONPools Community
@tonpools_com · 1,169
#16
Bit Official Updates
@Bit01updates · 742
#17
ArkeFi Announcements
@Arkefi_Announcement · 542
#18
Biswap Announcements
@biswap_news · 23,541
#19
WX Network Новостной Канал
@wxnetworknews · 1,147
#20
Watcher Guru
@WatcherGuru · 632,289
#21
ForkLog
@forklog · 101,391
#22
DeCenter — блокчейн, биткоин, инвестиции
@DeCenter · 1,640,924
#23
Cointelegraph
@cointelegraph · 325,603
#24
Marlin Protocol Announcements
@MarlinProtocolAnn · 1,401
#25
AscendEX Official Announcement
@AscendEXAnnoucement · 1,892
#26
QuickSwap Announcements Channel
@QuickSwapAnnouncements · 14,086
#27
DEFI Scam Check
@Defiscamcheck · 48,110
#28
unfolded.
@unfolded · 116,604
#29
Tezos Announcements
@TezosAnnouncements · 2,598
#30
📰 Ardor, Ignis, Nxt Community News 🚀
@nxt_ardor_ignis_news · 598
#31
IOST Official Announcements
@iost_announcements · 2,012
#32
Whale Sniper
@WhaleSniper · 59,201
#33
Viction Announcement
@buildonviction · 3,928
#34
Cardano Announcements
@CardanoAnnouncements · 35,015
#35
Альтхимия
@altchemistry · 830
#36
OVER Announcements
@ovrannouncements · 2,408
#37
Crypto news
@bingoblockchainar · 1,863
#38
PancakeSwap Announcements
@PancakeSwapAnn · 28,214
#39
Neo News Today
@neonewstoday · 496
#40
Satoshiat Chart
@SatoshiatChart · 2,953
#41
Astar Collective Announcements
@PlasmAnnouncement · 2,625
#42
Airdrop Portal🔆
@Airdrop_P0rtal · 1,334
#43
Bifrost Announcement
@bifrost_announcements · 1,084
#44
Decentr Announcements
@DecentrAnnouncements · 411
#45
Cappasity Updates
@cappasityupdates · 3
#46
Thravos Announcement
@thravosannouncement · 135
#47
BrightFunded
@brightfunded · 1,339
#48
Crypto Horizon | أفق الكريبتو
@CryptoHorizon · 2,520
#49
DeFi Land Announcements
@DeFiLand_announcements · 1,282
#50
Terra Governance Alerts
@terra_agora · 485
#51
Terra - Announcements
@terra_announcements · 3,804
#52
Router Announcements
@router_ann · 935
#53
Whales Crypto Guide
@Whalesguide · 183,177
#54
CoinGecko News
@coingeckonews · 9,878
#55
Seedify.fund Announcements
@seedifyfund · 78,107
#56
Web3 Security News
@web3secnews · 2,367
#57
Quest Alert 🧪
@QuestAlert · 65,099
#58
Bitcoin.com News
@www_Bitcoin_com · 51,436
#59
CryptoDiffer News
@cryptodiffer · 22,680
#60
Circular Protocol Announcements
@CircularWeb3 · 913
#61
Jack Dorsey Coins 🚀
@JackDorseyCoins · 21,691
#62
Injective Announcements
@injectiveann · 13,564
#63
Landshare Announcements
@LandshareAnnouncement · 1,687
#64
JLaunchpad
@JLaunchPad · 14,061
#65
Coindar
@coindar · 10,870
#66
CriptoNoticias
@criptonoticias · 39,590
#67
DYOR Announcements
@DyorAnnouncements · 972
#68
Bitfinex Announcements
@bfxannouncements · 1,480 (as read 15 August 2026)
#69
Decrypt
@DecryptNews · 15,570
#70
ForkLog FEED
@forklogfeed · 15,981
#71
CryptoQuant
@cryptoquant_official · 55,481
#72
Раунды и анонсы Arkimals
@wavesducksrounds_ru · 2,280
#73
Web3 Tech: новости
@web3technews · 764
#74
Bitcoin Treasuries
@BTCTreasuries · 1,135
#75
Hype Coin News
@hypecoinnews · 1,820
#76
No plan “A”
@avsha1umov · 387
#77
🔥🇩🇿 Binance wolves 🇩🇿🔥
@analyse_office · 660
#78
Jabaroot Dz 👑
@Jabaroottt · 7,425 (as read 15 August 2026)
#79
Xertra Announcements
@StratisAnnouncements · 296
#80
أفق الكريبتو للوساطة المالية 💵
@CryptoHorizon_Swap · 2,174
#81
Все о блокчейн/мозге/space/WEB 3.0 в России и мире
@blockchainRF · 20,457
#82
Official MEVerse Announcement Channel
@MEVerse_Announcement · 764
#83
ASI Announcements - Artificial SuperIntelligence Alliance
@ASI_announcements · 4,214
#84
Alpaca Finance - Announcements
@alpacafinanceannouncements · 5 (as read 15 August 2026)
#85
El Impulso
@elimpulso · 5,612
#86
Motor News
@CyR_MotorNews · 3,413
#87
PESAN SEMESTA ACADEMY
@PesanSemestaAcademy · 1,779
#88

Read from Telegram’s recommendation API, most recently 15 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Units.Network Announcements
@unitsnews · 658,491
Telegram ranks this channel #2 of 85 here — alongside 84 others — read 15 August 2026
Lumia News
@lumia_news · 98,320
Telegram ranks this channel #8 of 87 here — alongside 86 others — read 15 August 2026
Cardano Announcements
@CardanoAnnouncements · 35,015
Telegram ranks this channel #60 of 85 here — alongside 84 others — read 1 September 2026

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

Domains linked from posts

67 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

x.com59 posts · 12 August 2025 – 14 July 2026 · example post
unilend.io37 posts · 28 August 2025 – 30 January 2026 · example post
fun.units.networkregistrable domain: units.network31 posts · 15 August 2025 – 11 December 2025 · example post
wavesonchain.com30 posts · 12 August 2025 – 17 July 2026 · example post
zealy.io24 posts · 19 August 2025 – 9 May 2026 · example post
koalaswap.app18 posts · 1 October 2025 – 29 December 2025 · example post
medium.com17 posts · 12 August 2025 – 17 July 2026 · example post
app.waves.futbolregistrable domain: waves.futbol11 posts · 31 May 2026 – 1 July 2026 · example post
dao.unit0.devregistrable domain: unit0.dev10 posts · 15 August 2025 – 29 December 2025 · example post
xyper.market10 posts · 26 May 2026 – 31 July 2026 · example post
score.units.networkregistrable domain: units.network8 posts · 31 March 2026 – 15 April 2026 · example post
app.wavesfunnynode.comregistrable domain: wavesfunnynode.com8 posts · 20 April 2026 – 10 June 2026 · example post
blog.waves.techregistrable domain: waves.tech7 posts · 27 August 2025 – 25 May 2026 · example post
predictorium.io6 posts · 22 May 2026 – 7 July 2026 · example post
app.power.techregistrable domain: power.tech5 posts · 11 August 2025 – 10 July 2026 · example post
wx.network5 posts · 2 September 2025 – 10 December 2025 · example post
open.spotify.comregistrable domain: spotify.com4 posts · 19 December 2025 – 26 January 2026 · example post
swop.fi4 posts · 19 September 2025 – 14 December 2025 · example post
docs.units.networkregistrable domain: units.network4 posts · 23 March 2026 – 31 March 2026 · example post
ape.bond3 posts · 5 May 2026 – 28 May 2026 · example post
wallet.auraproject.netregistrable domain: auraproject.net3 posts · 2 December 2025 – 20 March 2026 · example post
bit.ly3 posts · 19 September 2025 – 4 March 2026 · example post
www.coingecko.comregistrable domain: coingecko.com3 posts · 5 November 2025 – 29 December 2025 · example post
github.com3 posts · 30 November 2025 – 16 June 2026 · example post
metealibaskaya.medium.comregistrable domain: medium.com3 posts · 15 August 2025 – 26 October 2025 · example post
swap.puzzle.networkregistrable domain: puzzle.network3 posts · 20 November 2025 – 16 December 2025 · example post
help.wavesfunnynode.comregistrable domain: wavesfunnynode.com3 posts · 20 April 2026 – 6 May 2026 · example post
www.weex.comregistrable domain: weex.com3 posts · 7 September 2025 – 9 September 2025 · example post
www.youtube.comregistrable domain: youtube.com3 posts · 19 December 2025 – 22 December 2025 · example post
www.ape.bondregistrable domain: ape.bond2 posts · 7 April 2026 – 10 April 2026 · example post
arkimals-game.com2 posts · 9 October 2025 – 26 January 2026 · example post
cards.auraproject.netregistrable domain: auraproject.net2 posts · 20 March 2026 – 23 March 2026 · example post
brevis.network2 posts · 27 October 2025 – 31 October 2025 · example post
docs.google.comregistrable domain: google.com2 posts · 15 September 2025 – 26 December 2025 · example post
pete.so2 posts · 2 December 2025 – 6 August 2026 · example post
raydium.io2 posts · 12 August 2025 – 15 August 2025 · example post
snapshot.box2 posts · 26 October 2025 – 12 November 2025 · example post
umerge.gitbook.io2 posts · 26 November 2025 – 30 November 2025 · example post
umerge.org2 posts · 26 November 2025 – 29 December 2025 · example post
safe.units.networkregistrable domain: units.network2 posts · 29 September 2025 – 3 October 2025 · example post
wavesducks.com2 posts · 2 December 2025 – 19 December 2025 · example post
pete.auraproject.netregistrable domain: auraproject.net1 post · 2 September 2025 – 2 September 2025 · example post
www.biconomy.comregistrable domain: biconomy.com1 post · 27 November 2025 – 27 November 2025 · example post
incentra.brevis.networkregistrable domain: brevis.network1 post · 29 October 2025 – 29 October 2025 · example post
www.diadata.orgregistrable domain: diadata.org1 post · 9 October 2025 – 9 October 2025 · example post
discord.com1 post · 1 February 2026 – 1 February 2026 · example post
discord.gg1 post · 26 November 2025 – 26 November 2025 · example post
eniac.network1 post · 23 April 2026 – 23 April 2026 · example post
drive.google.comregistrable domain: google.com1 post · 31 March 2026 – 31 March 2026 · example post
blockai.medium.comregistrable domain: medium.com1 post · 27 November 2025 – 27 November 2025 · example post
paragraph.com1 post · 6 December 2025 – 6 December 2025 · example post
prom.io1 post · 1 May 2026 – 1 May 2026 · example post
pundix.com1 post · 13 May 2026 – 13 May 2026 · example post
substack.com1 post · 6 March 2026 – 6 March 2026 · example post
sasha35625.substack.comregistrable domain: substack.com1 post · 7 April 2026 – 7 April 2026 · example post
app.uniswap.orgregistrable domain: uniswap.org1 post · 6 December 2025 – 6 December 2025 · example post
www.units.networkregistrable domain: units.network1 post · 19 June 2026 – 19 June 2026 · example post
units.network1 post · 1 February 2026 – 1 February 2026 · example post
waves.futbol1 post · 28 May 2026 – 28 May 2026 · example post
waves.tech1 post · 20 August 2025 – 20 August 2025 · example post
wavesbridge.io1 post · 14 December 2025 – 14 December 2025 · example post
wavesexplorer.com1 post · 1 December 2025 – 1 December 2025 · example post
wavesfunnynode.com1 post · 24 June 2026 – 24 June 2026 · example post
monitor.wavesonchain.comregistrable domain: wavesonchain.com1 post · 15 February 2026 – 15 February 2026 · example post
app.wowmax.exchangeregistrable domain: wowmax.exchange1 post · 6 October 2025 – 6 October 2025 · example post
wowmax.exchange1 post · 6 October 2025 – 6 October 2025 · example post
youtube.com1 post · 22 December 2025 – 22 December 2025 · example post

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

“Waves 🌊” (@wavesnews), 943,891 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/wavesnews.

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.