Channel
@apsp1234
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry
346subscribers
-535 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002174345965 |
|---|---|
| Type | Channel |
| Username | @apsp1234 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/apsp1234 |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 50 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @apsp1234/1353 · this entry19 Jul 2026, 08:20 UTC | @OZBhongdan/1207219 Jul 2026, 09:28 UTC | 1.00 | 68 minutes |
| @OZBhongdan/1207319 Jul 2026, 10:37 UTC | @apsp1234/1355 · this entry19 Jul 2026, 11:00 UTC | 1.00 | 23 minutes |
| @OZBhongdan/1207419 Jul 2026, 11:00 UTC | @apsp1234/1356 · this entry19 Jul 2026, 12:34 UTC | 1.00 | 1.6 hours |
| @OZBhongdan/1207619 Jul 2026, 14:12 UTC | @apsp1234/1359 · this entry19 Jul 2026, 16:40 UTC | 1.00 | 2.5 hours |
| @OZBhongdan/1207719 Jul 2026, 15:29 UTC | @apsp1234/1360 · this entry19 Jul 2026, 17:05 UTC | 1.00 | 1.6 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @OZBhongdan | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.6 hours | @OZBhongdan (4–1) |
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. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 18 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.
Of the group of 50 channels, the one whose matching posts we hold earliest is @J9yaya. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 13 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.
This channel is in a group of 50 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 01:38 | 346 | -56 |
| 2 Nov 2026, 11:29 | 402 | -50 |
| 26 Oct 2026, 22:28 | 452 | -22 |
| 19 Oct 2026, 14:00 | 474 | -6 |
| 12 Oct 2026, 13:15 | 480 | -1 |
| 2 Oct 2026, 10:00 | 481 | +376 |
| 16 Sept 2026, 17:02 | 105 | -35 |
| 9 Sept 2026, 03:18 | 140 | -21 |
| 31 Aug 2026, 11:54 | 161 | -519 |
| 24 Aug 2026, 02:53 | 680 | -34 |
| 16 Aug 2026, 04:16 | 714 | -165 |
| 8 Aug 2026, 03:06 | 879 | -2 |
| 8 Aug 2026, 01:06 | 881 | no change |
| 7 Aug 2026, 20:13 | 881 | first reading |
20 posts held, back to 18 July 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
🔹🔸 频道多福利，狂欢大放送！🔹🔸 ❤️💛💚 以下彩金，可叠加领取！✨ 🌈 新人首存 100 送 38！👉 40％ 高返利！ ❇️ 星空体育：首存 500，立即送 88！ ❇️ 指定赛事负盈利 100% 返还，最高 1,888 元！ 🎁 星空专属福利域名： fun-new.com 🌈 注册【云博】专家平台 → 连结 星空体育 ❇️ 「无需充值」188 彩金 免费领取！ ❇️ 方案＆娱乐 一次满足，双重彩金加倍领取！ 🎁 云博平台福利 ➕ 娱乐官网福利⚡️⚡️ 🥰 双重彩金：https://goo.su/a7sz1 备用： https://my5353.com/yunbo 💥 专家方案免费，额外彩金狂领！
Telegram必备的搜索引擎，极搜JISOU帮你精准找到，想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6502688290
Telegram必备的搜索引擎，极搜JISOU帮你精准找到，想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6502688290
2026-07-20 08:00 秘鲁甲组联赛 阿里萨利马 v 万卡 足球 大 / 小 大 2.5 / 3 2026-07-20 08:30 玻利维亚甲组联赛 邦明 v 皇家托马亚波 足球 大 / 小 大 3 2026-07-20 09:30 美国MLS Next职业联赛 皇家君主 v 塔科马挑战 足球 大 / 小 小 3 / 3.5 三串一
世界杯2026(在加拿大、墨西哥 &美国) 西班牙 VS 阿根廷 07-20 03:00 (GMT+8) [滚球] 上半场大小 [欧洲盘] 小 0.5 @ 2.28 零比零 可以上车了
Photo, posted without a caption
2026-07-20 00:30 罗马尼亚甲组联赛 佩特罗鲁 v 布加勒斯特迪纳摩 足球 让球 布加勒斯特迪纳摩 -0.5 2026-07-20 08:00 秘鲁甲组联赛 阿里萨利马 v 万卡 足球 让球 阿里萨利马 -1 / 1.5 2026-07-20 03:00 世界杯2026(美加墨) 西班牙 v 阿根廷 足球 让球 阿根廷 +0 / 0.5 ------------------------------ 三串一
22:30 瑞典甲 埃尔夫斯堡+0.5 赫根-1 戴戈福斯+2 三串一
Telegram必备的搜索引擎，极搜JISOU帮你精准找到，想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6502688290
---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 瑞典超 23:00 队伍：埃尔夫斯堡-天狼星 推荐：埃尔夫斯堡（+0.5） 瑞典超 23:00 队伍：哈马比-代格福什 推荐：全场大（3/3.5） 瑞典超 23:00 队伍：哈尔姆斯塔德-赫根 推荐：赫根（-1） 芬兰超 23:30 队伍：查路-图尔库国际 推荐：全场大（2.5/3） 世界杯 05:00 队伍：西班牙-阿根廷 推荐：全场小（2/2.5） 波胆：1/0 0/0 1/1 角球：全场大（7.5） 三串一：赫根+西班牙+查路
瑞典超级联赛 埃尔夫斯堡 VS 天狼星 07-19 22:30 全场大小 [欧洲盘] 大 2.5/3 @ 1.83 玻利维亚甲级联赛 GV圣何塞 VS 最强者07-19 23:00 全场大小 [欧洲盘] 大 3 @ 1.92 【重仓雷霆回血单】 芬兰超级联赛 查路 VS 图尔库国际 07-19 23:30 全场让球 [欧洲盘] 查路 +0.5/1 @ 1.88 冰岛超级联赛 雷克雅未克 VS 斯塔尔南 07-20 00:00 角球大小 [欧洲盘] 大 12.5 @ 1.97 世界杯2026(在加拿大、墨西哥&美国) 07-20 03:00 西班牙 VS 阿根廷 冠军 [欧洲盘] 阿根廷 @ 2.33 波胆:2-2 1-2
Forwarded From 开云 爱游戏 华体会 乐鱼体育代理招商佣金55% [https://t.me/FAHAN10/2905] (Channel Help) 北京时间 2026年7月20日的美加墨世界杯冠军 07-20🔢:🔢 西班牙VS阿根廷
Showing the 12 most recent of 20 posts we hold for @apsp1234. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“🏅足球推荐（看置顶）丨NBA篮球推荐丨电竞体育丨赛事红单推荐🏆2026世界杯 yb” (@apsp1234), 346 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/apsp1234.
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.