Telegram RegisterThe public register of Telegram
Telegram profile photo for 英雄联盟 LPL KPL 电竞赛事推单

Channel

英雄联盟 LPL KPL 电竞赛事推单

@obdjss

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,316subscribers

-4,271 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001863090998
TypeChannel
Username@obdjss
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/obdjss

Topic

Gambling & betting — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 10 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@obzs999g/1443331 Jul 2026, 13:37 UTC@obdjss/4890 · this entry31 Jul 2026, 13:37 UTC1.00under a minute
@obzs999g/144351 Aug 2026, 13:56 UTC@obdjss/4891 · this entry1 Aug 2026, 13:57 UTC1.0072 seconds
@obzs999g/144434 Aug 2026, 14:43 UTC@obdjss/4892 · this entry4 Aug 2026, 14:44 UTC1.00under a minute
@obzs999g/144466 Aug 2026, 13:48 UTC@obdjss/4893 · this entry6 Aug 2026, 13:48 UTC1.00under a minute
@obzs999g/144539 Aug 2026, 14:21 UTC@obdjss/4894 · this entry9 Aug 2026, 14:21 UTC1.00under a minute
@obzs999g/1445811 Aug 2026, 14:16 UTC@obdjss/4895 · this entry11 Aug 2026, 14:16 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@obzs999g6 (6/6 hand-verifiable sample passed)1.00under a minute@obzs999g (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 23 May 2026 to 11 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 10 channels, the one whose matching posts we hold earliest is @obzs999g. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 10 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

1 more channel is in this same group but not listed individually here.

Growth

1,3165,5873,451.57 August 2026 — 5,587 subscribers7 August 2026 — 5,587 subscribers10 August 2026 — 5,492 subscribers13 August 2026 — 5,456 subscribers16 August 2026 — 5,372 subscribers19 August 2026 — 5,088 subscribers23 August 2026 — 5,050 subscribers26 August 2026 — 5,028 subscribers29 August 2026 — 5,013 subscribers1 September 2026 — 4,951 subscribers4 September 2026 — 4,843 subscribers9 September 2026 — 4,831 subscribers13 September 2026 — 4,801 subscribers17 September 2026 — 4,767 subscribers26 September 2026 — 4,415 subscribers5 October 2026 — 3,781 subscribers11 October 2026 — 3,379 subscribers14 October 2026 — 3,186 subscribers17 October 2026 — 3,012 subscribers20 October 2026 — 2,892 subscribers23 October 2026 — 2,778 subscribers26 October 2026 — 2,590 subscribers29 October 2026 — 2,513 subscribers2 November 2026 — 2,382 subscribers5 November 2026 — 2,381 subscribers7 November 2026 — 2,079 subscribers12 November 2026 — 1,316 subscribers7 August 202612 November 2026
27 measurements spanning 97 days, net -4,271. 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 675–6,228 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
12 Nov 2026, 01:451,316-763
7 Nov 2026, 22:192,079-302
5 Nov 2026, 01:292,381-1
2 Nov 2026, 02:492,382-131
29 Oct 2026, 17:302,513-77
26 Oct 2026, 18:292,590-188
23 Oct 2026, 08:112,778-114
20 Oct 2026, 07:352,892-120
17 Oct 2026, 09:553,012-174
14 Oct 2026, 09:573,186-193
11 Oct 2026, 05:373,379-402
5 Oct 2026, 02:203,781-634
26 Sept 2026, 08:584,415-352
17 Sept 2026, 06:164,767-34
13 Sept 2026, 05:014,801-30
9 Sept 2026, 15:214,831-12
4 Sept 2026, 00:574,843-108
1 Sept 2026, 02:064,951-62
29 Aug 2026, 03:085,013-15
26 Aug 2026, 08:385,028first reading

Engagement

21 posts held, back to 23 May 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 8 pages 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 21 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 15s
Average length
2m 08s

Measured directly from 2 videos 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

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.0%

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

Measured over the 21 most recent posts we hold, published 23 May 2026 to 11 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

11 Aug 2026, 14:16 UTC16 viewsread 12 August 2026
Photo

【8月12日 17点整 LPL EDG vs AL】 数据初盘开出全局获胜:[email protected]/[email protected],机构更倾向于AL的绝对优势。AL暂以6胜2负、+8净胜分高居登峰组第3位,整体表现极具统治力,前中期在Tarzan的带节奏下野区与线上联动紧密,前中期节奏推进高效且压迫感十足。EDG则状态低迷,目前以0胜8负、-15净胜分惨遭登峰组垫底,队伍在前中期经常节奏掉档,中后期团战决策与战术执行力频繁脱节。两队近期交手AL多以压倒性优势获胜,阵容弹性与英雄池深度上AL优势极其显著。面对一胜难求的EDG,综合分析本场看好AL凭借强劲的前中实力与极佳的竞技状态轻松拿下胜利。 首局一血:[email protected] 首局击杀让分:[email protected] 首局比赛时间大小:小[email protected]

9 Aug 2026, 14:21 UTC30 viewsread 12 August 2026
Photo

【8月9日 15点整 LPL IG vs 苏州LNG】 数据初盘开出全局获胜:[email protected]/苏州[email protected],机构更倾向于IG优势。LPL中国职业联赛第三赛段涅槃组,IG暂以2胜1负排名涅槃组第2位,队伍状态良好,上单TheShy在涅槃组展现极强个人能力,两场BO3贡献四次单杀,被冠以涅槃单杀王称号。LNG暂以0胜2负排名涅槃组第4位,净胜场-4,开季至今尚未取得大场胜利,整体表现持续低迷。两队近期在8月2日有过一次直接交锋,IG以2-0横扫LNG,两局比赛TheShy连拿两局MVP,上路sheer被完全压制,打野Wei在野区对位中也明显优于Weiwei。面对LNG时TheShy无论是线上单杀还是团战收割都展现碾压级表现。综合分析本场看好IG延续对LNG的压制节奏再下一城。 首局一血:[email protected] 地图总数大小:小[email protected] 正确地图比分:[email protected]

6 Aug 2026, 13:48 UTC54 viewsread 12 August 2026
Photo

【8月6日 15点整 LPL LGD vs TT】 数据初盘开出全局获胜:[email protected]/[email protected],机构倾向TT稍占优势。LPL中国职业联赛第三赛段登峰组,LGD暂以1胜4负排名第5位,净胜场-4,本赛季唯一一胜来自对阵EDG,面对其他登峰组对手时仍难求一胜。TT暂以1胜5负排名第7位,净胜场-3,同样仅从EDG身上拿到唯一大场胜利。两队目前同处登峰组下游,EDG/LGD/TT三支通过骑士之路晋级的队伍在面对老登峰组队伍时至今大场全败,整体实力与登峰组强队存在明显差距。双方近3次交手LGD完胜,整体实力占优。综合分析本场看好LGD犯错更少拿下TT。 首局击杀让分:[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

4 Aug 2026, 14:44 UTC63 viewsread 12 August 2026
Photo

【8月5日 17点整 LPL 北京JDG vs LGD】 数据初盘开出全局获胜:北京[email protected]/[email protected],机构倾向JDG优势明显。LPL中国职业联赛第三赛段登峰组,JDG暂以1胜4负排名登峰组第6位,净胜场-3,近期整体状态低迷,但上一场面对强敌BLG虽有失利,队伍在部分对局中仍展现出一定韧性,整体硬实力与运营底蕴仍不容低估。LGD同样以1胜4负排名登峰组第5位,净胜场-4,战绩与JDG持平,但队伍打法极度依赖野区节奏,面对中上游队伍时稳定性不足,整体表现欠缺持续性。两队近四次交手JDG取得全胜,近年交锋占据压倒性优势,综合分析本场看好JDG拿下LGD止住颓势。 首局击杀让分:北京[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

1 Aug 2026, 13:57 UTC81 viewsread 12 August 2026
Photo

【8月2日 15点整 LPL TT vs 西安WE】 数据初盘开出全局获胜:[email protected]/西安[email protected],机构倾向西安WE优势。LPL 中国职业联赛第三赛段,TT暂时1胜3负登峰组排名第6,队伍前期对线相对较弱,状态欠佳,整体表现未如理想。WE暂时3胜1负登峰组排名第3,已斩获三连胜,野辅联动紧密,团队配合默契,韧性十足,发挥出色。两队近四场交锋西安WE获全胜,近年实力碾压对手,综合分析本场看好西安WE继续连胜节奏。 首局击杀让分:西安[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

31 Jul 2026, 13:37 UTC81 viewsread 12 August 2026
Photo

【8月1日 15点整 LPL AL vs TT】 数据初盘开出全局获胜:[email protected]/[email protected],机构倾向AL优势。LPL 中国职业联赛第三赛段,AL暂时2胜1负登峰组排名第3,队伍中野联动紧密,配合默契,韧性十足,整体表现出色。TT暂时1胜2负登峰组排名第5,早前遭受两连败,上一场2-0击败EDG,状态有所回暖。两队近五场交锋AL获全胜,小局未失一分,近年实力碾压对手,综合分析本场看好AL轻松取胜。 首局击杀让分:[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

25 Jul 2026, 14:50 UTC128 viewsread 12 August 2026
Photo

【7月26日 15点整 LPL 苏州LNG vs 深圳NIP】 数据初盘开出全局获胜:苏州[email protected]/深圳[email protected],机构倾向深圳NIP优势。LPL 中国职业联赛第三赛段,LNG上赛段骑士之路0-3不敌WE无缘淘汰赛,队伍运营能力较弱,整体表现未如理想。NIP上赛段同样在骑士之路被EDG击败无缘淘汰赛,队伍联动性有所下降,状态回落。两队近五场交锋NIP以4胜1负占优,近年实力略胜一筹,另加主场之利,综合分析本场看好深圳NIP获胜。 首局击杀让分:深圳[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

22 Jul 2026, 13:03 UTC134 views1 reactionsread 12 August 2026
Photo

【7月24日 15点整 LPL AL vs LGD】 数据初盘开出全局获胜:[email protected]/[email protected],机构倾向AL优势。LPL 中国职业联赛第三赛段,AL整体水平相对较高,队伍配合默契,表现相对稳定。LGD 上赛段常规赛在涅槃组3胜2负排名第3,运营能力较弱,状态欠佳,整体表现未如理想。两队近十局交锋AL获全胜,整体实力更胜一筹,综合分析本场看好AL轻松取胜。 首局击杀让分:[email protected] 首局击杀总数:小[email protected] 首局比赛时间:小[email protected]

❤1

22 Jul 2026, 12:59 UTC114 viewsread 12 August 2026
Photo

【7月23日 17点整 LPL 北京JDG vs AL】 数据初盘开出全局获胜:北京[email protected]/[email protected],机构倾向AL优势。LPL 中国职业联赛第三赛段,JDG上赛段组内赛9胜5负登峰组排名第2,运营能力有所提升,战队今年进步较大,愈战愈勇。AL上赛段8胜6负登峰组排名第4,近期电竞世界杯状态欠佳,整体表现未如理想。两队近十场交锋JDG以7胜3负占优,整体实力略胜一筹,综合分析本场看好北京JDG获胜。 首局击杀让分:北京[email protected] 首局击杀总数:大[email protected] 首局比赛时间:大[email protected]

14 Jul 2026, 15:25 UTC173 viewsread 12 August 2026
Photo

7月15日 17点整 EWC Gen.G vs Karmine Corp】 Gen.G作为LCK顶级强队,整体实力和团队运营能力均处于世界一流水准,选手个人能力突出,中后期团战执行力极强,面对实力稍逊的对手往往能够迅速掌控比赛节奏。Karmine Corp虽具备一定冲击力,但在硬实力、赛事经验以及运营细节方面与Gen.G仍存在明显差距。揭幕战对于Gen.G而言也是展示冠军竞争力的绝佳机会,势必全力以赴,因此本场更看好Gen.G轻松取胜。 首局击杀让分:[email protected] 首局击杀总大小:小[email protected] 首局比赛时间:小[email protected]

2 Jul 2026, 13:31 UTC287 viewsread 12 August 2026
Photo

LCK发布常规赛第三、四轮及季后赛赛程表:7月29日正式开赛 7月29日起,比赛将进入更加激烈的阶段,各支队伍将分别被划分至Legend组和Rise组。🔥 常规赛结束后,Legend组前四名将直接晋级季后赛;而Legend组第5名与Rise组前三名将获得季后赛入围赛资格。

2 Jul 2026, 13:31 UTC248 viewsread 12 August 2026
Photo

Kespa杯赛程:HLE和T1、GEN和DK同组,GEN前两战HLE和T1 其中GEN、DK、NS、DNS、KRX同分在A组,HLE、T1、BRO、BFX、KT分在B组。小组前四进入下一阶段。小组赛阶段各队将只会对阵另一组的队伍。

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

Mentions

Named by 7 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“英雄联盟 LPL KPL 电竞赛事推单” (@obdjss), 1,316 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/obdjss.

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.