Telegram RegisterThe public register of Telegram
Telegram profile photo for WavesOnChain News

Channel

WavesOnChain News

@wocnews

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

154subscribers

+5 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001529662113
TypeChannel
Username@wocnews
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/wocnews

Growth

149154151.56 August 2026 — 149 subscribers6 August 2026 — 150 subscribers8 August 2026 — 150 subscribers13 August 2026 — 152 subscribers27 August 2026 — 153 subscribers11 September 2026 — 154 subscribers6 August 202611 September 2026
6 measurements spanning 36 days, net +5. 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 148–155 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 12:15154+1
27 Aug 2026, 02:05153+1
13 Aug 2026, 11:25152+2
8 Aug 2026, 19:47150no change
6 Aug 2026, 17:10150+1
6 Aug 2026, 00:43149first reading

Engagement

20 posts held, back to 23 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
8s
Average length
8s

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

13 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
646.2%
👌430.8%
👍323.1%

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 4 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 13 reactions 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 23 July 2026 to 7 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

7 Aug 2026, 18:43 UTC36 viewsread 8 August 2026
Photo

⏳ Oh look, it’s that time again... Want another quiz next Friday (August 14), or are 20 clicks collectively too exhausting for you guys? 🙄 Once again, your fate is in your own hands. ❤️ 20 Likes • 🔁 20 Reposts https://x.com/WavesOnChains/status/2085770353826005479 👍🏻 If you actually manage to hit this massive milestone, there will be a quiz on August 14. 👎🏻 If not... cool. We could all use a break. We’ll just ta

7 Aug 2026, 17:34 UTC166 viewsread 8 August 2026
Photo

🌊 Wallet Flow — Update is live! Wallet Flow is now faster, clearer, and more reliable for on-chain analysis. 🏷️ Known CEX and dApp addresses are now displayed with their names and logos. 🔁 FLOW INTERNAL isolates transfers between selected main addresses. ⚡ Incremental data loading improves performance, especially for multi-address analysis. 🎯 Transfer lines are now easier to select on crowded graphs. 🔎 Address

7 Aug 2026, 14:12 UTC128 viewsread 8 August 2026
Photo

🐌 THE QUIZ IS BACK! You hit 20 Likes + 20 Reposts, so we're officially bringing the chaos back TONIGHT. 🏎💨 But remember: 🧠 Knowing the answer = smart. ⚡️ Knowing it first = dangerous. 🏆 Knowing it first and clicking fast enough = leaderboard material. There will be questions. There will be captchas. There will be milliseconds. And somewhere out there, someone will lose a podium spot because they spent 0.3 seconds

7 Aug 2026, 14:01 UTC44 viewsread 8 August 2026
Photo

🏎 Get in the starting grid. Join WavesOnChain before the quiz begins...

31 Jul 2026, 19:01 UTC109 viewsread 8 August 2026
Photo

⏳ One quick reminder... Want another quiz next Friday (August 7)? 👀 It's entirely up to the community. ❤️ 20 Likes • 🔁 20 Reposts https://x.com/WavesOnChains/status/2078056609092174160 👍🏻 If the target is reached, there will be another quiz on August 7. 👎🏻 If not... enjoy today's one, because the next quiz won't be until August 14. 😏 We'll let the numbers decide. 📊 * The community has until Wednesday night (Au

31 Jul 2026, 16:07 UTC80 views2 reactionsread 8 August 2026
Video

🌊 Waves Pulse — Weekly Update Your weekly ecosystem check-in 👇 📈 Transactions: weekly volume hit a new record — 53,145 (+7.53%) week-over-week 🖥 Node Network: node count grew by +3 — another milestone that lines up with the Prediction Pools rollout 👤 Active Users: Unique Sender Addresses peaked at 483 — the highest in a month 🔥 🗳 DAO Governance: the WavesLong Dev Funding proposal reached quorum with 100% Yes Momen

1👌1

30 Jul 2026, 20:14 UTC75 viewsread 8 August 2026
Photo

🚫 These users are 👎🏻 DISQualified from all quizzes...

30 Jul 2026, 13:53 UTC64 views2 reactionsread 8 August 2026
Photo

🔮 PREDICTION TIME Last round recap: Unit0 staking rise 📈 — it happened, even if modest. 3 of you called it right 👏 The next round. Pick the one that happens first 👇 1️⃣ Active Unique Addresses hits a new weekly high 2️⃣ PWR Stakers List grows by 5% 3️⃣ Unit0 staking rises again 4️⃣ Puzzle average APR moves 2%+ Vote, then come back and tell us why you're right (or weren't) 👇 🔗 wavesonchain.com/dashboard/on-chain/w

1👌1

29 Jul 2026, 06:03 UTC320 viewsread 8 August 2026
Photo

🎮 Quiz Mode: Fastest (Score ➔ Time) 👑 Server Owner: Father Time 🧠 Quiz Master: Knowledge ⏱️ Head Referee: Milliseconds ⚖️ Appeals Department: Permanently Closed Knowing the answer is impressive. Proving it before everyone else is profitable. Reason: 10/10 gets you into the race. Milliseconds decide who stands on the podium. Same score? ⏱️ Faster wins. Same score. Same time? 🎲 Fine... we'll let luck handle the pa

Showing the 12 most recent of 20 posts we hold for @wocnews. 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 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.

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.

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

“WavesOnChain News” (@wocnews), 154 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/wocnews.

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.