Telegram RegisterThe public register of Telegram

Channel

起点交易 - VIP供需资源

@qdvip

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

61,294subscribers

-351 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002036531212
TypeChannel
Username@qdvip
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/qdvip

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 49% 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 2 other registered channels. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qdvip/7955 · this entry5 Aug 2026, 13:02 UTC@HQWE00/639016 Aug 2026, 13:05 UTC1.0024 hours
@qdvip/7964 · this entry6 Aug 2026, 03:24 UTC@HQWE00/638856 Aug 2026, 03:25 UTC1.00under a minute
@HQWE00/638906 Aug 2026, 08:02 UTC@qdvip/7967 · this entry6 Aug 2026, 08:02 UTC1.00under a minute
@qdvip/7970 · this entry6 Aug 2026, 09:03 UTC@HQWE00/638946 Aug 2026, 09:03 UTC1.00under a minute
@HQWE00/638956 Aug 2026, 09:30 UTC@qdvip/7971 · this entry6 Aug 2026, 09:30 UTC1.00under a minute
@qdvip/7972 · this entry6 Aug 2026, 10:32 UTC@HQWE00/638966 Aug 2026, 10:33 UTC1.002 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@HQWE0022 (7/8 hand-verifiable sample passed)1.00under a minuteeven
@kuaishou17 (7/8 hand-verifiable sample passed)1.00under a minute@kuaishou (116)

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. 22 of the 22 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 39 comparable posts for this entry, running 5 August 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 3, the earliest publisher we hold is @qdvip — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 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 2 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

61,29461,64561,469.56 August 2026 — 61,645 subscribers6 August 2026 — 61,645 subscribers6 August 2026 — 61,623 subscribers8 August 2026 — 61,598 subscribers8 August 2026 — 61,523 subscribers10 August 2026 — 61,432 subscribers10 August 2026 — 61,417 subscribers11 August 2026 — 61,360 subscribers12 August 2026 — 61,294 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net -351. 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 61,241–61,698 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:2461,294-66
11 Aug 2026, 22:5861,360-57
10 Aug 2026, 23:0661,417-15
10 Aug 2026, 02:2261,432-91
8 Aug 2026, 23:5061,523-75
8 Aug 2026, 00:0861,598-25
6 Aug 2026, 23:2861,623-22
6 Aug 2026, 12:4561,645no change
6 Aug 2026, 12:3861,645first reading

Engagement

110 posts held, back to 5 August 2026the 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
1.26%
avg views ÷ 61,294 subscribers
Avg views / post
771
110 posts measured
Reaction rate
0.139%
reactions ÷ views · ER floor
Posts in window
110
of 110 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 52 of 110 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 12 August 2026
Posts held110 (5 August 202612 August 2026)
Views total84,794
Reactions total59
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 19:20 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

59 reactions across 50 posts, in 3 distinct kinds. The most used accounts for 78.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4678.0%
1220.3%
😭11.69%

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 52 of the 110 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 59reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 110 most recent posts we hold, published 5 August 2026 to 12 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

12 Aug 2026, 18:31 UTC20 views1 reactionsread 12 August 2026

🔥2026王炸五平台!🌟⚡领航🔥汇赢🔥TOP🌟君临💗星耀!(起点担保强烈推荐) 充值100送88 充值500送288 🔥全新模式大水满满 认准飞机实力总代太子集团太子哥! 🌟领航国际: lhr66.top (强推🌟) 🌟汇赢国际: hu65w.top (强推💗) 🌟君临国际: y6gx.top 🌟星耀国际: x13wy.top 🌟TOP娱乐: t94ur.top 100+88南宫综合所有台点我查看 🔥太子哥: @duge (认准四字id赌哥) 🔥飞机担保群:https://t.me/+NfWobfdyMyw2MDBh 🔥爆奖反馈🧧:https://t.me/NGbaojiang 💗麻豆视频: @NGmadou 🔥免费代理: @NGGFvpn 全网最高点位返水,认准飞机实力总代太子集团,全网在押20w!

👍1

12 Aug 2026, 16:32 UTC101 views1 reactionsread 12 August 2026

🔥2026王炸五平台!🌟⚡领航🔥汇赢🔥TOP🌟君临💗星耀!(起点担保强烈推荐) 充值100送88 充值500送288 🔥全新模式大水满满 认准飞机实力总代太子集团太子哥! 🌟领航国际: lhr66.top (强推🌟) 🌟汇赢国际: hu65w.top (强推💗) 🌟君临国际: y6gx.top 🌟星耀国际: x13wy.top 🌟TOP娱乐: t94ur.top 100+88南宫综合所有台点我查看 🔥太子哥: @duge (认准四字id赌哥) 🔥飞机担保群:https://t.me/+NfWobfdyMyw2MDBh 🔥爆奖反馈🧧:https://t.me/NGbaojiang 💗麻豆视频: @NGmadou 🔥免费代理: @NGGFvpn 全网最高点位返水,认准飞机实力总代太子集团,全网在押20w!

1

12 Aug 2026, 15:42 UTC129 viewsread 12 August 2026

微信zm直登 不用账号密码!!! 👑👑👑👑 微信zm 600起6️⃣0️⃣0️⃣ 招收大量号商价格🤩🤩🤩 微信zm号商来大量 公群负责人:@dyh5221 @WB88810 公群链接:https://t.me/+ocXNP6b_JrQ2ZWE1

12 Aug 2026, 15:39 UTC131 viewsread 12 August 2026

😃😀😃😀😃·😀😃😃😀 D228 云机微信zm包天6️⃣0️⃣0️⃣起步 已押1000U 😃😃😃😃😃 😃😄😄😄😃 ————————— 公群通道:https://t.me/+EMATRbnkYRs3NDI1 验群通道: @dianpu 公群大全 官方名单 报备流程 注意事项

12 Aug 2026, 13:34 UTC191 viewsread 12 August 2026

🔥2026王炸五平台!汇赢💰鼎天💰星耀💰无限💰新时代💰 充值100送88充值500送288 🔥全新模式大水满满 认准飞机实力总代强盛集团刀哥! 🔥汇赢国际: drd25.top (新台💗) 🔥無限娱乐: 86xwa.top (推荐) 🔥新时代: xsu52.top (推荐) 🔥星耀国际: zxy50.top 🔥鼎天国际: e55dc.top 100+88南宫综合所以台点我查看 ✍️刀哥:@NGdaoge(具体福利待遇请联系刀哥或者下方担保群置顶为准) ✍️飞机担保群: @NGqiangsheng ✍️爆奖反馈🧧: @NGbaojpd ✍️麻豆视频: @NGmado ✍️大神交流:@NGbaoj 全网最高点位返水,认准飞机实力总代强盛集团,全网在押20w!

12 Aug 2026, 13:33 UTC158 viewsread 12 August 2026

大发直营盘口 招租 uu远程微信 只语音不打字 要求:30好友以上活跃私人账号 需要电脑 下载uu远程只语音不打字 一台电脑一个号 挂电脑上就行剩下的什么都不用管 掉了补扫一下即可 超强续租 价格2️⃣😂😂起 量大号商还可谈 欢迎各位散户号商前来对接❗️❗️❗️❗️❗️❗️❗️❗️❗️ 联系人: @aale_220906 @Ming569 @dafa2350 公群链接:https://t.me/+o4NaodwbxAY3MTM1

12 Aug 2026, 13:01 UTC150 viewsread 12 August 2026

⚡️龙腾国际⚡️NG新台水蛇林帝同款 新用户注册充值100+100 500+388 1000+888 项目介绍:南宫全系列 pg 捕鱼 电子 加拿大 快三 百家乐 六合彩等等 新用户一个月可以保证不输钱 提款支持:🔥usdt 支付宝 银行卡 🔥不想玩的可以邀请好友充值500返700人头费 😀龙腾国际: tep67.top 😀聚鑫汇: f42hj.top 爆分反馈彩金群: https://t.me/+N9O9od2ngpJkMTNl 你不干不要叫我不要干 你不干你怎么抽中华住酒店 打不开关VPN或者切换Wi-Fi/流量 🟥🟥🟥🟥全网最强福利🟥🟥🟥🟥 ➡️1.充值任意金额送88.88红包 ➡️2.新人积累充值600送388红包 (投稿爆分素材奖励58彩金)✔️

12 Aug 2026, 11:40 UTC179 views1 reactionsread 12 August 2026

😎😀😀😀😀😎 😃😃系列:🇨🇦 : 经典2.0PC 🇨🇦 : 满赔PC28 🇨🇦 : PC2.8倍群 🇨🇦 : 网盘PC28 🇨🇦 : 2.84高倍PC 😀😀系列:🎰: 人民币版电子 🎰: U版电子 🎰: 完美娱乐综合 😀平台稳定,资金安全,您值得信赖的首选! 😀所有游戏公开透明,公平公正公开! 😀 玩得安心,赢得放心! 😀 官方频道: @wmzhpd 😁 官方客服: @xj666777

👍1

12 Aug 2026, 10:33 UTC187 viewsread 12 August 2026

⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥⭐️ ⭐️ ⭐️ 🫥🫥🫥🫥🫥 总押300万U 🇨🇦新宝飞投PC公群 🫥综合盘娱乐🎰 @xbyl 🎰:新宝娱乐纯电子 @xbdz 🎲快三扫雷合集:@k3k3 🇨🇦PC28🤖合集: @xb28 🫥新宝娱乐集团总群 🏆新宝娱乐官方频道: @x777 任意游戏流水均可免费参与流水夺宝最高奖励999999U @k777 😃有担保更放心 大额无忧! 😃PC/骰子客服👉 @x111 🫥电子类客服👉 @x444 新宝娱乐 · 三年沉淀,感谢信任,一路同行! 🫥🫥🫥🫥🫥🫥 为保障您的资金安全,请务必通过官方导航 @okyx 加入游戏公群! 🫥 验群机器人: @okxx

12 Aug 2026, 09:20 UTC191 views2 reactionsread 12 August 2026

月入过千美金项目教学💰 各位:混的人、挂壁仔、迷茫之人为了逃离出租屋 往更远的路走 现在来找我学习业务赚钱吧! 只要你肯干 收入只会涨 来找 @diaobao 开启你的新路子! 0风险! 0风险! 0风险! 上车费用仅需 58u 起,赚不回来你来砍我! 负责人 @diaobao 客服 @vk9178 起点公群: https://t.me/+sK-uN45Ku0M2ZGQ1 七月团队·天眼/查档/司法/网逃/案件 负责人 @diaobao 平安公群: https://t.me/+2c7miBvVqYhjYjBh 七月团队微信拉三人群 24一单 风险低 来就赚! 负责人:@diaobao 客服 @vk9178 提米在押:https://t.me/+Oi8iAc3MgEc2Mzhl

👍2

12 Aug 2026, 07:07 UTC220 viewsread 12 August 2026

😍😍😍😍😍盘口直收微信三人小群.😇 数据高通过.成单效率高.😍单号收入200+.一个人也可以收入多多.😀不封号😀不封号😀不封号 要捡😀的兄弟速度私信我 😍不会做的手把手教会.没架子人好说话.不懂得地方随时解惑. 简单好上手.散户也能稳稳吃肉. 😍😍😍😍😍😍😍😍🕶单价:😍😍 🕶团队:😍😍-😍😍 另收团队工作室公群老板,价格置顶 📱大量收 机房 团队 靠谱认真的有扶持.❣️ 😀😀😀😀 t.me/TGguniang2 😀😀😀😀 t.me/TGtubao - - - - - - - - - - - - - - - - https://t.me/+ikUrniUlk442YTFl

12 Aug 2026, 06:50 UTC206 viewsread 12 August 2026

抖音博彩无限发 封号包赔! 封号包赔不只是说说 对账号无要求 新号/老号/未实名 都能做 不修改任何资料 素材内容无任何引导.敏感.联系方式等 内容 作品审核 100% 通过必能发 单号一天发30 条,单号利润 450 以此类推欢迎团队机房散户前来对接 任何只要能发作品的抖音都可以做 做单联系:@JinYe6 公群:https://t.me/+VnpUwe9WraE1MzBh

Showing the 12 most recent of 110 posts we hold for @qdvip. 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 — 897,179 of 1,151,006entries 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 1 registered channel — 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.

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

“起点交易 - VIP供需资源” (@qdvip), 61,294 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/qdvip.

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.