如果非要等一个人的话 我想我要看到一双心疼我的眼睛.

Channel
拾荒文案馆🍃
@Shihuang888888
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
82subscribers
-2 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002021334525 |
|---|---|
| Type | Channel |
| Username | @Shihuang888888 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/Shihuang888888 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 16:45 | 82 | -1 |
| 24 Aug 2026, 22:23 | 83 | -1 |
| 18 Aug 2026, 03:02 | 84 | no change |
| 17 Aug 2026, 10:46 | 84 | first reading |
Engagement
20 posts held, back to 17 July 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 48s
- Average length
- 16s
Measured directly from 3 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.
Reaction mix
22 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 12 | 54.5% | |
| ❤ | 5 | 22.7% | |
| 🍾 | 3 | 13.6% | |
| 👍 | 2 | 9.09% |
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 11 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 22 reactions 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 17 July 2024 to 30 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Sticker, posted without a caption
Video, posted without a caption
🍷若酒逢知己千杯少,烈酒数杯入肚,回首望归路,茫然不知去处!那么各位家人此时可掏出你的🅱️🅱️机呼叫小北~为你保驾护航,带你回家🏠 预祝群里大家蛇年新春大吉!巳巳如意哦~家人们
👍1
拾荒文案馆🍃 pinned a photo
感谢各位兄弟在过去的一年里对众诚集团的支持与厚爱,在此新年到来之际,众诚集团在此祝各位兄弟,财源滚滚,蛇来运转,万事如意,身体健康,幸福绵长!新年快乐,2025蛇年行大运!
我只是舔狗 这辈子都会被人称为小丑,只愿意做你的小狗,你牵着我的手,向前走,告诉你的男朋友这是一只好狗,别送走。 —————风
🔥2
日子是崭新的 别烂在过去和梦里
🔥1
当凛冬割破蝴蝶的翅膀 它的眼里却是亘古春. 投稿 : 挽风
新鲜感过了,剩下的全是敷衍和厌倦,人还是刚认识的好、虚伪又浪漫,新鲜又热情。 ——投稿人:匿名
🔥3👍1
原来爱真的只在一瞬间 ——投稿人:是bb
❤1🍾1🔥1
时间永远不是记忆的对手 ————投稿人:张德帅
Showing the 12 most recent of 20 posts we hold for @Shihuang888888. 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.
Mentions
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.
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.
Cite this entry
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“拾荒文案馆🍃” (@Shihuang888888), 82 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Shihuang888888.
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.