Telegram RegisterThe public register of Telegram
Telegram profile photo for 盘古为你导航

Channel

盘古为你导航

@qq67006_bot

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

179subscribers

+25 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001931257897
TypeChannel
Username@qq67006_bot
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live11 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/qq67006_bot

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qq67006_bot/207 · this entry15 Jun 2026, 18:30 UTC@pp67077/7315 Jun 2026, 18:30 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@pp670776 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (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 0 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 8 comparable posts for this entry, running 8 June 2026 to 11 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @qq67006_bot — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. 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.

Growth

150179164.515 August 2026 — 154 subscribers15 August 2026 — 154 subscribers1 September 2026 — 153 subscribers9 September 2026 — 150 subscribers18 September 2026 — 156 subscribers3 October 2026 — 164 subscribers13 October 2026 — 168 subscribers20 October 2026 — 172 subscribers3 November 2026 — 175 subscribers11 November 2026 — 179 subscribers15 August 202611 November 2026
10 measurements spanning 88 days, net +25. 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 146–183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 12:48179+4
3 Nov 2026, 19:55175+3
20 Oct 2026, 09:48172+4
13 Oct 2026, 02:40168+4
3 Oct 2026, 06:02164+8
18 Sept 2026, 07:02156+6
9 Sept 2026, 23:00150-3
1 Sept 2026, 14:03153-1
15 Aug 2026, 03:45154no change
15 Aug 2026, 03:35154first reading

Engagement

13 posts held, back to 2 June 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 13 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Aug 2026, 13:33 UTC16 viewsread 15 August 2026
Forwarded from @TG67077Photo

欧亿10 鼎上娱乐 开业时间 : 2026年10月16号 😀😀招商引荐 直属预留 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

11 Aug 2026, 20:46 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

4 Aug 2026, 15:30 UTC49 viewsread 15 August 2026
Forwarded from @TG67077Photo

😀【泰达】拉菲13 /已放号公测 😀正式开业:2026/8/5 官方开业活动: 开业三天首充送1%无上限 盈利竞赛奖金1000~100000 开业首周每天送88888 🟣A模式:2000 下浮千分之二 奖金号:1900~2000 工资:0.75%~1.25% 彩票月分红:25% 彩票半月占成:10% (可自由参与高频彩或低频彩) 🟣B模式:2000 下浮千分之三 奖金号:1900~2000 工资:0.95%~1.45% 彩票半月占成:40% 🔵AB模式同步待遇: 代理半月排名奖励:前20名 娱乐月分红:25%(不累计) 娱乐半月占成:10% 电子工资:1.30% ✯ 泰 达 ✯ ➤ 国內线路: https://666.tdyule8444.com https://666.tdyule4141.com https://666.tdyule9289.com https://666.tdyule6443.com htt…

27 Jul 2026, 16:32 UTC73 viewsread 15 August 2026
Photo

本人飞机 @pgqq67006 @pgbr67006 泰达验量飞机 @taidapg 其余市场的飞机都不是盘古本人

20 Jul 2026, 08:04 UTC77 viewsread 15 August 2026
Forwarded from @pp67077Photo

【泰达】待遇已公布 首次充值1000最低送316 开业5大扶持现金🧧送不停 验证销量送88-1888红包 验量联系:@taidapg 泰达开业盘古团队群内红包撒不停 飞机群内发放28888金额 更有虚拟号博彩比赛火热进行中!!! 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

2 Jul 2026, 07:12 UTC76 viewsread 15 August 2026
Forwarded from @TG67077Photo

【泰达】待遇简介 A模式: 奖金号:1900~2000 工资:0.75%~1.25% 彩票月分红:35% 彩票半月占成:20% (可自由参与高频彩或低频彩) B模式: 奖金号:1900~2000 工资:0.95%~1.45% 彩票半月占成:50% (招商以下最高签订40%) AB模式同步待遇: 招商月排名奖励:前10名 代理半月排名奖励:前20名 娱乐月分红:50%(不累计) 娱乐半月占成:20% 电子工资:1.50% 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

30 Jun 2026, 08:45 UTC62 viewsread 15 August 2026
Forwarded from @TG67077Photo

汇众分红注册链接(有抽水) https://pc.hz11.vip/reg/xnthhr 汇众无分红注册链接(不抽水) https://pc.hz11.vip/reg/twusax 汇众通用登录地址: 密码:hz123456 ——————————— https://www.hz11.vip https://www.hz22.vip https://www.hz111.vip https://www.hz222.vip https://www.hz333.vip https://www.hz555.vip —- —- —- —- 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

29 Jun 2026, 12:41 UTC48 viewsread 15 August 2026
Forwarded from @TG67077Photo

盘古团队 瑞丰7月扶持活动 —- —- —- —- 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

15 Jun 2026, 18:30 UTC100 viewsread 15 August 2026

瑞丰娱乐通知: 骰子游戏上线,独立钱包以USDT结算,可与平台互转余额,投注数据进入彩票报表(即在机器人投注1万U,报表7.2万销量),与彩票共同享受工资,分红,占成待遇。 投注机器人 瑞丰游戏 @rfyx 盘古本人 @pgqq67006 注册;https://t.me/rfyx?start=8LKOQW

10 Jun 2026, 07:54 UTC91 viewsread 15 August 2026
Forwarded from @TG67077Photo

《大众5•汇众》待遇已出 😀😀😀重要通知 市场待遇 😃汇众待遇细则:https://zd.hzyl.vip/ 😃汇众新品展示:https://cp.hzyl.vip/ 😃汇众制度框架: 1:彩票无分红线路:1800-1980 +35实时+20日结+25浮动+日结亏损佣金+线路占成 2:彩票有分红线路:1800-1980 +35实时+20日结+25浮动+月分红不累计 3:娱乐城综合游戏:高佣模式百家乐高至180、电子280(层层利润) ✔️开业排程作出如下: 1:6月30日中午15点开户 2:7月1日早上8点开放充提 —- —- —- —- 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

8 Jun 2026, 07:16 UTC72 viewsread 15 August 2026
Forwarded from @TG67077Photo

通知! 拉菲系列第13个平台-泰达娱乐 即日起正式开启招商,日程安排如下: 招商时间:2026/6/8~2026/7/31 开放注册:2026/8/3 正式开业:2026/8/5 咨询预留最强扶持待遇政策联系 —- —- —- —- 😁合作私信盘古①线 :@pgbr67006 😁合作私信盘古②线 :@pgqq67006 😀 合 作 平 台 列 表

2 Jun 2026, 19:48 UTC70 viewsread 15 August 2026
Forwarded from @TG67077Photo

感谢大家的陪伴信任,本次活动赠送完毕。

Showing the 12 most recent of 13 posts we hold for @qq67006_bot. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 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.

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.

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

“盘古为你导航” (@qq67006_bot), 179 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/qq67006_bot.

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.