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

Channel

Surfboard News

@surfboardnews

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

28,380subscribers

+29 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001216277120
TypeChannel
Username@surfboardnews
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/surfboardnews

Growth

28,35128,38028,365.56 August 2026 — 28,351 subscribers6 August 2026 — 28,354 subscribers7 August 2026 — 28,366 subscribers9 August 2026 — 28,374 subscribers10 August 2026 — 28,377 subscribers10 August 2026 — 28,375 subscribers11 August 2026 — 28,372 subscribers12 August 2026 — 28,373 subscribers13 August 2026 — 28,377 subscribers15 August 2026 — 28,380 subscribers6 August 202615 August 2026
10 measurements spanning 9 days, net +29. 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,347–28,384 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:4428,380+3
13 Aug 2026, 16:0928,377+4
12 Aug 2026, 17:3628,373+1
11 Aug 2026, 18:3728,372-3
10 Aug 2026, 21:2128,375-2
10 Aug 2026, 00:0228,377+3
9 Aug 2026, 00:5228,374+8
7 Aug 2026, 21:3128,366+12
6 Aug 2026, 21:5528,354+3
6 Aug 2026, 11:0728,351first reading

Engagement

20 posts held, back to 25 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 23 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.2%
avg views ÷ 28,380 subscribers
Avg views / post
7,170
2 posts measured
Reaction rate
0.544%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 3 August 2026
Posts held20 (25 February 20263 August 2026)
Views total14,330
Reactions total78
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 04:54 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
144

Lifetime counters from Telegram’s own channel header, read 16 August 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

875 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 46.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
40346.1%
👍30234.5%
👏10812.3%
🎉242.74%
🔥141.60%
🥰141.60%
🏆20.229%
🐳20.229%
👎20.229%
😈20.229%
🙏10.114%
🤨10.114%

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 20 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 875reactions 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 25 February 2026 to 3 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

3 Aug 2026, 16:01 UTC≈4,900 views42 reactionsread 16 August 2026
File

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

👍2318👎1

18 Jul 2026, 18:22 UTC≈9,430 views36 reactionsread 16 August 2026
File

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

👍279

5 Jul 2026, 07:10 UTC≈12,600 views42 reactionsread 16 August 2026
File

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

👍308🔥2🏆1🐳1

2 Jul 2026, 14:57 UTC≈12,200 views26 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.32.3 Improvements - Support entering multiple IP addresses (comma-separated) in single DNS host record.

👍242

27 Jun 2026, 16:04 UTC≈14,600 views39 reactionsread 16 August 2026
File

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

🎉2411👍2🐳1👏1

8 Jun 2026, 15:49 UTC≈16,500 views39 reactionsread 16 August 2026
File

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

29👍8👎1🙏1

26 May 2026, 17:46 UTC≈16,400 views33 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.31.0 Improvements - Optimized profile import speed. - Added speed test warmup to reduce cold-start bias on measurement accuracy. Fixes - Fixed large domain-based rulesets (RULE-SET) not taking effect. - Fixed incorrect parsing of trailing comment text in configuration lines. - Fixed severely underreported rule counts for DOMAIN-SET and nested RULE-SET.

👏257😈1

26 May 2026, 17:24 UTC≈13,100 views11 reactionsread 16 August 2026
File

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

👏74

24 May 2026, 16:51 UTC≈15,800 views56 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/tv-1.1.0 ### New Features - Added Explorer service with QR code for profile import - Added DNS and Private IP cards to dashboard - Added speed test entry to Tools row - Support Snell/AnyTLS/Hysteria2/Shadowsocks 2022 protocol - Support Smart proxy group type(fallback to auto) - Support underlying-proxy to chain proxies - Support all Host DNS rule types for prox

41👏10🥰5

4 May 2026, 15:56 UTC≈15,900 views56 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.30.0 mobile-2.30.0 - New Features - Underlying Proxy (Proxy Chain): Support proxy chaining for any proxy type. - Picture-in-Picture Speed Window: Floating network speed display. (Requires Android 8+) - Profile Editor Keyboard Shortcuts: Readline-style shortcuts (Ctrl+T, Ctrl+A/E, etc.). - HTTP Basic Auth for External Resources: Support authenti

👍3221👏2🥰1

22 Apr 2026, 18:04 UTC≈18,600 views38 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.29.6 mobile-2.29.6 - New Features - Lower MTU Limit: MTU can now be lowered down to 1400. - DoH Item in Host List: Host list now supports adding DoH server entries. - Fixes - Fixed several crash issues. - Fixed OOM when decoding large profiles.

32👏5👍1

19 Apr 2026, 17:54 UTC≈16,600 views40 reactionsread 16 August 2026
File

https://github.com/getsurfboard/surfboard/releases/tag/mobile-2.29.5 New Features DoH Server in Host Rules: DNS over HTTPS servers can now be configured in the [Host] section of profiles. Proxy Group Icon URL Parsing: Proxy groups now support parsing the icon-url parameter (UI display not yet supported). Quoted Proxy Names: Proxy names wrapped in quotes are now fully supported in lookup, validation, and UI display.

28👍6👏4🥰2

Showing the 12 most recent of 20 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.

Citation-graph rank

Citation-graph rank — 624,158 of 1,481,217entries 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.

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.

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.

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.

科学上网观察与机场测速
@jichangtj · 133,388
Telegram ranks this channel #53 of 54 here — alongside 53 others — read 15 August 2026
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 100,041
Telegram ranks this channel #56 of 56 here — alongside 55 others — read 15 August 2026

This channel appears in 2 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Surfboard News” (@surfboardnews), 28,380 subscribers as measured 15 August 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.