Channel
@speedyabc99955
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
527subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003724691684 |
|---|---|
| Type | Channel |
| Username | @speedyabc99955 |
| Created | Between 1 February 2026 and 29 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/speedyabc99955 |
Other / unclassifiable — 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 33% 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.
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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @Speedyabc3/7929 May 2026, 08:48 UTC | @speedyabc99955/73 · this entry29 May 2026, 08:48 UTC | 1.00 | under a minute |
| @Speedyabc3/10522 Jun 2026, 07:35 UTC | @speedyabc99955/100 · this entry22 Jun 2026, 07:36 UTC | 1.00 | 72 seconds |
| @Speedyabc3/1236 Jul 2026, 11:00 UTC | @speedyabc99955/118 · this entry6 Jul 2026, 11:02 UTC | 1.00 | 72 seconds |
| @speedyabc99955/119 · this entry6 Jul 2026, 12:02 UTC | @Speedyabc3/1246 Jul 2026, 12:04 UTC | 1.00 | 2 minutes |
| @Speedyabc3/1584 Aug 2026, 07:14 UTC | @speedyabc99955/155 · this entry4 Aug 2026, 07:16 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Speedyabc3 | 6 (5/6 hand-verifiable sample passed) | 1.00 | 72 seconds | @Speedyabc3 (5–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 5 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 29 May 2026 to 6 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.
Across the whole group of 2, the earliest publisher we hold is @Speedyabc3. 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 19:20 | 527 | -2 |
| 6 Aug 2026, 19:17 | 529 | first reading |
18 posts held, back to 29 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (29 May 2026 – 6 August 2026) |
| Views total | 92 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:17 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 18 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 29 May 2026 to 6 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.
来自速搜推荐 @SSOU 📢欧博假网 亚星假网 皇冠... 📢全国商k预订，游戏情趣真... 📢亚星私网/欧博私网/利博... 📢缅甸◉新闻曝光🌎 📢外围足球 世界杯足球 世... 📢盯射-旗袍 📢皇冠代理 皇冠体育 皇冠... 📢欧博假网 亚星假网 皇冠... 📢利博官网 利博代理 利博... 📢亚星包杀 欧博包杀 亚星... 📢战斗民族|火爆现场|美女... 📢科学·科普·气象·生物·... 📢亚星包杀 欧博包杀 亚星... 📢🔥听风的蚕|军事科技⚡... 📢欧博官网 亚星官网 皇冠... 👉流量互推规则介绍💥 以下是广告推荐 📢专业Telegram账号交易平台🔥热门社交媒体账号交易 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢💎 【8.cc】U投领导者 千万域名 百亿大盘 充值笔笔加赠3% ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 📢XX789🔞成人资源一站式导航 🇨🇳 简体中文包 ——————…
主推墨西哥短信，日发百万，内容不限，落地高效果棒✔️✔️✔️ Primarily promoting SMS to Mexico, sending millions of messages daily, with no content restrictions, high delivery rate and excellent results.👌👌👌 Welcome all Mr. Pan to consult and test. 欢迎各位盘总咨询测试 @SpeedyABC
骗子模仿，仔细甄别，被骗概不负责，认准唯一账号@SpeedyABC
#巴西 #RCS 游戏短信线路已经恢复，支持VIVO、TIM、CLARO等运营商，需要的老板可以下单安排
全球短信价格表 短信供应商 #菲律宾短信 #哥伦比亚短信 #印度短信 #墨西哥 各国家线路均有可卡发可直连！ BC-兼职-网赚-刷单-棋牌等均秒发秒到 https://t.me/SpeedyABC 你的专属客服，等你敲窗永不失联ID :@SpeedyABC 唯一账号，谨防上当受骗
🇮🇳提供热门的 #印度短信 路线! 每条印度短信路线都经过测试，稳定可靠，随时可用于您的营销活动。 ✔️ 最高转化率 ✔️最优价格 ✔️超大容量 ✉️适用于游戏、博彩、营销或一次性密码（OTP）应用 —————————————————— 😀销售业务咨询： @SpeedyABC
😃😃这个号是冒充的，唯一号@SpeedyABC
商品：#全球号码检测 📣商品介绍：-全球数据自助检测平台 提供独立后台、实时在线检测、账户余额通用，自助充值， 能筛选的项目：ws\\tg\\fb\\vk等社交软件、binance,bybit，Robinhood等交易所平台, 新增amazon，ins，microsoft，twitter邮箱检测，料子筛选，活跃天数，性别 年龄筛选，可开后台，提供免費的國家號段 等交易所软件 📱联系方式： @SpeedyABC 🏷频道：https://t.me/speedyabc99955
优势：通道0扣量，包料发送可保最低万10充值转化 注意事项 ①提前报备文案、发送数量 ②指定VT/VN运营商发送 —————————————————— 😀客服：@SpeedyABC
⚡️⚡️【全球数据自助检测平台】⚡️⚡️ 🍎24小时实时检测 源头稳定出🍎 🔼WS、Facebook、Telegranm、Line数据筛选 🔼Viber、Zalo、Botim、momo、imo数据筛选 🔼Skype、Snapchat、Signal数据筛选 🔼ios数据筛选、im过蓝、苹果安卓用户筛选 、RCS筛选 🔼全球领英(LinkedIn)、亚马逊（Amazon）、推特（Twitter）数据筛选 🔼全球Tiktok、Band、Kakao、VKontakte数据筛选 🔼全球Binance（币安）、OKX（欧意）、bybit、HTX（火币）等交易所数据筛选 🔼全球号码过空、互联网行为筛选、指定地区，运营商数据筛选 🔼 美国、欧洲、中东、越南、印度、印尼、香港、泰国、澳大利亚、菲律宾、尼日利亚、台湾、韩国、意大利、马来西亚、土耳其、加纳、巴西、日本、新西兰等海外国家 ‼️合…
来自速搜推荐 @SSOU 📢收藏片单局 📢欧博代理 亚星代理 欧博... 📢欧美精选 📢深夜精选局 📢币盘合约交易所精聊盘 📢2026世界杯 世界杯赛... 📢私藏片库局 📢足球下注 世界杯买球 世... 📢皇冠代理 皇冠足球 皇冠... 📢足球比赛 世界杯比赛 世... 📢电影解说🎬|精彩视频�... 📢东南亚狗仔队-热点新闻 📢电报低成本引流｜高质量增... 📢足球下注 世界杯买球 世... 📢亚星代理 欧博代理 亚星... 👉流量互推规则介绍💥 以下是广告推荐 ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 ✅南风数据全行业✅，sdk，DPI，106短信劫持，诚邀合作 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢💹567U时代火爆上线！招收玩家/代理，匿名开户，放心娱乐！ 📢 全网最全面、最便宜的自助引流服务 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员，即可在20
#巴基斯坦 JAZZ新通道 直连+卡发组合 全通 不需要加白内容 点击w500-600 要发bc短信DD我 @SpeedyABC
Showing the 12 most recent of 18 posts we hold for @speedyabc99955. 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.
Citation-graph rank — 289,830 of 1,084,084entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 30 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@speedyabc99955 named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“全球短信API” (@speedyabc99955), 527 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/speedyabc99955.
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.