Telegram RegisterThe public register of Telegram
Telegram profile photo for (官方)球速体育频道

Channel

(官方)球速体育频道

@qswj4

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

18,162subscribers

-3,375 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-1003152585530
TypeChannel
Username@qswj4
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/qswj4

Topic

Gambling & betting — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

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 word for word on 1 other registered channel. They sit inside a group of 6 channels that share the same post bodies 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qswj4/450 · this entry5 Aug 2026, 12:23 UTC@ty182_4/4595 Aug 2026, 12:24 UTC1.00under a minute
@ty182_4/4585 Aug 2026, 09:52 UTC@qswj4/449 · this entry5 Aug 2026, 09:53 UTC0.88under a minute
@ty182_4/4617 Aug 2026, 06:31 UTC@qswj4/452 · this entry7 Aug 2026, 06:31 UTC0.88under a minute
@ty182_4/4606 Aug 2026, 06:29 UTC@qswj4/451 · this entry6 Aug 2026, 06:30 UTC0.87under a minute
@ty182_4/45230 Jul 2026, 06:43 UTC@qswj4/444 · this entry30 Jul 2026, 06:43 UTC0.86under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ty182_45 (5/5 hand-verifiable sample passed)0.90under a minute@ty182_4 (41)

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. 2 of the 4 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 19 comparable posts for this entry, running 13 July 2026 to 7 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).

Across the whole group of 6, the earliest publisher we hold is @Y30022. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 5 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

18,16221,53719,849.56 August 2026 — 21,537 subscribers6 August 2026 — 21,536 subscribers7 August 2026 — 21,499 subscribers9 August 2026 — 21,474 subscribers10 August 2026 — 21,430 subscribers10 August 2026 — 21,417 subscribers12 August 2026 — 21,374 subscribers13 August 2026 — 21,368 subscribers14 August 2026 — 21,334 subscribers15 August 2026 — 21,259 subscribers17 August 2026 — 21,135 subscribers18 August 2026 — 21,078 subscribers19 August 2026 — 21,039 subscribers20 August 2026 — 21,008 subscribers21 August 2026 — 20,979 subscribers22 August 2026 — 20,886 subscribers23 August 2026 — 20,819 subscribers25 August 2026 — 20,768 subscribers26 August 2026 — 20,743 subscribers27 August 2026 — 20,729 subscribers28 August 2026 — 20,672 subscribers29 August 2026 — 20,590 subscribers30 August 2026 — 20,525 subscribers31 August 2026 — 20,495 subscribers1 September 2026 — 20,465 subscribers2 September 2026 — 20,438 subscribers3 September 2026 — 20,392 subscribers4 September 2026 — 20,342 subscribers8 September 2026 — 20,011 subscribers11 September 2026 — 19,560 subscribers13 September 2026 — 19,143 subscribers14 September 2026 — 18,905 subscribers16 September 2026 — 18,551 subscribers18 September 2026 — 18,162 subscribers6 August 202618 September 2026
34 measurements spanning 43 days, net -3,375. 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 17,656–22,043 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 20:5918,162-389
16 Sept 2026, 09:3718,551-354
14 Sept 2026, 15:5618,905-238
13 Sept 2026, 04:3819,143-417
11 Sept 2026, 03:2119,560-451
8 Sept 2026, 04:2020,011-331
4 Sept 2026, 21:3620,342-50
3 Sept 2026, 09:1420,392-46
2 Sept 2026, 06:1820,438-27
1 Sept 2026, 05:1320,465-30
31 Aug 2026, 03:1720,495-30
30 Aug 2026, 05:3420,525-65
29 Aug 2026, 01:5420,590-82
28 Aug 2026, 03:3720,672-57
27 Aug 2026, 05:1620,729-14
26 Aug 2026, 06:5720,743-25
25 Aug 2026, 04:0620,768-51
23 Aug 2026, 20:0720,819-67
22 Aug 2026, 07:4620,886-93
21 Aug 2026, 01:4420,979first reading

Engagement

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

ERR · 30 days
6.88%
avg views ÷ 18,162 subscribers
Avg views / post
1,250
11 posts measured
Reaction rate
0.072%
reactions ÷ views · ER floor
Posts in window
11
of 41 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. It is computed over the 2 of 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held41 (13 July 20262 September 2026)
Views total13,736
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 00:16 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.

Reaction mix

4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
👍125.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 4 of the 41 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 41 most recent posts we hold, published 13 July 2026 to 2 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.

Recent posts

2 Sept 2026, 06:56 UTC≈1,080 viewsread 3 September 2026

日职联 18:00 大阪樱花 受平/半 柏太阳神 推荐:柏太阳神-0/0.5 日职联 18:00 千叶市原 受半球 冈山绿雉 推荐:冈山绿雉-0.5 日职联 18:00 町田泽维亚 半球 川崎前锋 推荐:町田泽维亚-0.5 日职联 18:00 水户蜀葵 受半球 鹿岛鹿角 推荐:鹿岛鹿角-0.5 日职联 18:00 广岛三箭 一球 名古屋鲸八 推荐:广岛三箭-1 日职联 18:00 东京绿茵 受半球 神户胜利船 推荐:神户胜利船-0.5 日职联 18:00 长崎成功丸 受平/半 大阪钢巴 推荐:大阪钢巴-0/0.5 日职联 18:00 横滨水手 平/半 京都不死鸟 推荐:横滨水手-0/0.5 日职联 18:00 清水鼓动 受半球 FC东京 推荐:FC东京-0.5 丹麦超 2:00 奥胡斯 受平/半 中日德兰 推荐:中日德兰-0/0.5 比甲 2:30 圣图尔登 受半球 圣吉罗斯 推荐:圣吉罗斯-0.5 瑞士超

1 Sept 2026, 06:23 UTC876 viewsread 3 September 2026

冰岛超 1:15 KR雷克雅未克 受平/半 维京古 推荐:KR雷克雅未克-0/0.5 沙特联 2:00 利雅得新月 半/一 吉达国民 推荐:利雅得新月-0.5/1 瑞士超 2:30 苏黎世 受一球 年轻人 推荐:年轻人-1 英冠 2:45 林肯城 平/半 布莱克本 推荐:林肯城 -0/0.5 英冠 2:45 朴茨茅斯 平/半 德比郡 推荐:朴茨茅斯-0/0.5 英冠 2:45 普雷斯顿 平手 布里斯托城 推荐:普雷斯顿-0 英冠 2:45 谢菲尔德联队 半/一 博尔顿 推荐:谢菲尔德联队-0.5/1 英冠 2:45 西汉姆联 半球 狼队 推荐:西汉姆联-0.5 英冠 2:45 斯旺西 半球 沃特福德 推荐:斯旺西 -0.5 英甲 2:45 布拉德福德 半/一 剑桥联 推荐:布拉德福德-0.5/1 英甲 2:45 布罗姆利 平手 莱顿东方 推荐:布罗姆利-0 英甲 2:45 唐卡斯特 半球 诺茨郡 推荐:唐卡

31 Aug 2026, 07:55 UTC≈1,280 viewsread 3 September 2026

芬超 0:00 奥卢 平/半 塞伊奈约基 推荐:奥卢-0/0.5 芬超 0:00 格尼斯坦 半球 TPS土尔库 推荐:格尼斯坦-0.5 芬超 0:00 埃尔维斯 受半球 赫尔辛基 推荐:赫尔辛基-0.5 芬超 0:00 图尔库国际 平/半 古比斯 推荐:图尔库国际-0/0.5 芬超 0:00 玛丽港 平/半 雅罗 推荐:玛丽港 -0/0.5 芬超 0:00 VPS瓦萨 平/半 拉赫蒂 推荐:VPS瓦萨-0/0.5 意甲 0:30 莱切 受半/一 罗马 推荐:罗马-0.5/1 希腊超 0:30 莱瓦费科斯 受半/一 帕纳辛纳科斯 推荐:帕纳辛纳科斯-0.5/1 瑞典超 1:00 尤尔加登 一球 米亚尔比 推荐:尤尔加登-1 瑞典超 1:00 哥德堡盖斯 半/一 布洛马波卡纳 推荐:哥德堡盖斯-0/0.5 瑞典超 1:00 天狼星 半球 马尔默 推荐:天狼星-0.5 丹麦超 1:00 哥本哈根 一/球半 桑德捷

30 Aug 2026, 10:20 UTC≈1,570 viewsread 3 September 2026

葡超 22:30 葡萄牙国民 平/半 阿马多拉 推荐:葡萄牙国民 -0/0.5 俄超 22:30 莫斯科斯巴达 一/球半 奥伦堡加索维 推荐:莫斯科斯巴达 -1/1.5 瑞士超 22:30 圣加仑 半/一 图恩 推荐:圣加仑 -0.5/1 瑞典超 22:30 哥德堡 一球 奥尔格里特 推荐:哥德堡 -1 荷甲 22:45 特尔斯达 受一球 阿贾克斯 推荐:阿贾克斯 -1 荷乙 22:45 芬洛 平手 埃门 推荐:芬洛 -0 西甲 23:00 皇家马德里 两球 马拉加 推荐:皇家马德里 -2 西乙 23:00 安道尔FC 平/半 埃瓦尔 推荐:安道尔 -0/0.5 法甲 23:15 雷恩 一/球半 勒芒 推荐:雷恩 -1/1.5 英超 23:30 曼彻斯特联 一/球半 伊普斯维奇 推荐:曼彻斯特联 -1/1.5 德甲 23:30 奥格斯堡 平/半 沙尔克04 推荐:奥格斯堡 -0/0.5 土超 0:00 埃于

29 Aug 2026, 09:33 UTC967 views1 reactionsread 3 September 2026

瑞典超 23:30 哈尔姆斯塔德 受平/半 卡尔马 推荐:卡尔马 -0/0.5 瑞士超 0:00 洛桑 半球 苏黎世 推荐:洛桑 -0.5 英超 0:30 托特纳姆热刺 平/半 纽卡斯尔联 推荐:托特纳姆热刺 -0/0.5 德甲 0:30 多特蒙德 球半 汉堡 推荐:多特蒙德 -1.5 意甲 0:30 佛罗伦萨 半/一 弗洛西诺尼 推荐:佛罗伦萨 -0.5/1 意甲 0:30 蒙扎 受平/半 乌迪内斯 推荐:乌迪内斯 -0/0.5 意甲 0:30 萨索洛 平/半 都灵 推荐:都灵 +0/0.5 荷甲 0:45 阿尔克马尔 球半 前进之鹰 推荐:阿尔克马尔 -1.5 西甲 1:00 皇家社会 半球 西班牙人 推荐:皇家社会 -0.5 西乙 1:00 阿尔巴塞特 平/半 皇家奥维耶多 推荐:阿尔巴塞特 -0/0.5 西乙 1:00 莱加内斯 半球 埃登斯 推荐:莱加内斯 -0.5 俄超 1:00 格罗兹尼特里克

👍1

28 Aug 2026, 06:02 UTC≈1,060 viewsread 3 September 2026

韩K2联 18:30 安山小绿人 受一/球半 大邱FC 推荐:大邱-1/1.5 韩K2联 18:30 全南天龙 平/半 天安城 推荐:全南天龙-0/0.5 中超 19:35 大连英博 受平/半 北京国安 推荐:北京国安-0/0.5 中超 19:35 上海申花 半球 山东泰山 推荐:上海申花-0.5 中超 20:00 深圳新鹏城 受半球 上海海港 推荐:上海海港-0.5 俄超 23:00 阿克伦陶里亚蒂 受半/一 莫斯科中央陆军 推荐:莫斯科中央陆军-0.5/1 德乙 0:30 波鸿 半/一 奥斯纳布鲁克 推荐:波鸿-0.5/1 德乙 0:30 布伦瑞克 平手 柏林赫塔 推荐:布伦瑞克-0 西甲 1:00 桑坦德竞技 平/半 埃尔切 推荐:桑坦德竞技-0/0.5 丹麦超 1:00 霍森斯 受半/一 维堡 推荐:维堡-0.5/1 荷甲 2:00 格罗宁根 一/球半 福图纳锡塔德 推荐:格罗宁根-1/1.5 法乙

26 Aug 2026, 07:23 UTC≈1,490 viewsread 3 September 2026

韩K联 18:30 FC安养 受平/半 仁川联队 推荐:仁川联队-0/0.5 韩K联 18:30 大田市民 平/半 蔚山HD 推荐:大田市民-0/0.5 韩K联 18:30 江原FC 一球 光州FC 推荐:江原-1 东南锦 21:00 越南 半/一 泰国 推荐:越南-0.5/1 挪甲 0:00 斯托曼 半球 诺霍斯 推荐:斯托曼-0.5 欧协联 0:45 维也纳快速 一球 哈茨 推荐:维也纳快速-1 挪甲 1:00 阿萨纳 受平/半 利恩 推荐:利恩-0/0.5 挪甲 1:00 海于格松 一球 埃格尔森德 推荐:海于格松-1 挪甲 1:00 莫斯 平手 松达尔 推荐:莫斯+0 挪甲 1:00 奥德 平手 康斯文格 推荐:奥德+0 挪甲 1:00 斯塔贝克 球半 兰黑姆 推荐:斯塔贝克-1.5 挪甲 1:00 斯托姆加斯特 球半/两 禾特 推荐:斯托姆加斯特-1.5/2 埃及超 1:

25 Aug 2026, 05:59 UTC≈1,800 views1 reactionsread 3 September 2026

澳足总 17:30 昆士兰狮队 球半 北鹰阳光 推荐:昆士兰狮队-1.5 韩K联 18:30 金泉尚武 受平/半 全北现代 推荐:全北现代-0/0.5 韩K联 18:30 济州SK 平/半 浦项制铁 推荐:浦项制铁+0/0.5 韩K联 18:30 FC首尔 一球 富川FC 推荐:首尔-1 欧冠杯 0:45 萨巴赫 半/一 贝尔谢巴夏普尔 推荐:萨巴赫-0.5/1 瑞典甲 1:00 奥雷布洛 平手 瓦尔贝里 推荐:奥雷布洛-0 瑞典甲 1:00 奥斯达 一球 松兹瓦尔 推荐:奥斯达-1 英联赛 2:00 卡迪夫城 平/半 诺维奇 推荐:卡迪夫城-0/0.5 英锦赛 2:00 布里斯托流浪 半球 切尔西U21 推荐:布里斯托流浪-0.5 英联赛 2:30 唐卡斯特 受半/一 米德尔斯堡 推荐:米德尔斯堡-0.5/1 英联赛 2:45 巴恩斯利 一球 克鲁 推荐:巴恩斯利-1 英联赛 2:45 布莱克本 平手 谢

1

24 Aug 2026, 09:06 UTC≈1,680 viewsread 3 September 2026

罗甲 23:30 博托沙尼 半/一 FK米耶尔库雷亚丘克 推荐:博托沙尼-0.5/1 德国杯 0:00 艾尔格里尼克(中) 受两球 沃尔夫斯堡 推荐:沃尔夫斯堡-2 德国杯 0:00 SC维尔 受一球 汉堡 推荐:汉堡-1 德国杯 0:00 维尔茨堡踢球者 受球半 科隆 推荐:科隆-1.5 保甲 0:00 华拉特莎 受半球 普罗夫迪夫博特 推荐:普罗夫迪夫博特-0.5 意甲 0:30 博洛尼亚 半球 拉齐奥 推荐:博洛尼亚-0.5 瑞典超 1:00 马尔默 平手 尤尔加登 推荐:马尔默+0 丹麦超 1:00 布隆德比 一/球半 锡尔克堡 推荐:布隆德比-1/1.5 西甲 1:30 奥萨苏纳 半/一 莱万特 推荐:奥萨苏纳-0.5/1 俄超 1:30 加里宁格勒巴蒂卡 半球 喀山红宝石 推荐:加里宁格勒巴蒂卡-0.5 保甲 2:15 普罗夫迪夫火车头 受平/半 埃尔塔 推荐:埃尔塔-0/0.5 土超 2:30

23 Aug 2026, 05:54 UTC923 viewsread 3 September 2026

英超 21:00 布莱顿 平/半 阿斯顿维拉 推荐:布莱顿 -0/0.5 英超 21:00 曼彻斯特城 一/球半 伯恩茅斯 推荐:曼彻斯特城 -1/1.5 德国杯 21:30 耶拿 受一球 达姆施塔特 推荐:达姆施塔特 -1 德国杯 21:30 布伦瑞克 受半球 柏林联合 推荐:柏林联合 -0.5 丹麦超 22:00 霍森斯 平手 利恩比 推荐:霍森斯 -0 俄超 22:30 马哈奇卡拉 受半球 克拉斯诺达尔 推荐:克拉斯诺达尔 -0.5 瑞典超 22:30 哈马比 一/球半 哥德堡盖斯 推荐:哈马比 -1/1.5 荷甲 22:45 坎布尔 受球半 费耶诺德 推荐:费耶诺德 -0.6 荷乙 22:45 芬洛 受平/半 格拉夫夏普 推荐:格拉夫夏普 -0/0.5 西甲 23:00 马德里竞技 半球 比利亚雷亚尔 推荐:马德里竞技 -0.5 西乙 23:00 埃瓦尔 平/半 巴拉多利德 推荐:巴拉多利德 +0/0

22 Aug 2026, 06:54 UTC≈1,010 viewsread 3 September 2026

英超 22:00 埃弗顿 平/半 水晶宫 推荐:埃弗顿 -0/0.5 英超 22:00 诺丁汉森林 平/半 利兹联 推荐:诺丁汉森林 -0/0.5 英冠 22:00 普雷斯顿 受平/一 狼队 推荐:狼队 -0.5/1 英冠 22:00 女王公园巡游者 半球 博尔顿 推荐:女王公园巡游者 -0.5 芬超 22:00 埃尔维斯 平/半 VPS瓦萨 推荐:埃尔维斯 -0/0.5 芬超 22:00 雅罗 受平/半 奥卢 推荐:奥卢 -0/0.5 荷乙 22:30 布雷达 球半/两 阿贾克斯青年队 推荐:布雷达 -1.5/2 西甲 23:00 毕尔巴鄂竞技 半/一 塞维利亚 推荐:毕尔巴鄂竞技 -0.5/1 西乙 23:00 皇家奥维耶多 半球 莱加内斯 推荐:皇家奥维耶多 -0.5 法甲 23:15 朗斯 一球 欧塞尔 推荐:朗斯 -1 波兰超 23:30 皮亚斯特 受平/半 华沙莱吉亚 推荐:华沙莱吉亚 -0/0.

21 Aug 2026, 05:54 UTC936 viewsread 3 September 2026

日职联 18:00 柏太阳神 半/一 长崎成功丸 推荐:柏太阳神 0.5/1 日职联 18:30 FC东京 一球 千叶市原 推荐:FC东京 -1 芬甲 23:30 哈卡 球半/两 SJK学院 推荐:哈卡 -1.5/2 芬超 0:00 塞伊奈约基 平手 拉赫蒂 推荐:塞伊奈约基 +0 芬甲 0:00 PK-35海辛基 一球 查普斯 推荐:PK-35海辛基 -1 瑞典超 1:00 天狼星 半/一 赫根 推荐:天狼星 0.5/1 秘鲁甲秋 1:00 卡哈马卡俱乐部 平/半 格劳竞技 推荐:卡哈马卡俱乐部 -0/0.5 奥甲 1:30 里德 平/半 格拉茨AK 推荐:里德 -0/0.5 阿甲 1:30 阿尔多斯维 受平/半 圣塔菲联 推荐:圣塔菲联 -0/0.5 法乙 2:00 布洛涅 受平/半 红星 推荐:红星 -0/0.5 法乙 2:00 克莱蒙 受平/半 第戎 推荐:第戎 -0/0.5 法乙 2:00 波城

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 49 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“(官方)球速体育频道” (@qswj4), 18,162 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/qswj4.

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.