Channel
@taotu_rssucai1
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,161subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003209135936 |
|---|---|
| Type | Channel |
| Username | @taotu_rssucai1 |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/taotu_rssucai1 |
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 63% 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 3 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @taotuio1/40842 Aug 2026, 08:06 UTC | @taotu_rssucai1/8275 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| @taotuio1/40862 Aug 2026, 08:06 UTC | @taotu_rssucai1/8277 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| @taotuio1/40872 Aug 2026, 08:06 UTC | @taotu_rssucai1/8278 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| @taotuio1/40892 Aug 2026, 08:06 UTC | @taotu_rssucai1/8280 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| @taotuio1/40902 Aug 2026, 08:06 UTC | @taotu_rssucai1/8281 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| @taotuio1/40912 Aug 2026, 08:06 UTC | @taotu_rssucai1/8282 · this entry7 Aug 2026, 13:14 UTC | 1.00 | 5 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @taotuio1 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 5 days | @taotuio1 (8–0) |
| @xiaomengtaotu1 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 5 days | @xiaomengtaotu1 (8–0) |
| @xiaomengtaotu_c1 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 5 days | @xiaomengtaotu_c1 (8–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. 24 of the 24 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 12 comparable posts for this entry, running 7 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.
Across the whole group of 4, the earliest publisher we hold is @xiaomengtaotu_c1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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.
This channel’s posts match, word for word or near enough, posts on 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 20:02 | 2,161 | -10 |
| 8 Aug 2026, 15:42 | 2,171 | -1 |
| 7 Aug 2026, 20:33 | 2,172 | first reading |
19 posts held, back to 7 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 7 August 2026 |
|---|---|
| Posts held | 19 (7 August 2026 – 7 August 2026) |
| Views total | 106 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 20:33 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.
Measured directly from 1 video 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.
自助挑选，选好发编号给🦧🦇🌻➡️【库奇--套图】 👻🎈👻😇🥰【人设套图频道】✍🍡🎈👻🎈 ⚡️😍😍欢迎加入库奇工作室😘感谢新老客户的信任 😘人设套图素材业务如下：😭😜💋😌 😮人设套图【欧美女】 😮人设套图【亚洲女】 😮人设套图【亚洲男】 😮人设套图【欧美男】 😮 证件p图女 😮人设套图【私密女】 😮 证件p图男 😮【吃瓜】HS精聊 😮【免费】话术素材 😮 微信号商 😮【查档】天眼查档 😮 缅北包厢文化DJ 😮美工p图绘画 ✈️Ins~FB~火种~大黄蜂~巴豆~OKC~有缘~推特 …
编号 25VX135 #精品 证件🌕 日本驾驶证 证件🌕 日本护照 #日本 气质美女 生活场景丰富 自拍多 美景 旅游 美食 高尔夫 生日照 时尚会打扮 性感照 宠物 健身 高品质生活 3420张照片 635个视频 (带IG）后期可更新
编号 30XH188 #精品 证件🌕 大陆身份证 证件🌕 中国护照 证件🌕 美国驾驶证 生活日常🌟🌟🌟🌟 #香港 睡前面膜 聚会 保龄球 宝妈 家人合照 自拍多 生活场景丰富 生活日常 旅游 风景 《证件照》照片1768张 视屏172个 (带IG）
编号 13XC309 #精品 证件🌕 韩国身份证 自拍 生活日常🌟🌟🌟🌟 #韩国 生活场景丰富 海边 旅游 风景 自拍 美食 养宠物 曝光度低 照片3403 视频48个（带IG）
编号 VX684 #韩国 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 浴袍照 生日照 闺蜜照 打排球 比基尼 性感照 健身 高尔夫 宠物 床上照 4449张照片 296个视频 (带IG）后期可更新
编号 13sk25 #精品 证件🌕 马来西亚身份证 #台湾 #性感 美女 36D 自拍多 旅游 健身 1393 张照片视频 117 个《合适虚拟视频》诱惑 抖胸 解衣服扣子 视频
编号 VX675 #马来西亚 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 1553张照片 112个视频 (带IG）后期可更新
编号 VX670 #新加坡 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 床上照 闺蜜照 宠物 瑜伽 2991张照片 187个视频 (带IG）后期可更新
编号 VX671 #新加坡 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 比基尼 性感照 纹身 2018张照片 134个视频 (带IG）后期可更新
编号 VX669 #新加坡 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 毕业照 生日照 1342张照片 92个视频 (带IG）后期可更新
编号 VX639 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 潜水 健身 高尔夫 生日照 宠物 闺蜜照 机车女孩 床上照 比基尼 性感照 瑜伽 浴缸照 浴袍照 6115张照片 757个视频 (带IG）后期可更新
编号 VX640 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 比基尼 性感照 生日照 闺蜜照 宠物 531张照片 33个视频 (带IG）后期可更新
Showing the 12 most recent of 19 posts we hold for @taotu_rssucai1. 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 — 716,312 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 2 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.
“人设套图【亚洲女】renshe taotu” (@taotu_rssucai1), 2,161 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/taotu_rssucai1.
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.