Channel
@taotu811
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
19,204subscribers
-2,219 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001884905439 |
|---|---|
| Type | Channel |
| Username | @taotu811 |
| Description | 🌸心心念念是旧人🌸 🌸笔笔写下是旧情🌸 #头像 #姓氏头像 #壁纸 #素材 #文案 ！每日更新，你的关注，是我最大的动力！ 💎商务合作: @kfqiya |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/taotu811 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 16:39 | 19,204 | -346 |
| 13 Aug 2026, 04:33 | 19,550 | -280 |
| 12 Aug 2026, 08:04 | 19,830 | -574 |
| 11 Aug 2026, 06:43 | 20,404 | -463 |
| 10 Aug 2026, 05:13 | 20,867 | -232 |
| 9 Aug 2026, 01:40 | 21,099 | -324 |
| 8 Aug 2026, 03:16 | 21,423 | first reading |
24 posts held, back to 6 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 18 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 11 August 2026 |
|---|---|
| Posts held | 24 (6 August 2026 – 11 August 2026) |
| Views total | 1,978 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 08:44 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.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 5 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.
🙁☺️😚🙂↔️☺️😉 😮【亚洲女套图 】 😮 【亚洲男套图 】 😮 😮【欧美女套图 】 😮 【欧美男套图 】 😮 😮【私密女套图 】 😮 【私密女套图 】 😮 😮【海外素材库 】 😮 【美食素材库 】 😮 😮【文案素材库 】 😮 【海外智能AI 】 😮 😮【海外大事件 】 😮 【业务频道 】 😮 😮【证件定制PS 】 😮 【素描彩绘画 】 😮 😮【写人设资料 】 😮 【代开TG会员】 😮 😮【定制表情图标】 😮 【午夜小电影 】😮 😮😥🥺😬🙄😥😮😟😶🌫️ 客 服 咨 询😌： @kfqiya 双 向 联 系😌 : @qiyaai_bot 😀😊😊😃🙂😊😊😊😃☺️😳
你又装作薄情的人了 实际上失去或拥有你都很在意。
所有的用心，都源于喜欢 所有的冷漠，都写满答案。
“真正的高情商～ 是敢于在关键时刻 说难听的话， 做得罪人的决定，并不是一味的妥协！”
知道吗 我故意不理你的时候 我比你更难过 我说狠话的时候 只是想让你哄我 我从未想过要和你走散。
长期坚持的诀窍就是无视中断。比如你昨天熬夜了，那你直接无视掉它，今天回到早睡的节奏。如果你昨天偷懒没有运动，那今天按时走进健身房就好。总之不要让之前的一些决定，影响你今天的选择和判断。事物的发展都是螺旋式上升的，允许自己掉链子，但不要停止行动，只有这样你才能长期坚持。
不感谢任何伤痛 我之所以能走到今天 是因为我厉害 。
“这个世界会让你一直痛苦 直到你学会胆子大和不要脸.”
错过的交易，不会产生任何成本，鲁莽的交易，可能会让你失去一切。
大家真的不要太有生存焦虑 老天让你出现在这个世界 肯定会养你 让你有活 。
人在跌落谷底时 偏偏最励志 全靠恨意和耻辱支撑起自己。
🙁☺️😚🙂↔️☺️😉 😮【亚洲女套图 】 😮 【亚洲男套图 】 😮 😮【欧美女套图 】 😮 【欧美男套图 】 😮 😮【私密女套图 】 😮 【私密女套图 】 😮 😮【海外素材库 】 😮 【美食素材库 】 😮 😮【文案素材库 】 😮 【海外智能AI 】 😮 😮【海外大事件 】 😮 【业务频道 】 😮 😮【证件定制PS 】 😮 【素描彩绘画 】 😮 😮【写人设资料 】 😮 【代开TG会员】 😮 😮【定制表情图标】 😮 【午夜小电影 】😮 😮😥🥺😬🙄😥😮😟😶🌫️ 客 服 咨 询😌： @kfqiya 双 向 联 系😌 : @qiyaai_bot 😀😊😊😃🙂😊😊😊😃☺️😳
Showing the 12 most recent of 24 posts we hold for @taotu811. 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 — 166,371 of 1,478,351entries 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 11 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“🐦🔥皆是人间温柔【文案馆】” (@taotu811), 19,204 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/taotu811.
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.