Telegram RegisterThe public register of Telegram
Telegram profile photo for TLS Tunnel Updates

Channel

TLS Tunnel Updates

@tlstunnelinfo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

235,373subscribers

+1,612 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001124737435
TypeChannel
Username@tlstunnelinfo
DescriptionOfficial TLS Tunnel updates channel. TLS Tunnel: https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel Email: [email protected]
Created3 June 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/tlstunnelinfo

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

233,280235,373234,326.56 August 2026 — 233,761 subscribers7 August 2026 — 233,757 subscribers8 August 2026 — 233,719 subscribers9 August 2026 — 233,728 subscribers10 August 2026 — 233,695 subscribers11 August 2026 — 233,518 subscribers12 August 2026 — 233,280 subscribers13 August 2026 — 233,496 subscribers14 August 2026 — 233,569 subscribers15 August 2026 — 233,646 subscribers17 August 2026 — 233,572 subscribers18 August 2026 — 233,585 subscribers19 August 2026 — 233,616 subscribers20 August 2026 — 233,706 subscribers21 August 2026 — 233,745 subscribers22 August 2026 — 233,907 subscribers24 August 2026 — 234,001 subscribers25 August 2026 — 234,041 subscribers26 August 2026 — 234,058 subscribers27 August 2026 — 234,090 subscribers28 August 2026 — 234,211 subscribers29 August 2026 — 234,311 subscribers30 August 2026 — 234,396 subscribers31 August 2026 — 234,482 subscribers1 September 2026 — 234,498 subscribers2 September 2026 — 234,517 subscribers4 September 2026 — 234,659 subscribers6 September 2026 — 234,774 subscribers9 September 2026 — 234,885 subscribers12 September 2026 — 234,753 subscribers13 September 2026 — 234,801 subscribers15 September 2026 — 234,895 subscribers17 September 2026 — 235,373 subscribers6 August 202617 September 2026
33 measurements spanning 42 days, net +1,612. 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 232,966–235,687 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 10:15235,373+478
15 Sept 2026, 11:01234,895+94
13 Sept 2026, 20:39234,801+48
12 Sept 2026, 00:57234,753-132
9 Sept 2026, 14:00234,885+111
6 Sept 2026, 07:17234,774+115
4 Sept 2026, 01:59234,659+142
2 Sept 2026, 15:48234,517+19
1 Sept 2026, 13:03234,498+16
31 Aug 2026, 11:35234,482+86
30 Aug 2026, 12:36234,396+85
29 Aug 2026, 12:52234,311+100
28 Aug 2026, 14:48234,211+121
27 Aug 2026, 16:34234,090+32
26 Aug 2026, 14:52234,058+17
25 Aug 2026, 16:38234,041+40
24 Aug 2026, 13:43234,001+94
22 Aug 2026, 20:49233,907+162
21 Aug 2026, 14:18233,745+39
20 Aug 2026, 12:25233,706first reading

Engagement

26 posts held, back to 26 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 101 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.0%
avg views ÷ 235,373 subscribers
Avg views / post
40,000
3 posts measured
Reaction rate
0.898%
reactions ÷ views · ER floor
Posts in window
3
of 26 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 23 September 2026
Posts held26 (26 January 202623 September 2026)
Views total120,140
Reactions total1,079
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 07:31 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

Links
182

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

10,745 reactions across 25 posts, in 11 distinct kinds. The most used accounts for 53.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5,75553.6%
👍1,68015.6%
👎1,36112.7%
🔥4964.62%
🤬3202.98%
👏2452.28%
🗿2312.15%
👌2292.13%
🙊1841.71%
🎉1501.40%
😱940.875%

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

Measured over the 26 most recent posts we hold, published 26 January 2026 to 23 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.

Telegram Stars

Stars received
40
across the posts below
Posts paid on
16
of 25 we hold a reading for · 64%
Most on one post
7
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tlstunnelinfo. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 26 most recent posts we hold for this entry, published 26 January 2026 to 23 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

23 Sept 2026, 22:39 UTC≈4,540 views50 reactionsread 24 September 2026
File

✔️ ALPN HTTP/2 and HTTP/1.1 on direct connections (TCP+TLS) ✔️ ALPN only HTTP/1.1 when using a Proxy (TCP+TLS) ✔️ WebRTC ALPN with SRTP extension in UDP mode (DTLS) and corresponding JA3 Profiles. ✔️ TCP PLPMTUD Enabled ✔️ Anti TCP OOB and Anti UDP/ICMP Storm ✔️ Payloads with support for hex "\x00 .. \xff" ✔️ And a few more fixes and optimizations 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel

31👍8👎6🔥3👌1👏1

9 Sept 2026, 19:31 UTC≈42,700 views397 reactionsread 24 September 2026
File

✔️ Crash when using proxy or private server fixed ✔️ ALPN only HTTP 1.1 enabling the use of CDN Proxy with TLS (Blind WebSocket) 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.4.1 [507] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

208👎74👍55🔥25🗿12🎉7🙊7👏6

26 Aug 2026, 17:42 UTC≈72,900 views632 reactions2 Starsread 24 September 2026
File

✔️ New connection method with UDP/DTLS ✔️ Host resolution with DoH ✔️ Recompilation of native libs for better performance ✔️ Fixed reconnection bug when wifi and mobile data were enabled at the same time. ✔️ And a few more improvements and minor bug fixes 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.4.0 [506] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

326👎118👍72🗿28👏22🔥18🙊18👌16

17 Aug 2026, 00:32 UTC≈82,100 views461 reactions2 Starsread 24 September 2026
File

✔️ Compatibility with 32-bit devices restored ✔️ Improvements to Anti-DPI and IO functions 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.3.1 [503] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

249👎91👍41🗿17🙊16🔥15🎉14👌9

11 Aug 2026, 00:12 UTC≈91,300 views334 reactionsread 24 September 2026

❗️ Bug fix on the servers For a few days, the official servers had a protocol bug that kept packet compression active for all connections, causing instability for users who hadn't enabled this option in the TLS Tunnel settings. Gaming, downloads, speed tests, and battery consumption were all affected. ✔️ This has now been fixed, and everyone can enjoy the algorithm improvements from the latest update. I apologize f

👍130115👎40🔥21🙊12👌11🗿5

10 Aug 2026, 00:47 UTC≈81,700 views335 reactions1 Starread 24 September 2026
File

✔️ Fixed Android 17 compatibility ✔️ New options for connection method and tunnel configuration ✔️ Improvements to the IO algorithm ✔️ Improvements to Anti-DPI ✔️ Security and integrity enhancements ✔️ Slight reduction in ad frequency ✔️ Removal of some clutter... 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.3.0 [502] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

182👎64👍36🔥17👌15🗿8🙊6🎉5

3 Aug 2026, 00:59 UTC≈83,800 views398 reactionsread 24 September 2026
File

✔️ Bug fix on reconnection (was not reconnecting after a drop) ✔️ Some shortcuts for system settings ✔️ Modification in the ad system ✔️ Some improvements in security and the default connection method 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.2.0 [500] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

206👎90👍32🔥18👌13🗿12🎉9👏9

29 Jul 2026, 23:51 UTCviews —

TLS Tunnel Updates pinned «🔓 List of open TCP/UDP ports on official servers By default, TLS Tunnel is configured with TCP ports 80 and 443 and offers a "CUSTOM" option, allowing you to set any TCP/UDP port between 1 and 10240. All ports in this range accept any type of payload and…»

23 Jul 2026, 20:00 UTC≈104,000 views502 reactions2 Starsread 24 September 2026
File

✔️ Security update ✔️ Improvements to the ad system ✔️ Some interface changes ✔️ Removal of unnecessary code ✔️ Some bug fixes 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.1.0 [498] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

275👎65👍64👌21👏19🔥17🗿17🙊14

12 Jul 2026, 21:30 UTC≈114,000 views440 reactions1 Starread 24 September 2026
File

⚠️ No 32-bit libraries - If your device's architecture is armeabi-v7a (32-bit), use version [485] temporarily. 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.0.6 [486] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

239👎58👍56🔥21🙊18🎉14🗿14👌13

12 Jul 2026, 21:08 UTC≈99,500 views212 reactionsread 24 September 2026
File

✔️ Some changes to the interface ✔️ Increased free renewal limit ✔️ Testing some ad networks ✔️ And some minor bug fixes 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.0.6 [485] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

116👍25👎25🔥13🎉7👌7🗿7🙊7

4 Jul 2026, 02:51 UTC≈106,000 views364 reactions2 Starsread 24 September 2026
File

✔️ A few more changes to ad behavior ✔️ And some bug fixes... 📣 Telegram Channel https://t.me/tlstunnelinfo ⬇️ Download TLS Tunnel 8.0.4 [482] https://play.google.com/store/apps/details?id=com.tlsvpn.tlstunnel

197👎61👍31🔥20🎉12👌12🗿11🙊11

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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 2 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.

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

“TLS Tunnel Updates” (@tlstunnelinfo), 235,373 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tlstunnelinfo.

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.