Channel
@sdbg66
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2,297subscribers
-2 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003930188956 |
|---|---|
| Type | Channel |
| Username | @sdbg66 |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/sdbg66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 10:16 | 2,297 | -2 |
| 16 Aug 2026, 18:45 | 2,299 | first reading |
3 posts held, back to 15 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 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 16 August 2026 |
|---|---|
| Posts held | 3 (15 August 2026 – 16 August 2026) |
| Views total | 120 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 18:45 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.
名人堂做资金支付界一大败类，他妈死全家 ，相信跟他合作的有不少钱没拿回来吧！ 跑资金前期微信扫码通道 给我们混BC料进来 三方后台巡查60几单凭证证据确凿还死不承认 福建霞浦人混料狗 专门打混料 让他处理事情一直拖 让马商说解决方案 马商给了解决方案他不同意 让他自己说一个 他说只处理投诉订单1比三 说混料的事情处理不了 60几单 将近2W 还不能按规则赔付 混料事实摆在面前不承认 只认出投诉的 当我们是小白嘛 有跟他家合作的三方大家擦亮眼睛 最好终止合作 别到吃亏在来后悔 👤 7044170556 👦🏻 MRT-唯一负责人 🌐 @mrt9101 🇨🇳 Chinese 🕑 最後同步時間 07/08/2026 👤 7456118063 👦🏻 MRT-客服（没量别催预付） 🌐 @MRT001122 🕑 最後同步時間 16/08/2026 👤 8065604369 👦🏻 MRT-小跟班 🌐 @mrtgenban 🕑 最後…
👤 6745726122 👦🏻 小火车 🌐 @rz8878 🇨🇳 Chinese 🕑 最後同步時間 06/08/2026 👤 8552654379 👦🏻 金钻TT 🌐 @TT231 🕑 最後同步時間 14/08/2026 👤 8799739907 👦🏻 金钻集团（不私聊） 🌐 @jzjz332 🕑 最後同步時間 13/07/2026 大家注意下 这三个人是p图假回调的骗子，帮我们打款一直催回u，商户那边没收到钱，被我发现在了就把群里的聊天记录全删了，大家注意下千万别被这样的傻逼给骗了！！！ ⚡ 投稿曝光澄清联系 ⚡ @shand 闪电集团一键关注防失联
骗子卖京东E卡石油卡密等，并教学抖音打法为由（以前学过，建立的基础信任），要求打了1500U预付，期间一直拖着，各种托词画饼立人设，说他合作伙伴胖小六跑路了，是他在还债。特在此曝光，给有过合作的人提个醒，谨防受骗。 👤 7230628794 👦🏻 Llll（转账语音确认，厌蠢sb别来） 🌐 @OoOoOoOoOo630 🇨🇳 Chinese 🕑 最後同步時間 08/08/2026 👤 6777604731 👦🏻 LIII（只收钱不打钱) 🌐 @kkyq19 🕑 最後同步時間 15/08/2026 👤 6898057643 👦🏻 呆子 🌐 @daizi7658 🕑 最後同步時間 03/07/2026 ⚡ 投稿曝光澄清联系 ⚡ @shand 闪电集团一键关注防失联
Showing the 3 most recent of 3 posts we hold for @sdbg66. 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 — 375,145 of 1,549,376entries 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 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.
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.
@sdbg66 named 2 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“⚡️闪电担保曝光频道⚡️” (@sdbg66), 2,297 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/sdbg66.
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.