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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
33 measurements spanning 43 days, net +87. 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 28,338–28,451 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
18 Sept 2026, 00:59
28,438
+14
15 Sept 2026, 22:40
28,424
+7
14 Sept 2026, 08:19
28,417
+2
12 Sept 2026, 19:56
28,415
+10
10 Sept 2026, 21:37
28,405
-6
7 Sept 2026, 19:19
28,411
+10
3 Sept 2026, 06:49
28,401
-3
2 Sept 2026, 02:27
28,404
+2
1 Sept 2026, 05:26
28,402
+2
31 Aug 2026, 02:16
28,400
-9
30 Aug 2026, 05:46
28,409
+12
29 Aug 2026, 07:46
28,397
-1
28 Aug 2026, 09:11
28,398
+12
27 Aug 2026, 06:19
28,386
-4
26 Aug 2026, 04:52
28,390
-14
25 Aug 2026, 03:37
28,404
-5
24 Aug 2026, 00:17
28,409
-4
22 Aug 2026, 07:37
28,413
+1
20 Aug 2026, 19:04
28,412
+6
19 Aug 2026, 20:02
28,406
first reading
Engagement
24 posts held, back to 25 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 67 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
22.3%
avg views ÷ 28,438 subscribers
Avg views / post
6,340
2 posts measured
Reaction rate
0.442%
reactions ÷ views · ER floor
Posts in window
2
of 24 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
Window
Rolling 30 days · latest post in window 20 September 2026
Posts held
24 (25 February 2026 – 20 September 2026)
Views total
12,670
Reactions total
56
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
25 Sept 2026, 07:27 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
8
Links
148
Lifetime counters from Telegram’s own channel header, read 25 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
993 reactions across 24 posts, in 18 distinct kinds. The most used accounts for 47.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
468
47.1%
👍
343
34.5%
👏
110
11.1%
🎉
24
2.42%
🥰
16
1.61%
🔥
14
1.41%
👎
3
0.302%
🏆
2
0.201%
🐳
2
0.201%
🕊
2
0.201%
😈
2
0.201%
🌚
1
0.101%
😢
1
0.101%
🙏
1
0.101%
🤣
1
0.101%
🤨
1
0.101%
🤮
1
0.101%
🥱
1
0.101%
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 24 of the 24 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 993 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 25 February 2026 to 20 September 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.
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.35.1
mobile-2.35.1
- New Features
- External Resource Auto-Update: RULE-SET, DOMAIN-SET and policy-path resources can declare an update-interval and are refreshed automatically in the background.
- Rule support for Surge port expressions (DEST-PORT / SRC-PORT / IN-PORT ranges and operators), SRC-IP CIDR, and bare IP addresses (treated as a /32 or /1…
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.34.4
New Features
- Pinned Profile Shortcuts: Pinned profiles now appear as dynamic launcher shortcuts; long-press the app icon to switch profiles directly.
- Hysteria2: support the gecko-password parameter.
- VMess: support the encrypt-method parameter.
- Maximum MTU raised from 32000 to 64000.
Fixes
- Fixed screen flicker when starting the VPN via a …
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.34.3
Fixes
- Fixed SSH Dump crashing the app when enabled.
- Fixed crash when opening the file picker on devices without a file manager (e.g. some TV boxes).
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.34.2
New Features
- Default Profile: Fresh installs now include a ready-to-use default profile with built-in ad-blocking rules.
Fixes
- Fixed the snackbar floating above the bottom navigation bar when using 3-button navigation.
- Fixed connections hanging when IPv6 is unreachable; they now fail fast.
- Fixed rules not updating after the content of a DO…
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.34.1
New Features
- Backup & Restore: Export app settings and proxy profiles to a password-protected archive and restore them on another device. Cross-version compatible.
- Subnet Proxy Group: Support the subnet group type, which automatically selects a proxy based on the current network environment (e.g. WiFi, cellular, SSID, gateway).
- mDNS Resolutio…
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.33.0
New Features
- TUIC v5: Support TUIC v5 proxy protocol.
- [Host] Rule Sets: Support DOMAIN-SET and RULE-SET entries in the [Host] section for assigning DNS servers to domain lists.
Fixes
- Fixed idle connections causing continuous CPU usage and battery drain.
- Fixed UDP not working for AnyTLS/Trojan/VMess/Snell proxies when chained over a TCP-onl…
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.32.4
New Features
- AnyTLS UDP Relay: Support UDP relay for AnyTLS proxies.
- UDP Proxy Chaining: Support underlying-proxy to chain proxies for UDP traffic.
Fixes
- Fixed UDP proxy not updating when switching selections in a proxy group.
Improvements
- Improved speed test accuracy for proxies using underlying-proxy.
- Simplified proxy group list to a …
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.32.3
Improvements
- Support entering multiple IP addresses (comma-separated) in single DNS host record.
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.32.2
New Features
- DOMAIN-WILDCARD Rule: Support DOMAIN-WILDCARD rule type for matching domain names with wildcards.
- Salamander Password for Hysteria2: Support salamander-password parameter for Hysteria2 proxy.
- Turkish Language: Add Turkish language support.
Fixes
- Fix Shadowsocks AEAD buffer overflow crash.
- Fix missing syntax highlighting keyw…
https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.31.1
New Features
- TLS Certificate Pinning: Support server-cert-fingerprint-sha256 parameter to pin server TLS certificates. Works with all TLS-based proxies (Trojan, VMess, Hysteria2, AnyTLS, Snell, HTTPS, SOCKS5-TLS).
- Snell v4: Support Snell v4 protocol.
- Explorer URL Import: Support importing profiles from URLs directly via the Explorer web servi…
https://github.com/getsurfboard/surfboard/releases/tag/tv-1.1.1
**Fixes**
- Fixed some HTTPS proxies not working
- Fixed incorrect parsing of trailing comments in profile files
- Fixed inaccurate rule count for DOMAIN-SET and nested RULE-SET
- Fixed mobile version checker incorrectly prompting for TV app updates
- Fixed some DOMAIN-SET/RULE-SET not taking effect
👏7❤4
Showing the 12 most recent of 24 posts we hold for @surfboardnews. 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
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
Named by 4 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.
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.
Yet Another Public Notification Channel @yapnc · 7,517#1
Read from Telegram’s recommendation API, most recently 9 September 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.
Github_2dust @github_2dust · 91,394 Telegram ranks this channel #1 of 71 here — alongside 70 others — read 17 August 2026
Yamby Release @yamby_release · 36,793 Telegram ranks this channel #5 of 29 here — alongside 28 others — read 1 September 2026
Matsuridayo GitHub @MatsuriDayo · 45,413 Telegram ranks this channel #30 of 58 here — alongside 57 others — read 30 August 2026
FlClash Channel @FlClash · 46,371 Telegram ranks this channel #37 of 53 here — alongside 52 others — read 28 August 2026
֍可莉日常֎ @ibilibili · 47,636 Telegram ranks this channel #40 of 40 here — alongside 39 others — read 14 September 2026
Shadowrocket News @ShadowrocketNews · 46,743 Telegram ranks this channel #40 of 60 here — alongside 59 others — read 27 August 2026
Duyao|SpeedTest|科技生活|资讯转发 @DuyaoSS · 67,712 Telegram ranks this channel #45 of 45 here — alongside 44 others — read 20 August 2026
Loon News @LoonNews · 46,023 Telegram ranks this channel #46 of 49 here — alongside 48 others — read 27 August 2026
Appinn Feed|小众软件 @appinnfeed · 33,361 Telegram ranks this channel #52 of 52 here — alongside 51 others — read 4 September 2026
科学上网观察与机场测速 @jichangtj · 134,124 Telegram ranks this channel #53 of 54 here — alongside 53 others — read 15 August 2026
Apple Nuts @AppleNuts · 37,006 Telegram ranks this channel #56 of 56 here — alongside 55 others — read 1 September 2026
前女友们用过的机场—始于机场,不止机场 @gebaopiCloud · 101,135 Telegram ranks this channel #56 of 56 here — alongside 55 others — read 15 August 2026
APPDO 数字生活指南 @AppDoDo · 40,358 Telegram ranks this channel #57 of 57 here — alongside 56 others — read 30 August 2026
QAuxiliary @QAuxiliary · 44,820 Telegram ranks this channel #58 of 58 here — alongside 57 others — read 12 September 2026
Legado|开源阅读|频道 @Legado_Channels · 93,002 Telegram ranks this channel #58 of 61 here — alongside 60 others — read 17 August 2026
Clash Verge Rev Channel @clash_verge_re · 80,521 Telegram ranks this channel #60 of 64 here — alongside 63 others — read 19 August 2026
This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“Surfboard News” (@surfboardnews), 28,438 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/surfboardnews.
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.