今天突然覺得 白襯衫跟眼鏡好像很搭🤍👓 你們覺得呢?
❤2

Channel
@xiaoyi0718
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
93subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003578572210 |
|---|---|
| Type | Channel |
| Username | @xiaoyi0718 |
| Created | Between 1 December 2025 and 19 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 3 October 2026 |
| On Telegram | t.me/xiaoyi0718 |
Personal blog — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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 |
|---|---|---|
| 9 Sept 2026, 19:00 | 93 | +1 |
| 31 Aug 2026, 06:47 | 92 | +2 |
| 24 Aug 2026, 01:48 | 90 | -1 |
| 9 Aug 2026, 14:17 | 91 | no change |
| 7 Aug 2026, 18:53 | 91 | first reading |
11 posts held, back to 19 April 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
17 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 58.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 58.8% | |
| 🔥 | 7 | 41.2% |
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 7 of the 11 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 19 April 2026 to 3 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.
今天突然覺得 白襯衫跟眼鏡好像很搭🤍👓 你們覺得呢?
❤2
19歲 就想找一個人出來一起玩 有 有這麼難嗎?
🔥1
一個美麗的誤會~~😂
🔥2
https://t.me/ZS8875
成人姬地🔞色情文學城TG:https://t.me/+OCMUikZv5-5mYzNl
給你們分享一個群組 下班後如果覺得無聊 可以來這個群組看看 裡面有來自各地的女生 聊天氣氛很好 不約會也沒關係 什麼都能聊 很熱鬧 我也在裡面等你喔 🤍 https://t.me/+f34H_UQZ9sw4ZWFl
42歲了 皮膚狀態還可以吧 你們覺得呢
❤4🔥1
😔😔😔
這次真的讓我很生氣 也很難過 現在對女生都變得這麼不友善了嗎? 彼此之間給一點基本的尊重 真的很難嗎?
❤3
Photo, posted without a caption
🔥1
我也是暈了 真的很難過🥹 原本只是想好好給你一個放鬆、舒服的陪伴 所以約好之後 我就沒有再接其他人 一直等了你一整天 沒想到到了旅館 你卻臨時反悔沒有出現 還在手機上一直跟我凹價格 我自認個性算是很溫柔的人 很少生氣 但這次真的讓我有點受傷😔 等了一天 最後卻被放鳥的感覺 其實很不好受😞 如果是真的想約我 麻煩請你先開好房給我 不要在讓我白跑一趟 也給彼此一點基本的尊重
🔥2❤1
Showing the 11 most recent of 11 posts we hold for @xiaoyi0718. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“小紅色色小天地” (@xiaoyi0718), 93 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/xiaoyi0718.
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.