Telegram RegisterThe public register of Telegram
Telegram profile photo for Remnawave

Channel

Remnawave

@remnawave

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

13,446subscribers

+1,120 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002421403148
TypeChannel
Username@remnawave
Created2 February 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live5 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/remnawave

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.

Growth

12,32613,44612,8867 August 2026 — 12,326 subscribers7 August 2026 — 12,326 subscribers8 August 2026 — 12,355 subscribers9 August 2026 — 12,359 subscribers10 August 2026 — 12,373 subscribers11 August 2026 — 12,398 subscribers12 August 2026 — 12,415 subscribers14 August 2026 — 12,423 subscribers15 August 2026 — 12,435 subscribers16 August 2026 — 12,469 subscribers17 August 2026 — 12,499 subscribers19 August 2026 — 12,525 subscribers20 August 2026 — 12,554 subscribers21 August 2026 — 12,570 subscribers22 August 2026 — 12,604 subscribers24 August 2026 — 12,636 subscribers25 August 2026 — 12,662 subscribers26 August 2026 — 12,672 subscribers27 August 2026 — 12,690 subscribers28 August 2026 — 12,721 subscribers29 August 2026 — 12,727 subscribers29 August 2026 — 12,737 subscribers30 August 2026 — 12,749 subscribers31 August 2026 — 12,777 subscribers1 September 2026 — 12,793 subscribers2 September 2026 — 12,816 subscribers4 September 2026 — 12,839 subscribers6 September 2026 — 12,892 subscribers10 September 2026 — 12,965 subscribers12 September 2026 — 13,004 subscribers14 September 2026 — 13,034 subscribers15 September 2026 — 13,065 subscribers17 September 2026 — 13,114 subscribers28 September 2026 — 13,315 subscribers5 October 2026 — 13,446 subscribers7 August 20265 October 2026
35 measurements spanning 58 days, net +1,120. 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 12,158–13,614 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
5 Oct 2026, 02:0113,446+131
28 Sept 2026, 03:3513,315+201
17 Sept 2026, 20:2213,114+49
15 Sept 2026, 16:4013,065+31
14 Sept 2026, 03:3613,034+30
12 Sept 2026, 10:1613,004+39
10 Sept 2026, 05:1612,965+73
6 Sept 2026, 23:1712,892+53
4 Sept 2026, 07:4112,839+23
2 Sept 2026, 22:1512,816+23
1 Sept 2026, 18:4612,793+16
31 Aug 2026, 20:1412,777+28
30 Aug 2026, 23:1412,749+12
29 Aug 2026, 21:3712,737+10
29 Aug 2026, 00:1312,727+6
28 Aug 2026, 02:1512,721+31
27 Aug 2026, 00:2412,690+18
26 Aug 2026, 01:5512,672+10
25 Aug 2026, 04:5412,662+26
24 Aug 2026, 02:0812,636first reading

Engagement

9 posts held, back to 2 February 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 45 pages 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 9 posts for this entry, the most recent from 19 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

950 reactions across 7 posts, in 24 distinct kinds. The most used accounts for 30.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥28730.2%
❤24726.0%
👍18919.9%
❤‍🔥596.21%
🙏434.53%
😱181.89%
🤯161.68%
👎151.58%
🥰141.47%
👏101.05%
😁80.842%
😭80.842%
🤝80.842%
🍌50.526%
🤷‍♂40.421%
⚡30.316%
😍30.316%
🙈30.316%
🏆20.211%
🐳20.211%
4 further kinds60.632%

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

Measured over the 9 most recent posts we hold, published 2 February 2025 to 19 June 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

19 Jun 2026, 20:22 UTCviews —

Remnawave pinned «⚠️ Security Notice Recently, a user reported a critical vulnerability in the Subscription Page. The issue was identified and fixed. ☄️ Please update Subscription Page to version 7.2.5 immediately. If you installed the Subscription Page using the instructions…»

19 Jun 2026, 20:22 UTC≈25,800 views272 reactionsread 2 September 2026
Forwarded from @remnalog

⚠️ Security Notice Recently, a user reported a critical vulnerability in the Subscription Page. The issue was identified and fixed. ☄️ Please update Subscription Page to version 7.2.5 immediately. If you installed the Subscription Page using the instructions on website, the update command looks like this: cd /opt/remnawave/subscription && docker compose pull && docker compose down && docker compose up -d && dock…

👍135🙏43❤40😱18🤯12🤝8🔥6😁4

28 Mar 2026, 03:43 UTC≈59,700 views332 reactionsread 2 September 2026
Photo

🏴‍☠️ Remnawave v2.7.0 is ready! Node Plugins (Torrent Blocker, Ingress & Egress Filters, Connection Drop), Hysteria2 (Xray-Json only), KCP transport, Sessions Explorer, revamped Telegram notifications, new Prometheus metrics, and much more. ⚠️ This release contains breaking changes. Please read the changelog and make a backup before updating! 🆕 Learn more about Node Plugins β 👀 Check out release notes and changelo…

🔥179❤61❤‍🔥54👏10👎9🍌5👍4😁4

10 May 2025, 19:00 UTC≈88,800 views200 reactionsread 2 September 2026
Photo

🏴‍☠️ Remnawave v1.6.0 is ready! This release was mostly focused on refining RestAPI schema to match RestAPI standarts. Also: updated structure of the documentation site, support for login via Telegram, custom tags, completely rewritten backend part of the @remnawave/subscription-page component. → Check out release notes and changelog here → Upgrading guide → v1.6.0 RestAPI Schema –––––––––––––––––– 😈 Report bug…

❤86🔥57👍19🥰14😭8👎6❤‍🔥5🤷‍♂4

6 Apr 2025, 20:35 UTC≈58,400 views59 reactionsread 2 September 2026
Photo

🏴‍☠️ Remnawave v1.5.0 is now LIVE! Bulk actions with users, full mTLS between the panel and nodes, reworking of some UI elements, xHTTP Extra and much more. → Check out release notes and changelog here → Updating guide → v1.5.0 RestAPI Schema –––––––––––––––––– 😈 Report bug 💪 Request new feature ❤️ Support Remnawave (no registration required!) –––––––––––––––––– 🦵 Don't forget to follow and star – https://g…

❤30🔥21👍6💯2

13 Feb 2025, 21:33 UTC≈37,900 views53 reactionsread 2 September 2026
Photo

🦋

👍25❤16🔥4🤯4😍3🎉1

11 Feb 2025, 18:55 UTC≈28,200 views8 reactionsread 2 September 2026

1️⃣ https://t.me/+c8wKd62eIAE4ZDdi

❤8

11 Feb 2025, 18:40 UTC≈25,600 views26 reactionsread 2 September 2026
Sticker

Sticker, posted without a caption

🔥20❤6

Showing the 9 most recent of 9 posts we hold for @remnawave. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Remnawave” (@remnawave), 13,446 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/remnawave.

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.