Telegram RegisterThe public register of Telegram
Telegram profile photo for OpenWrt NanoPi R2S

Channel

OpenWrt NanoPi R2S

@nanopi_r2s

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

3,470subscribers

-5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001462036850
TypeChannel
Username@nanopi_r2s
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 16 August 2026
On Telegramt.me/nanopi_r2s

Growth

3,4703,4753,472.57 August 2026 — 3,475 subscribers8 August 2026 — 3,474 subscribers10 August 2026 — 3,473 subscribers13 August 2026 — 3,470 subscribers7 August 202613 August 2026
4 measurements spanning 6 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 3,469–3,476 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:373,470-3
10 Aug 2026, 19:243,473-1
8 Aug 2026, 02:273,474-1
7 Aug 2026, 09:153,475first reading

Engagement

20 posts held, back to 19 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 13 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

122 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3327.0%
2823.0%
😢1814.8%
🥰1814.8%
😁119.02%
👏54.10%
🎉43.28%
🔥21.64%
10.82%
😱10.82%
🤔10.82%

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 17 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 122reactions 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 19 February 2026 to 13 July 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

13 Jul 2026, 06:48 UTC775 views1 reactionsread 7 August 2026

ImmortalWrt 25.12.1 released - Core components update - autocore: remove incorrect rps_cpus override - ca-certificates: update to 20260601 - cgi-io/dropbear/odhcpd/uhttpd: multiple CVE fixes - dnsmasq: update to 2.93 - fstools: enable f2fs overlay compression formatting - kernel: update to 6.12.94 - openssl: update to 3.5.7 - wireless-regdb: update to 2026.05.30 - Targets update - airoh

🔥1

13 Jul 2026, 06:48 UTC736 views0 reactionsread 7 August 2026

For existing ImmortalWrt 25.12.0 RC users, please note that we have moved all RC releases to archive server. You may update the apk feed URL with the following command: sed -i.bak "s,mirrors.vsean.net/openwrt,archive.immortalwrt.org,g" "/etc/apk/repositories.d/distfeeds.list" We would suggest upgrading to the latest stable release if possible.

1 Jun 2026, 00:21 UTC≈1,580 views16 reactionsread 7 August 2026

祝大家儿童节快乐🥳🥳🥳

🥰10🎉4👏2

27 May 2026, 01:56 UTC≈1,930 viewsread 7 August 2026

podman dns 最近有点抽风,如果固件选择器自定义构建出现 failed to fetch,可以在 1 分钟后再次尝试。

27 May 2026, 01:52 UTC≈1,710 views9 reactionsread 7 August 2026

ImmortalWrt 25.12.0 released An upgrade from ImmortalWrt 24.10 to ImmortalWrt 25.12 is supported in many cases with the help of the sysupgrade utility which will also attempt to preserve the configuration. A configuration backup is advised nonetheless when upgrading to ImmortalWrt 25.12. - Major core components update - Toolchain: - binutils 2.44 - gcc 14.3.0 - glibc 2.41 - musl 1.2.5

9

1 May 2026, 11:44 UTC≈1,920 views1 reactionsread 7 August 2026
Photo

See also: https://donate.imouto.in

1

27 Apr 2026, 07:13 UTC≈2,080 views3 reactionsread 7 August 2026

ImmortalWrt 24.10.6 released - Core components update - jsonfilter: fix CVE-2026-30873 (Memory leak in jsonpath) - kernel: update to 6.6.133 - luci: fix CVE-2026-32721 (Possible XSS attack via malicious SSID in LuCI WiFi scan modal) - procd: fix CVE-2026-30874 (Command execution via PATH environment variable filter bypass in procd) - umdns: fix CVE-2026-30871, CVE-2026-30872 - wireless-regdb: upda

1👍1🤔1

24 Apr 2026, 08:38 UTC≈1,650 views5 reactionsread 7 August 2026

ImmortalWrt 25.12.0-rc2 released ⚠️ This is just a release candidate and not the final release yet. - Core components update - hostapd: fix memory leak - kernel: update to 6.12.79 - mbedtls: update to 3.6.6 - openssl: update to 3.5.6 - Targets update - loongarch64 - add common pcie ethernet drivers by default - backport Motorcomm YT6801 PCIe driver - increase CMA size to 64M for d

👍5

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

Citation-graph rank

Citation-graph rank — 926,275 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“OpenWrt NanoPi R2S” (@nanopi_r2s), 3,470 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/nanopi_r2s.

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.