Telegram RegisterThe public register of Telegram
Telegram profile photo for HLS-Proxy

Channel

HLS-Proxy

@hlsproxy

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

386subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001261850290
TypeChannel
Username@hlsproxy
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/hlsproxy

Growth

386387386.57 August 2026 — 387 subscribers8 August 2026 — 387 subscribers23 August 2026 — 386 subscribers7 August 202623 August 2026
3 measurements spanning 16 days, net -1. 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 386–387 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 23:16386-1
8 Aug 2026, 06:03387no change
7 Aug 2026, 21:20387first reading

Engagement

20 posts held, back to 27 November 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 9 November 2022. An engagement rate over an empty window would be a number about nothing.

Reaction mix

132 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 88.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11788.6%
107.58%
🔥53.79%

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 16 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 132reactions 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 27 November 2021 to 9 November 2022, 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

9 Nov 2022, 19:23 UTC≈4,080 views10 reactionsread 8 August 2026

FYI, For all versions prior 8.4.0 from now on is impossible to auto update hls-proxy due change of update server URL. You can still update hls-proxy manually.

👍64

7 Oct 2022, 14:24 UTC≈3,770 views13 reactionsread 8 August 2026

v8.4.6 - Config: Automatically select first enabled playlist - Config: New option: isHtmlPlayerEnabled (play inline video) - Channel db fixes - Fix UI error popup - Add "country" to group config. Allows to reassign channel group to country based detection. - Normalize quotes in channel name - Add "get playlist by user/pass" into client section of config

👍103

24 Sept 2022, 08:24 UTC≈2,920 views12 reactionsread 8 August 2026

v8.4.5 - Allow epg match by tvg-name - Add isRestreamer option (works with isAllowUsersWithAnyToken: true) - Added /restream api endpoint to separate it from usual users - Fix epgMatch - Fix ffmpeg stop - Change ffmpeg default parameters

👍102

11 Sept 2022, 08:35 UTC≈2,560 views6 reactionsread 8 August 2026

v8.4.4 - Allow custom login page path - Update default userAgent - XC API: return correct exp_dat - Fix EPG parser

🔥5👍1

4 Sept 2022, 22:17 UTC≈2,310 views8 reactionsread 8 August 2026

v8.4.2 - Fix open stream from web browser if isSkipBitrateChoice: true - Fix FreeBSD binary - Fix wrong channel id generation in /getchannelid - Fix archive playback if isSkipBitrate checked

👍8

2 Sept 2022, 05:24 UTC≈2,010 views6 reactionsread 8 August 2026

v8.4.0 - Add initial Xtream Codes Player API - Playlist link supports ?username=user&password=pass without token

👍6

21 Aug 2022, 06:34 UTC≈2,240 views9 reactionsread 8 August 2026

v8.3.1 - Bump node 16.16.0 - Fix logos - Stop channel if admin removed it from the playlist - Fix channelHandler error handling - Proper behavior of isSkipBitrateChoice - Fix exact epg match - Add description to epg in status - More archive support - Fix epg country match - Fix favorite toggle - Fix plugin.error

👍9

18 Jul 2022, 16:13 UTC≈1,790 views10 reactionsread 8 August 2026

v8.2.3 - Fix unhandled rejection message - Add logos - Fix multiaccount detect timeout - Add PageUp/PageDown keys in channels - Fix epgTime - Fix 'keep-alive' regression for Kodi - Bump dependencies

👍10

5 Jul 2022, 17:05 UTC≈1,710 views6 reactionsread 8 August 2026

8.2.2 - Fix group sorting - Add client search by token or username in config - Fix pooler config exception - Fix groups.json - Add/Fix channels db - Add streams count to status - Fix multiaccount detector - Remove runme.cmd dependency for win-x86 build

👍6

24 Jun 2022, 09:28 UTC≈1,640 views10 reactionsread 8 August 2026

v8.2.1 - Fix playlist parse failure (Rare case) - Fix empty group-title tag - Add reserved streams config (no need for plugin anymore) - Optimize get playlist code - Small UI fixes - New pooler config format (prepare for autodetect) - Add Windows 7 support - Fix VOD GC memory leak - Bump node 16.15.0 for all builds (security patches applied) - Fix stream stuck with no clients - Fix archive to use pooler - Add runme.c

👍10

7 Jun 2022, 06:41 UTC≈1,540 views8 reactionsread 8 August 2026

v8.2.0 - #KODIPROP tag support - Fix headers on ts chunk - Add isAllowRangeHeader - Fix bad sequences - Stop stream when no more chunks available - Add clientCount to status response - Add web status console to Log - Fix big files handling - Fix content-type for file - Add group sorting by config order - Fix status loading daisy wheel - Add VOD rewind (mpegts not supported) - Breaking changes for playlist queue - Add

👍8

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

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

“HLS-Proxy” (@hlsproxy), 386 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/hlsproxy.

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.