Telegram RegisterThe public register of Telegram
Telegram profile photo for NBA League Pass DP

Channel

NBA League Pass DP

@NBA_League_Pass_Premium

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry

86subscribers

+2 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-1002119986073
TypeChannel
Username@NBA_League_Pass_Premium
Created23 April 2024 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/NBA_League_Pass_Premium

Topic

Gaming — 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 28 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

8486857 August 2026 — 84 subscribers9 August 2026 — 84 subscribers28 September 2026 — 85 subscribers8 October 2026 — 86 subscribers7 August 20268 October 2026
4 measurements spanning 62 days, net +2. 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 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 07:5686+1
28 Sept 2026, 15:1585+1
9 Aug 2026, 17:1784no change
7 Aug 2026, 12:3784first reading

Engagement

6 posts held, back to 23 April 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 6 posts for this entry, the most recent from 29 April 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
28s
Average length
28s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

7 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤342.9%
👍342.9%
🤔114.3%

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

Measured over the 6 most recent posts we hold, published 23 April 2024 to 29 April 2024, 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

29 Apr 2024, 12:17 UTC≈3,160 views4 reactionsread 9 August 2026
Video

🇺🇸在IOS上的使用教程 #教程 录制视频时的网络环境:肉身墙内,🚀Shadowrocket全局(代理)新加坡🇸🇬ip 首次观看需要将定位设置为「使用APP期间」随即关闭「精确位置」 最好还把「允许跟踪」关闭 还不能看就是节点没有解锁 所以说这玩意到底有多难呢?折腾了一个月都还看不了的是不是真要反思自己的问题⁉

❤3🤔1

Signed RoCo

27 Apr 2024, 14:42 UTC≈2,830 viewsread 9 August 2026
Photo

🇺🇸NBA LEAGUE PASS涨价📈 #涨价 可用于合租的方案PREMIUM已从₺599.99涨价到了₺869.99,涨幅45%,约合人民币60 赶上末班车的车友就偷着乐吧😁

Signed RoCo

24 Apr 2024, 15:56 UTC≈2,170 views3 reactionsread 9 August 2026
Photo

#DP 曾经能在IOS上看的车友如果发现换账号提示需要购买订阅,可以尝试重装App 已经过本人同意 via @djenfkd

👍3

Signed RoCo

23 Apr 2024, 06:38 UTC≈1,690 views0 reactionsread 9 August 2026

Q:为何创建该频道? A:方便各位交流🍎系统上NBA在🇨🇳大陆的使用技巧 Q:之前的群组呢? A: @Lile168 于2024年3月17日 上车,该人称其不会使用IOS客户端观看NBA,车主心软,与其协商后允许其月付上车,若一个月内其使用无问题,再改为年付上车。并且十分好心地创建了群组供其学习。4月15日,该人对车主的提醒付费未读未回。4月17日上午,该人将某车友发送给其的账号恶意多端登录,导致其他车友无法正常观看。在车主正准备处理该问题时,其在群组发言。 @Lile168 上线时间和账号异常时间高度吻合,很明显, @Lile168 是拿到了某人发送给他的账号密码,这严重违反了合租规则。因此车主决定解散NBA交流群,改用频道进行交流。 另外也提醒各位车友,将账号密码发送给互联网上的陌生人是对车主和车友极其不负责任的行为,一经发现,拉黑踢车不退款。目前已处理本次事件中的违规车友。

Signed RoCo

Showing the 6 most recent of 6 posts we hold for @NBA_League_Pass_Premium. 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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“NBA League Pass DP” (@NBA_League_Pass_Premium), 86 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/NBA_League_Pass_Premium.

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.