无盲流水 1-3-6-12-24-36-开卡至今 今天加一车,晚上发车,周五左右回

Channel
大鲨鱼权威查档|@bgshark
@bgshark03
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
14,519subscribers
+653 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001374798124 |
|---|---|
| Type | Channel |
| Usernames | @bgshark03 @bgshark777 |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/bgshark03 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 14:18 | 14,519 | +40 |
| 17 Aug 2026, 17:28 | 14,479 | no change |
| 17 Aug 2026, 12:36 | 14,479 | +27 |
| 16 Aug 2026, 16:14 | 14,452 | +39 |
| 16 Aug 2026, 05:43 | 14,413 | no change |
| 15 Aug 2026, 00:48 | 14,413 | +28 |
| 14 Aug 2026, 14:55 | 14,385 | +44 |
| 13 Aug 2026, 16:28 | 14,341 | +9 |
| 13 Aug 2026, 08:52 | 14,332 | +61 |
| 12 Aug 2026, 15:04 | 14,271 | +10 |
| 12 Aug 2026, 06:32 | 14,261 | +112 |
| 11 Aug 2026, 12:53 | 14,149 | +43 |
| 11 Aug 2026, 03:31 | 14,106 | +105 |
| 10 Aug 2026, 12:26 | 14,001 | +48 |
| 10 Aug 2026, 00:30 | 13,953 | +59 |
| 9 Aug 2026, 12:34 | 13,894 | +28 |
| 9 Aug 2026, 03:32 | 13,866 | first reading |
Engagement
49 posts held, back to 3 August 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 17 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.00%
- avg views ÷ 14,519 subscribers
- Avg views / post
- 435
- 49 posts measured
- Reaction rate
- 0.268%
- reactions ÷ views · ER floor
- Posts in window
- 49
- of 49 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 16 of 49 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 August 2026 |
|---|---|
| Posts held | 49 (3 August 2026 – 18 August 2026) |
| Views total | 21,335 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Aug 2026, 06:54 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.
What this channel posts
- Video runtime
- 38s
- Average length
- 38s
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
19 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 68.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 68.4% | |
| ❤ | 6 | 31.6% |
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 16 of the 49 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 49 most recent posts we hold, published 3 August 2026 to 18 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
交管12123 名下车 ❤️❤️❤️ 回单 备案驾驶证+名下车辆+车辆状态+违章(有就给) 注意‼️查空给图一样收费 提供:大头+身份证号+手机号
⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ ⚡️点我查看所有业务模版⚡️ ⚡️点我查看所有业务模版⚡️ ⚡️点我查看所有业务模版⚡️ 💫💫💫💫💫💫💫💫💫 ——————————————————— 2026.8月所有业务正常.公群上押交易保障 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
👍1
移动精准定位 开始时间上午9点---结束时间凌晨2点 不需要排队平均每一单5分钟 目前只出移动(联通电信陆续开放) 出来的全部实时位置 假一单赔一万人民币 历史遗留位置一个赔五千人民币 失败会告知多久得历史位置 报单不用说测试直接埋雷即可 报单之前确定手机是否开机 报单之前确定是否携号转网
电商后台预留历史地址 图一: 美团后台预留历史 ❤️❤️❤️ 图二: 拼多多后台预留历史 ❤️❤️❤️ 图三:淘宝后台预留历史❤️❤️❤️ 没有时间显示,只出历史地址, 介意勿报,出单不扯皮
哈啰所有出行记录 ❤️❤️❤️ 录屏注册至今所有出行记录 截屏注册至今所有常用地址 报单提供:个户+哈啰账号(手机号) (账号可以在哈啰app上找回密码查看)
国政名下 源头出单价格随便开❤️❤️ 提供名字身份证大头 出名下所有证件有多少算多少 源头出单价格随便开
民政婚姻带结离 ❤️❤️❤️ 正常当天隔天回最稳的板子。 目前最真最稳无遗漏民政局版本婚姻,空单的是民政局没有登记, 没有离婚记录但离婚的是没有过民政局系统,法院判离。 工作日当天15.00前报单的当天回,之后隔天回 ——————————————————————————— 其他业务模板价格和回单时间 看频道置顶
飞火监控开 ❤️❤️❤️❤️ 当天或者往后几天只要购买飞机火车高铁记录都可以监控到 提供身份证报单挂系统 出票了通知你算成交 默认挂15天 被监控人购票后已选座位都可以看到 抓人一抓一个准 一手资源 批量价优 好东西不常有 强推
人行征信报告开 ❤️❤️❤️❤️ 纯人民银行出品 去人行征信打出来什么样 我回出来就是什么样 非小贷公司 律所提取版本 查背景 查对象 查合作伙伴必备单品 工作日当天隔天回 私信看板 同行代理拿优势
公户银行验资金额 同行全网最低价 ❤️❤️❤️❤️一笔交易金额 全银行通杀 四大 九商 地方银行 合作社 全部工作日内30分钟内回单 例如 抖音平台开企业蓝v 公户验证 平台向公户打款 报给我公司名字和提交的打款账户 30分钟以内就能出金额 任何平台 任何银行 都可以 只要是查款验资 一律30分钟内出金额
👍1
全国航班记录,未起飞的也有 一年记录 极少遗漏 ❤️❤️❤️❤️ 同行人+❤️❤️❤️ 源头收单 同行代理问价 板子问我拿
Showing the 12 most recent of 49 posts we hold for @bgshark03. 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
Citation-graph rank — 41,915 of 1,549,704entries 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.
Mentions
Named by 4 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@bgshark03 named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 16 August 2026 – 16 August 2026
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 August 2026 — this entry's latest reading, not the date you are reading this.
“大鲨鱼权威查档|@bgshark” (@bgshark03), 14,519 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/bgshark03.
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.