Channel
@taotuak1
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
5,257subscribers
-224 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002912992086 |
|---|---|
| Type | Channel |
| Username | @taotuak1 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/taotuak1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:22 | 5,257 | -91 |
| 11 Aug 2026, 20:53 | 5,348 | -127 |
| 8 Aug 2026, 22:21 | 5,475 | -6 |
| 8 Aug 2026, 05:03 | 5,481 | 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 5 pagesof 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 17 July 2026 |
|---|---|
| Posts held | 20 (4 June 2026 – 17 July 2026) |
| Views total | 1,721 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:25 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 June 2026 to 17 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
😘😘😘😘😘小黄鸭人设套图素材业务如下：😭😜💋😌😘点击蓝色文字跳转频道！😂😂 😮{精品}套图亚洲女 😮亚洲女{带IG~小红书} 😮{精品}套图亚洲男 😮亚洲男{带IG~小红书} 😮{精品}套图欧洲女 😮欧洲女{带IG~小红书} 😮{精品}套图欧洲男 😮欧洲男{带IG~小红书} 小黄鸭精聊业务全方位掌控：😘❤️😊 😞【美工】证件 P图 😞【绘画】私人定制 😞【会员】官方秒开 😞【代购】全球配送 😞【代洗】人物照片 😞【飞机】业务齐全 😞【免费】美食素材 😞【免费】话术素材 😊客服：@Anrsadn2kI 小黄鸭 😊双向客服: @Anrsadn2kI_bot 支付方式：😊😊⚡️🙂😊😊😊😃☺️😃☺️
👈🤶人设套图素材业务如下：😉😉😉😄 😖🧐😞 0️⃣海外素材 @sucai_c8 1️⃣人设套图 @taotu_renshes1 2️⃣换脸大师 @facewapp 3️⃣电话轰炸 @hongzha_c8 4️⃣素材精聊 @huashuii8 5️⃣云湾海外 @cloudbays_fwp 6️⃣话术素材 @huashui66 7️⃣吃瓜猎奇 @chiguadashen1 8️⃣贷款数据 @dazhangguishuoju 9️⃣麻豆视频 @madou_91av ➕疯狂吃瓜 @nasachadang7878 ➕成人小说 @sesebooki 🧐😆🙂↕️ 😘@sucai398 😘 @xn1314520 🥒🥒🥒🥒 请鼠标往上面😊移动，挑选您喜欢
📱精选人设素材一直在持续更新最新人设素材 💻请大家持续关注👍频道😀以免上架错过更好的人设素材🥰祝您天天开大单，财源广进！分类素材频道如下🦜 😊海外素材 ⏩@sucai_taotu1 😊人设套图 ⏩@xiaolongtaotu 😊绘图大师 ⏩@huituruanjiang 😊客服系统 ⏩@Chat007_guanfeng 🇳🇿新西兰素 ⏩https://t.me/sucaille 🇯🇵日本素材 ⏩https://t.me/sucaillu 🇮🇹意大利素 ⏩https://t.me/sucaillw 🇺🇸美国素材 ⏩https://t.me/sucaills 🇰🇷韩国素材 ⏩https://t.me/sucailly 🇸🇬新加坡素 ⏩https://t.me/sucaillt 🇲🇽墨西哥素 ⏩https://t.me/sucaillo 🇲🇾马来西亚 ⏩https://t.me/sucaillr 🔼搜索方法：输入 “#关键词”，例…
✨绘图大师·加密货币网银P图【其他均为病毒】 ， ✨绘图大师官方频道✨P图软件✨https://t.me/zuantuvi 😲📥以下为素材分类频道📥⚡️⚡️😍😍 😉【海王出海】 😉【网银转账】 😉【人设套图】 😉【聊天翻译】 😉【翻译软件】 😉【三国演义】 😉【中国素材】 😉【007 开户】 请鼠标往上面😊移动，挑选您可以点击蓝色字体
编号XH459 生活日常🌟🌟🌟🌟 #台湾 宝妈 自拍多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片1696张 视屏78个 （带Ig）
编号XH458 生活日常🌟🌟🌟🌟 #台湾 职业： 台球助教 自拍多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片1318张 视屏80个 （带Ig）
编号XH457 生活日常🌟🌟🌟🌟 #台湾 职业： 活动主持人 自拍多 瑜伽 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片1810张 视屏228个 （带Ig）
编号XH455 生活日常🌟🌟🌟🌟 #台湾 个人写真照片多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片342张 视屏8个 （带Ig）
编号XH454 生活日常🌟🌟🌟🌟 #日本 宝妈 美容 自拍多 带娃照片多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片542张 视屏35个 （带Ig）
编号XH452 生活日常🌟🌟🌟🌟 #台湾 个人写真照片多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片891张 视屏70个 （带Ig）
编号XH451 生活日常🌟🌟🌟🌟 #台湾 健身 黑丝 个人写真照片多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片2044张 视屏120个 （带Ig）
编号XH449 生活日常🌟🌟🌟🌟 #台湾 宝妈 黑丝 个人写真照片多 居家 日常生活照片比较真实 生活场景丰富 生活日常 旅游 风景 照片1760张 视屏82个 （带Ig）
Showing the 12 most recent of 20 posts we hold for @taotuak1. 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 — 932,301 of 1,481,217entries 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 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.
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.
@taotuak1 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“套图-小黄鸭套图-人设【亚洲女】” (@taotuak1), 5,257 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/taotuak1.
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.