Channel
@TG_OQ005
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
1,008subscribers
-26 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001949905679 |
|---|---|
| Type | Channel |
| Username | @TG_OQ005 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/TG_OQ005 |
Adult — 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 71% 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.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @taotu9n/2223 Jun 2026, 15:04 UTC | @TG_OQ005/1233 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| @taotu9n/2233 Jun 2026, 15:04 UTC | @TG_OQ005/1234 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| @taotu9n/2243 Jun 2026, 15:04 UTC | @TG_OQ005/1235 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| @taotu9n/2253 Jun 2026, 15:04 UTC | @TG_OQ005/1236 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| @taotu9n/2273 Jun 2026, 15:04 UTC | @TG_OQ005/1238 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| @taotu9n/2283 Jun 2026, 15:04 UTC | @TG_OQ005/1239 · this entry4 Jun 2026, 03:53 UTC | 1.00 | 13 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @taotu9n | 10 (8/8 hand-verifiable sample passed) | 1.00 | 13 hours | @taotu9n (10–0) |
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 10 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 12 comparable posts for this entry, running 4 June 2026 to 29 June 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.
Across the whole group of 2, the earliest publisher we hold is @taotu9n. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:23 | 1,008 | -26 |
| 8 Aug 2026, 03:07 | 1,034 | no change |
| 8 Aug 2026, 02:33 | 1,034 | first reading |
20 posts held, back to 4 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 pageof 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 20 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
✅客服 @Anrsadn2k11【妃妃套图】🥇素材总频道有五万多张美食素材和生活素材不断更新➡️ 海外素材库总频道 三方套图专区 ⬇️专注收录曝光量低的三方人设套图 ➡️💞【亚洲男套图】 ➡️💞【亚洲女套图】 ➡️💞【欧美男套图】 ➡️💞【欧美女套图】 ➡️💞【女私密套图】 ➡️💞【免费男私密】 妃妃精聊业务⬇️做业务必备各种资源专区，谢谢关注 ➡️🔥【 P 图 证 件 】 ➡️🔥 【绘 画 素 描】 ➡️🔥【免 费 话 术】 ➡️🔥 【人 设 代 写】 ➡️【最靠谱号商】微信号、抖音号、支付宝、实名手机卡等 点击蓝色文字，可跳转频道 ➡️ 欢迎关注 🥇免费素材总频道 ➡️ 24h在 线 客 服 妃妃： @Anrsadn2k11
编号UK206 生活日常🌟🌟🌟🌟 #德国 自拍多 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片2166张 视屏230个 （带IG）
编号UK199 生活日常🌟🌟🌟🌟 #巴西 宝爸 健身 肌肉 家人合照 生活场景丰富 聚会 旅游 风景 生活日常 照片671张 视屏42个 （带IG）
编号UK200 生活日常🌟🌟🌟🌟 #英格兰 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片1521张 视屏198个 （带IG）
编号UK201 生活日常🌟🌟🌟🌟 #英国 正装照 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片896张 视屏84个 （带IG）
编号UK202 生活日常🌟🌟🌟🌟 #瑞典 自拍多 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片1067张 视屏93个 （带IG）
编号UK203 生活日常🌟🌟🌟🌟 #德国 自拍多 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片456张 视屏26个 （带IG）
编号UK204 生活日常🌟🌟🌟🌟 #德国 自拍多 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片1866张 视屏199个 （带IG）
编号UK205 生活日常🌟🌟🌟🌟 #德国 宝爸 自拍多 健身 肌肉 朋友合照 生活场景丰富 聚会 旅游 风景 生活日常 照片1068张 视屏162个 （带IG）
✅客服 @Anrsadn2k11【妃妃套图】🥇素材总频道有五万多张美食素材和生活素材不断更新➡️ 海外素材库总频道 三方套图专区 ⬇️专注收录曝光量低的三方人设套图 ➡️💞【亚洲男套图】 ➡️💞【亚洲女套图】 ➡️💞【欧美男套图】 ➡️💞【欧美女套图】 ➡️💞【女私密套图】 ➡️💞【免费男私密】 妃妃精聊业务⬇️做业务必备各种资源专区，谢谢关注 ➡️🔥【 P 图 证 件 】 ➡️🔥 【绘 画 素 描】 ➡️🔥【免 费 话 术】 ➡️🔥 【人 设 代 写】 ➡️【最靠谱号商】微信号、抖音号、支付宝、实名手机卡等 点击蓝色文字，可跳转频道 ➡️ 欢迎关注 🥇免费素材总频道 ➡️ 24h在 线 客 服 妃妃： @Anrsadn2k11
编号DD44 素材简介：#法国 合适45至55岁人设 素材整体表现比较放松 更多的是看起来比较热爱生活 热爱运动 居家 热爱旅行 素材比较接近真实普通人生活 宝爸 【图片411张 视频33张】 （带IG持续更新)
编号DD45 素材简介：#意大利 合适45至55岁人设 腹肌 健身 欧美型男 素材整体表现比较放松 高大上生活 更多的是看起来比较热爱生活 热爱运动 居家 热爱旅行 自拍多 【图片377张 视频37张】 （带IG持续更新)
Showing the 12 most recent of 20 posts we hold for @TG_OQ005. 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 — 210,846 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.
Named by 7 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“套图 【欧美男】” (@TG_OQ005), 1,008 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TG_OQ005.
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.