可能最近太累了 提前来生理期了 又要鸽子几位充满期待的饱饱了 下次开课会平道里通知喔 蟹蟹各位大佬的关注和喜欢

Channel
🎀爽汁在干嘛
@lyna7188
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,251subscribers
-1 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001871733574 |
|---|---|
| Type | Channel |
| Username | @lyna7188 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/lyna7188 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 18:15 | 3,251 | -10 |
| 2 Sept 2026, 00:44 | 3,261 | +12 |
| 29 Aug 2026, 21:54 | 3,249 | -2 |
| 24 Aug 2026, 04:43 | 3,251 | -1 |
| 22 Aug 2026, 22:15 | 3,252 | first reading |
Engagement
15 posts held, back to 1 May 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.
- ERR · 30 days
- 28.0%
- avg views ÷ 3,251 subscribers
- Avg views / post
- 911
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 15 held
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 20 August 2026 |
|---|---|
| Posts held | 15 (1 May 2026 – 20 August 2026) |
| Views total | 2,734 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 22:15 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.
What this channel posts
- Video runtime
- 8s
- Average length
- 4s
Measured directly from 2 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
13 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 76.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 76.9% | |
| 💔 | 3 | 23.1% |
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 9 of the 15 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 1 May 2026 to 20 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.
Recent posts
七夕快乐 桃花开不开没关系 只想发财树开一下🤩
爽汁课堂开课噜 佛系开课 初次见面的giegie定金留位哦🤩
休息喽 开课会发平道哒 天气炎热giegie们记得多喝烫水 多穿衣服 以防中暑喔🙂
🤩 🤩 🤩
❤5
🤩夏日炎炎 有我真甜 你们开心我就开心 🤩 是的我就是这样一个媚粉又宠粉的爽汁
🤩金主爸爸们你们好呀 炎炎夏日 空气闷热 想必我的哥哥们偶尔也容易心情烦躁 在此呢特地准备了一些好吃的水蜜桃子送给经常支持爽汁的金主爸爸们 也借此能给努力工作的你们带来一点点的小开心 🤩 没有收到的金主们也不要伤心 因为吧爽汁毕竟口袋钞票有限 暂时还没有那么大能力回馈一大部分的哥哥们 后续有空有合适的time也会更新小礼物喔 礼物虽小但是饱含了爽汁惦记我的金主爸爸们的心 只想让你们知道我们的关系不止于枕席之欢 也可以是朋友 更可以是超越了普通界限、又比传统伴侣更自由的暧昧状态 好啦打这么多字很辛苦哒 总结 吃桃子 喝爽汁🥰 爱你们的爽汁呦🤩
❤1
爽子请客的下午茶time🍵 在雨天 在一个空闲的日子 在一个适合下午茶的日子 因为群里不够抽奖人数 所以爽汁就随机挑选一位平常比较照顾爽汁的哥哥 一边欣赏雨景 一边吸溜美味的coffee l🤩
人设仅供参考,具体自行了解🤩
自制生椰拿铁 味道老灵额 有没有喜欢的giegie 🤩
❤1
各位亲爱的金主爸爸们你们好呀 小爽又出现了 已有许久没有做回馈爸爸们的活动了 思来想去还是想做个抽奖 不过请允许我有一个小小的条件 都知道我其实是个话痨 所以非常希望金主 爸爸们可以来我的群里陪我一起聊天 想挨骂也好 想吸溜我也好 人多也会更加快乐 暂时的想法呢是这样的 爸爸们也可以提提意见 当我的聊天群的人数达到520人的时候 我会进行一波小抽奖 然后下一次抽奖呢 会放在888人的时候 至于奖品的话 请容我先卖个关子 以后也会不定期进行一些含有我个人心意的抽奖 所以 快来我的群陪我一起聊天吧😚
❤2
我们一起玩牌叭🤩 如果饱饱们有点i 不用害怕 爽汁我呀是个e人 会想尽一切办法让饱饱们开心欢愉哒 玩牌也是增进约会感情的小游戏呢🤩
Showing the 12 most recent of 15 posts we hold for @lyna7188. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“🎀爽汁在干嘛” (@lyna7188), 3,251 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/lyna7188.
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.