Telegram RegisterThe public register of Telegram
Telegram profile photo for ByWave Channel

Channel

ByWave Channel

@bywavego

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

9,899subscribers

-16 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001492205869
TypeChannel
Username@bywavego
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/bywavego

Growth

9,8999,9459,9226 August 2026 — 9,915 subscribers6 August 2026 — 9,915 subscribers10 August 2026 — 9,929 subscribers12 August 2026 — 9,942 subscribers15 August 2026 — 9,945 subscribers18 August 2026 — 9,939 subscribers21 August 2026 — 9,930 subscribers24 August 2026 — 9,927 subscribers28 August 2026 — 9,925 subscribers31 August 2026 — 9,918 subscribers3 September 2026 — 9,916 subscribers9 September 2026 — 9,899 subscribers6 August 20269 September 2026
12 measurements spanning 33 days, net -16. 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 9,892–9,952 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:179,899-17
3 Sept 2026, 21:429,916-2
31 Aug 2026, 03:549,918-7
28 Aug 2026, 06:159,925-2
24 Aug 2026, 20:179,927-3
21 Aug 2026, 10:149,930-9
18 Aug 2026, 12:569,939-6
15 Aug 2026, 19:199,945+3
12 Aug 2026, 17:339,942+13
10 Aug 2026, 00:309,929+14
6 Aug 2026, 21:009,915no change
6 Aug 2026, 20:539,915first reading

Engagement

18 posts held, back to 7 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 9,899 subscribers
Avg views / post
1,350
1 post measured
Reaction rate
2.00%
reactions ÷ views · ER floor
Posts in window
1
of 18 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
WindowRolling 30 days · latest post in window 27 August 2026
Posts held18 (7 March 202527 August 2026)
Views total1,350
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 04: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.

Reaction mix

5,611 reactions across 18 posts, in 35 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩2,66747.5%
👍68412.2%
🤬57010.2%
😭5569.91%
👎2354.19%
2083.71%
🤡1773.15%
👏1703.03%
😡460.82%
🤮410.731%
💔290.517%
🌚280.499%
🙏190.339%
😱180.321%
😐160.285%
🤷‍♂160.285%
🥰140.25%
🙊130.232%
🤪120.214%
🤯120.214%
15 further kinds801.43%

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 18 of the 18 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 5,611 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 7 March 2025 to 27 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

27 Aug 2026, 04:16 UTC≈1,350 views27 reactionsread 29 August 2026

我们的 iOS 客户端现已可用, 您可访问知识库查看使用教程 https://u.bws.lol/kb/bywave-ios-nextin

💩19👏6👍2

6 Jun 2026, 07:10 UTC≈13,000 views828 reactionsread 29 August 2026

我们已完成协议的更换, 请您前往官网获取最新的订阅链接重新订阅节点

💩687👎65🤮23👍19💔178🌚4🤡3

5 Jun 2026, 12:58 UTC≈13,500 views175 reactionsread 29 August 2026

我们将逐步丢弃SS协议的节点并全面更换为anytls, 若您在此过程中发现无法使用请立即更新订阅。我们将从香港以外的节点开始进行此进程。

💩157👏94👍3🔥2

8 Mar 2026, 13:27 UTC≈23,300 views276 reactionsread 29 August 2026
File

我们已发布全新客户端, 我们建议您在安装后卸载老版客户端, 若有任何问题欢迎通过客服系统反馈

💩22018🤡13🤮7🤔6👍4👎3😐3

22 Feb 2026, 04:56 UTC≈23,000 views214 reactionsread 29 August 2026

神秘代码: BG6ZH1QC90 名额 50

💩15238😭20💊2🤮2

19 Feb 2026, 04:03 UTC≈22,900 views196 reactionsread 29 August 2026

神秘代码: S9WN4VJ4S7 名额 20

💩115😭3719👎12🤡5👍4💊2🤮1

11 Feb 2026, 06:25 UTC≈22,700 views232 reactionsread 29 August 2026

因供应商IP切换疏忽导致断线,我们正全力推进服务商更换并优化网络。补偿将于稍后发放。给您带来不便,敬请谅解。

💩163😱18😡15👍12👌87🤡6💊2

10 Feb 2026, 07:21 UTC≈20,800 views182 reactionsread 29 August 2026

ByWave向您致以最诚挚的节日祝福! 我们特别为您准备了以下独家优惠: 所有套餐现享8折优惠!使用优惠码:43E3GWANYD 我们还将在 TG 频道不定时发放 5 折优惠码 请享受我们为您准备的节日特惠, 祝您假期愉快。 感谢您选择ByWave.

💩120👏3123🤡5🤔2🤮1

30 Jan 2026, 05:37 UTC≈18,700 views149 reactionsread 29 August 2026

上游正在對出口路由進行調整, 期間可能會出現節點延遲升高或無法訪問等情況, 我們將在完成該進程後通知各位

💩13310🌚5🤮1

22 Dec 2025, 05:18 UTC≈22,900 views262 reactionsread 29 August 2026

很抱歉我們的郵件係統出現了莫名的遞歸循環導致所有用戶收到了不屬於自己的郵件, 我們現已修復該問題並為各位用戶發放 5 元餘額作為此次事件的補償.

💩172🤡2220👍19🤬13😐9🎄6🤮1

21 Dec 2025, 09:06 UTC≈21,800 views85 reactionsread 29 August 2026

我們已啟用永久域名如下: bw.icu byw.lol 閣下可通過以上域名永久訪問我們的用戶中心.

💩51👍292🤮2👏1

29 Sept 2025, 08:25 UTC≈27,700 views369 reactionsread 29 August 2026

我們已向所有符合條件的客戶賬戶發放餘額50元作爲近期遭受DDoS攻擊導致服務不穩定的補償。

👍199💩87🤡34👎2216🕊4🤔2🥰2

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

Named by 1 registered channel — 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“ByWave Channel” (@bywavego), 9,899 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/bywavego.

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.