Telegram RegisterThe public register of Telegram
Telegram profile photo for 每日内涵段子🔥吃瓜搞笑视频

Channel

每日内涵段子🔥吃瓜搞笑视频

@bx666bp

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

1,458subscribers

-58 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003906837005
TypeChannel
Username@bx666bp
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/bx666bp

Topic

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 57% 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
@bx666bp/8346 · this entry6 Aug 2026, 15:36 UTC@sssso001/94456 Aug 2026, 15:36 UTC1.00under a minute
@bx666bp/8347 · this entry6 Aug 2026, 15:43 UTC@sssso001/94466 Aug 2026, 15:43 UTC1.00under a minute
@bx666bp/8534 · this entry7 Aug 2026, 15:35 UTC@sssso001/95717 Aug 2026, 15:35 UTC1.00under a minute
@bx666bp/8541 · this entry7 Aug 2026, 15:49 UTC@sssso001/95787 Aug 2026, 15:49 UTC1.00under a minute
@bx666bp/8544 · this entry7 Aug 2026, 15:55 UTC@sssso001/95797 Aug 2026, 15:55 UTC1.00under a minute
@bx666bp/8346 · this entry6 Aug 2026, 15:36 UTC@ChiGua052/81286 Aug 2026, 15:36 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@sssso0015 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)
@ChiGua0525 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

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 17 comparable posts for this entry, running 6 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 @bx666bp — 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 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.

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

1,4581,5171,487.56 August 2026 — 1,516 subscribers7 August 2026 — 1,517 subscribers10 August 2026 — 1,513 subscribers13 August 2026 — 1,505 subscribers19 August 2026 — 1,501 subscribers23 August 2026 — 1,492 subscribers26 August 2026 — 1,483 subscribers4 September 2026 — 1,478 subscribers10 September 2026 — 1,458 subscribers6 August 202610 September 2026
9 measurements spanning 34 days, net -58. 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 1,449–1,526 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 00:171,458-20
4 Sept 2026, 11:171,478-5
26 Aug 2026, 15:361,483-9
23 Aug 2026, 21:391,492-9
19 Aug 2026, 20:351,501-4
13 Aug 2026, 11:481,505-8
10 Aug 2026, 08:401,513-4
7 Aug 2026, 07:381,517+1
6 Aug 2026, 19:461,516first reading

Engagement

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

What this channel posts

Video runtime
4m 27s
Average length
30s

Measured directly from 9 videos 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.

Recent posts

7 Aug 2026, 17:24 UTC1 viewsread 7 August 2026

📌 其他 📢 精选福利社 📢 菲律宾大事件 菲律宾日记 📢 缅甸新闻 泰国大事件 越南大事件 📢 金三角大事件 特区实时资讯 📢 西港事件 西港曝光 西港大事件 西港日记 西港新闻 📢 斯里兰卡大事件 东南亚动态 东南亚早报 东南亚新鲜事 📢 内涵段子🔥搞笑视频 📢 吃瓜 猎奇 热门 搞笑 📢 娱乐头条(吃瓜段子) 📢 内涵段子TV 📢 搞笑视频 内涵段子 吃瓜视频 📢 东南亚热点|新闻|曝光 📢 国产热门擦边短剧 📢 海外素材库/人设 套图 📢 欧美AV无码女优 📢 人间文案馆 📢 擦边短剧精选热播 📢 日本AV 中文字幕 精品女优合集 📢 日本AV|高清无码 📢 日本AV 中文字幕 精品女优合集 📢 每日精选AV(黑丝 自慰 露出 巨乳 ) 📢 中文字幕 | 日本AV 📢 日本无码AV/在线/最新 📢 日本无码破解av少妇人妻 📢 无码AV精选 📢 热门电影速看/高分电影推荐 📢 每日素材精选 📢 热门BGM|抖音神曲 📢

7 Aug 2026, 17:24 UTC1 viewsread 7 August 2026

🔍同城交友 📢 767资源导航|精品资源 🧩兴趣社区 📢 网红极品无码推特 📢 伪娘TS人妖男同 📢 足交黑丝白丝母狗玉足 📢 大屌人妖女王伪娘高潮 📢 欧美黑人无码AV 📢 伪娘男奴潮喷 📢 热点曝光台 📢 i8国际娱乐平台(⚽️2026世界杯专属平台) 📢 体育|电竞|足球|NBA【每日推荐】 🍉新闻吃瓜 📢 搞笑视频 内涵段子 吃瓜视频 📢 亚太曝光 亚太大事件 金边大事件 国家大事件 📢 东南亚吃瓜搞笑 📢 木牌大事件 戈公日记 西港新闻 📢 迪拜新闻|东南亚大事件|曝光群 📢 全网热搜社 📢 东南亚吃瓜 @cg258 📢 东南亚吃瓜新闻|新闻快讯 📢 新闻情报局 📢 吃瓜群众丨抖音热搜 📢 国际新闻|吃瓜新闻|突发事件 📢 全球新闻|曝光|吃瓜|突发事情 📢 东南亚大事件 | 吃瓜新闻 📢 东南亚大事件 | CG快报 🎬影视资源 📢 口爆反差极品 📢 群P巨乳妹迷奸 📢 母狗|反差|福利 📢 网红资源之家 📢 网

7 Aug 2026, 17:22 UTC2 viewsread 7 August 2026

谷歌互推【频道B4】 👉关键词搜索 丨 全网搜片 1. 日本 2. 长春真实上门服务一条龙 3. 洛阳外围全区上门空降服务 4. 导航大全 更多资源 每日更新 5. 男技师为/富婆/网红做SPA按摩推油㊙️ 6. 韩国高清裸舞直播 7. 电报流量密码|一键涨粉 8. 课外教学的船只遭遇事故,学生们流落到孤岛。 9. 收藏级韩国热舞 10. 昆明上门约 11. 体育情报局|足球|NBA|每日推荐 12. 乱伦熟女😍 少妇 13. 💋Ai自动去衣换脸(白嫖+赚钱) 14. 大尺度国模私拍评鉴 15. SMM资源库 16. 🟢绿帽淫妻少妇3P调教🟢 17. 资源导航中心|新闻导航|吃瓜导航 18. 💃 小表妹的白色嫩足 19. 中文字幕 | 日本AV 20. 韩国主播热舞 裸舞 21. 骚气小姐姐在线裸聊一对一👄 22. 全球新闻|曝光|吃瓜|突发事情 23. 吃瓜群众丨抖音热搜 24. 柏林引流|Telegram引流增粉|Tele

7 Aug 2026, 17:17 UTC2 viewsread 7 August 2026

大流量互推首选【频道B7】 最爱反差婊🌹爸爸你不要这样,小穴要裂开了,你都让女儿怀孕了! 1. 西港事件 西港曝光 西港大事件 西港日记 西港新闻 2. 番号/无码/高清 3. 热门DJ【包厢打碟 环绕上头】 4. 欧美AV|AV女优|色情片 5. 电影解说/高分电影/影视速看 6. 付费资源免费看的福利搜索引擎✅ 7. 反差学生少女萝莉 8. 🐶 晨光的母狗日记 9. AV/番号/无码/高清💿 10. 欧美AV|AV女优| 11. 电报精准获客|高效涨粉 12. 欧美系列 媚黑无码 13. 电报引流|持续增粉 14. 文案宝藏屋 孤独收藏家 15. AV/番号/无码 16. AV女优|色情片 17. 国际新闻|吃瓜新闻|突发事件 18. 好色小哥|国产福利视频 每日大赛🍑妈妈的屁股太大了,尤其是在练瑜伽的时候,爸爸太幸福了,可以天天👅我妈的大屁股🌹

7 Aug 2026, 16:23 UTC1 viewsread 7 August 2026
Photo

TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇

7 Aug 2026, 16:04 UTC1 viewsread 7 August 2026
Video

爆单了,秋天的第一杯奶茶这做的完吗 加入吃瓜dog‘

7 Aug 2026, 16:02 UTC1 viewsread 7 August 2026
Video

结婚三天就离婚 新婚3天因谁洗碗谁管钱离了,男方要求全额返还15万彩礼,经调解女方返还10万彩礼及金首饰 加入吃瓜dog‘

7 Aug 2026, 15:55 UTC1 viewsread 7 August 2026
Photo

中国最大的 AI 模型正在 Bytedance 开发 Bytedance 正在训练一个拥有高达 10 万亿参数的 AI 模型。据 Financial Times 报道,该模型的规模是目前中国最大模型 Moonshot Kimi K3 的 3 倍。

7 Aug 2026, 15:51 UTC1 viewsread 7 August 2026

常规资源: 新闻频道:https://t.me/hotdny 吃瓜搞笑:https://t.me/iiit001 DJ经典:https://t.me/DJ057 国际资讯:https://t.me/qqhots 体育赛事每日更新:https://t.me/kq978 文案馆:https://t.me/wenan018 币圈实时更新新闻:https://t.me/niuniubtc 电影解说:https://t.me/dianying28 海外素材/人设/套图:https://t.me/sucai098 黑平台曝光:https://t.me/baoguang066 群组: 体育交流群:https://t.me/sportscn 极搜中文资源搜索:https://t.me/qisuso AI中文搜索:https://t.me/aasuso 色情搜索大全:https://t.me/sosozwz 成人内

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

Mentions

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

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

“每日内涵段子🔥吃瓜搞笑视频” (@bx666bp), 1,458 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/bx666bp.

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.