Channel
@taotu_sucail2
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,150subscribers
+1,036 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003255677298 |
|---|---|
| Type | Channel |
| Username | @taotu_sucail2 |
| 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 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/taotu_sucail2 |
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 07:00 | 2,150 | +1,016 |
| 14 Sept 2026, 17:18 | 1,134 | -2 |
| 10 Sept 2026, 18:57 | 1,136 | -7 |
| 7 Sept 2026, 02:22 | 1,143 | no change |
| 1 Sept 2026, 23:55 | 1,143 | -2 |
| 30 Aug 2026, 06:03 | 1,145 | +547 |
| 24 Aug 2026, 00:58 | 598 | -426 |
| 20 Aug 2026, 16:22 | 1,024 | -76 |
| 17 Aug 2026, 15:58 | 1,100 | -4 |
| 14 Aug 2026, 08:55 | 1,104 | -5 |
| 11 Aug 2026, 05:26 | 1,109 | -5 |
| 7 Aug 2026, 20:31 | 1,114 | first reading |
20 posts held, back to 27 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 page of 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 27 August 2026 |
|---|---|
| Posts held | 20 (27 August 2026 – 27 August 2026) |
| Views total | 9,632 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 02:22 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.
助挑选，选好发编号给🦧🦇🌻➡️【小沫--套图】 ⚡️⚡️😍😍欢迎加入小沫工作室😘感谢新老客户的信任 😘人设套图素材业务如下：😭😜💋😌 😮人设套图【亚洲女】 😮人设套图【欧洲女】 😮人设套图【亚洲男】 😮人设套图【欧洲男】 😮 证件p图女 😮【私密照】 😮 证件p图男 😮【吃瓜】HS精聊 😮 绘画素描 😮美工P图 😮【免费】话术素材 😮 微信号商 😮 缅北包厢文化DJ 🎧🎧 🎧🎧 🎧🎧 🎧🎧 🎧🎧🎧 下面新版素材分类频道，是最正规的频道， 可以先关注，分类明细，后续有更新！！ 😃【素材总库】：@sucaizk_1 😃【韩国素材】：@sucai01_taotu1 😃【美国素…
编号UU130 素材简介：#台湾 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 自拍多 【图片753张 视频115个】 （带有IG持续更新）
编号UU129 素材简介：#新加坡 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 瑜伽 【图片1023张 视频92个】 （带有IG持续更新）
编号AUU128 精品：10u 素材简介：#台湾 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 自拍多 打高尔夫球 【图片2270张 视频164个】 （带有IG持续更新）
编号UU127 素材简介：#台湾 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 自拍多 【图片2657张 视频358个】 （带有IG持续更新）
编号AUU126 精品：10u 素材简介：#台湾 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 自拍多 居家魅惑漏胸沟自拍多 宅男幻想天花板 宝妈 【图片1263张 视频143个】 （带有IG持续更新）
编号UU125 素材简介：#香港 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 名媛 打高尔夫球 自拍多 【图片1969张 视频287个】 （带有IG持续更新）
编号UU124 素材简介：#香港 合适35至45岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 宝妈 【图片2118张 视频49个】 （带有IG持续更新）
编号UU123 素材简介：#香港 合适35至45岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 宝妈 【图片2276张 视频165个】 （带有IG持续更新）
编号UU122 素材简介：#香港 合适35至45岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 宝妈 自拍多 【图片967张 视频59个】 （带有IG持续更新）
编号UU121 素材简介：#香港 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 【图片242张 视频7个】 （带有IG持续更新）
编号UU120 素材简介：#香港 合适25至35岁人设 个人自拍 艺术照 个人日常分享较全面 不同场景照片丰富 素材真实 居家 好友合照 喜欢旅行 有旅行照片 照片氛围比较接近素人朋友圈 【图片609张 视频105个】 （带有IG持续更新）
Showing the 12 most recent of 20 posts we hold for @taotu_sucail2. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“人设套图素材【亚州女】taoturenshe” (@taotu_sucail2), 2,150 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/taotu_sucail2.
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.