我始终不明白 短暂的陪伴到底是奖励还是惩罚
Signed 下次见

Channel
@wenan1122
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
11,765subscribers
-773 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001790825009 |
|---|---|
| Type | Channel |
| Username | @wenan1122 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/wenan1122 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 12:55 | 11,765 | -53 |
| 29 Aug 2026, 14:47 | 11,818 | -62 |
| 28 Aug 2026, 17:37 | 11,880 | -81 |
| 27 Aug 2026, 17:57 | 11,961 | -3 |
| 26 Aug 2026, 14:53 | 11,964 | -42 |
| 25 Aug 2026, 11:29 | 12,006 | -34 |
| 24 Aug 2026, 09:01 | 12,040 | -88 |
| 22 Aug 2026, 16:34 | 12,128 | -66 |
| 21 Aug 2026, 04:04 | 12,194 | -25 |
| 20 Aug 2026, 20:28 | 12,219 | no change |
| 20 Aug 2026, 04:02 | 12,219 | -18 |
| 19 Aug 2026, 00:54 | 12,237 | -19 |
| 17 Aug 2026, 21:34 | 12,256 | -18 |
| 16 Aug 2026, 21:37 | 12,274 | -45 |
| 15 Aug 2026, 16:49 | 12,319 | -29 |
| 14 Aug 2026, 05:28 | 12,348 | -48 |
| 12 Aug 2026, 18:53 | 12,396 | -18 |
| 11 Aug 2026, 18:02 | 12,414 | -35 |
| 10 Aug 2026, 15:51 | 12,449 | -32 |
| 9 Aug 2026, 19:22 | 12,481 | first reading |
86 posts held, back to 19 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 20 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. It is computed over the 5 of 77 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 86 (19 August 2026 – 30 August 2026) |
| Views total | 13,711 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 10:13 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 49 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.
7 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 57.1% | |
| 👍 | 2 | 28.6% | |
| 🐳 | 1 | 14.3% |
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 5 of the 86 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 86 most recent posts we hold, published 19 August 2026 to 30 August 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.
我始终不明白 短暂的陪伴到底是奖励还是惩罚
Signed 下次见
顺路的话 我们会看到更多的风景 不顺路的话 祝我们都能看到不同的风景
Signed 东南亚情感文案集✨
人人都说你要知足 我没有说话 我在问我自己到底要了什么又得到了什么
Signed 暴躁的胜◎
为什么我总觉得,世界上不需要我了,我也不知道为什么,有时候想吃安眠药一走了之,在8月19日那天我吃了6颗安眠药,但是没有死,只是睡了39个小时,为什么别人不想死,都死了,为什么我想死确死不了呢, #美金
Signed _ᵒ池池のᵇᵃᵇʸ
你是我最爱过的一个人以后不会了
帮忙进一下微信群噶姐妹们
Signed 💕情思维 《资金转账确认》
积分获取方式: 1. 群里面发言 每条10积分 2. 群签到,每天签到一次可获得.500积分 3.邀请好友进群,每成功邀请以为有效好友可获得1000积分,上不封顶 积分用途: 积分可在群内兑换现金奖励,以及飞机会员,飞机典藏礼物,10000积分对应10000缅币 参与方式: 加入群聊 @xiangqinwenan 并在群聊发送 我的邀请链接 即可获得专属邀请链接
Signed 李太皇
Video, posted without a caption
Signed 性感的母螳螂❤️
好人我当过 但没有坏人舒服。
Signed 老k
总想两全,总是难全,人生不过尔尔! #胜
Signed 暴躁的胜◎
好累,感觉心情好低落,就像失去什么东西一样,为什么不能给我从新选择一次?我只想自己做出现在,我不想别人来给我做选择! #选择 #是自己给的 投稿~匿名
Signed 💕情思维 《资金转账确认》
从前认为有问题就应该沟通 直到有一天我也变成哑巴
❤1
Signed 哆一哆
Showing the 12 most recent of 86 posts we hold for @wenan1122. 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 — 1,343,200 of 1,627,068entries 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 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“情感文案馆🌙 交友| 表白” (@wenan1122), 11,765 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/wenan1122.
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.