Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6067162660

Channel
YYの回忆录
@Lzzzz7777
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,111subscribers
+34 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002354570792 |
|---|---|
| Type | Channel |
| Username | @Lzzzz7777 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Lzzzz7777 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:43 | 1,111 | +7 |
| 9 Aug 2026, 10:51 | 1,104 | +27 |
| 6 Aug 2026, 20:27 | 1,077 | no change |
| 6 Aug 2026, 20:05 | 1,077 | first reading |
Engagement
6 posts held, back to 22 June 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 28.4%
- avg views ÷ 1,111 subscribers
- Avg views / post
- 316
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 6 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 2 August 2026 |
|---|---|
| Posts held | 6 (22 June 2026 – 2 August 2026) |
| Views total | 632 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:05 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.
Reaction mix
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 2 of the 6 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 22 June 2026 to 2 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
【妹子花名】:阿依夏 【妹子车牌】:@ayixia0 【所在位置】:高新区 天府二街 【验证时间】:7月 【修车水费】:800P 1400PP 【是否代聊】:自聊 【硬件评价】: 身高168左右,体重90斤,年龄大概21-23左右,人照相似度8.8分左右,视频去点美白,基本是本人;真人颜值优秀,比照片看着更显御姐,黑长直的秀发配深邃大眼+精致的面容,看着比较养眼,身材是真滴不错,特别穿短裙的时候,纤细腰身和大长腿看的牛牛有点硬🤣;手腕处有纹身,整体肤色小麦色,很光滑;胸为B+,有点科技,但影响不大,胸型好看,圆润挺拔;下面洞口比较小,收缩感很明显,稍微深入一顶就把牛牛给咬住,有点遭不住,射意强烈🤣(ps: 楼下等待期间,碰巧遇见,确实有种平常路边看见漂亮小姐姐行注视礼的既视感) 【软件评价】: 陪洗 A面 口 大蟒蛇 69 服务整体不多,但比较细致,舌吻是那种任人索取的状态,舌头很软,可以随便搅拌😋,🐍🐍精爱了~女上很会扭,…
【妹子花名】:虞姬 【妹子车牌】:@Yuji_baby 【所在位置】:高新区 天府二街 【验证时间】:7月 【修车水费】:1100P 1600PP 【是否代聊】:自聊 【硬件评价】: 身高167左右,体重90斤,年龄大概23-25左右,人照相似度8.8分左右,戴眼镜那张照片去美白,基本接近;真人颜值顶,妆容魅感强,红唇大眼配大波浪,御姐感拉满;整体身材比例很好,细腰长腿,进门穿个黑丝情趣装,确实有食欲😀;大腿处有纹身,整体肤色偏白,比较光滑;胸为天然B+,被黑色情趣勾勒的很圆润挺拔;重点下面是真紧,直接紧紧箍住,感觉都不好抽插🤣,依然传教士最佳,看着老师精致五官下水灵灵的模样,精神愉悦,期间随便🐍🐍! 【软件评价】: 水中萧 A面 指滑 舌吻 服务整体不多,走的情绪流模式,说话声线很好听,毕竟学的播音主持;从进门到出门整个过程中,各种有意无意的微表情和小动作让人心痒痒~女友感很强,随时直勾勾的看本狼,整的都有点害羞了😅,🐍🐍…
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6067162660
【妹子花名】:小羊 【妹子车牌】:@YNAAAB21 【所在位置】:高新区 天府三街 【验证时间】:6月 【修车水费】:600P 900PP 【是否代聊】:自聊 【硬件评价】: 身高161左右,体重90斤,年龄大概27-29左右,人照相似度8.9分,去掉美白,很像;真人颜值精致,人妻感很足,穿衣前比较端庄,褪去衣物后来到床上,骚骚的感觉就出来了😄,眼神拉丝;整体身材匀称,皮肤比较白皙光滑,胸为B,掌中宝,软糯;户型为小蝴蝶,外褐内粉,水比较多;老师是真敏感,很容易高潮~每个姿势夺一会都能感受到里面持续收缩,来感觉后的舌吻略微窒息... 【软件评价】: 陪洗 AB面 大蟒蛇 69 服务意识很强,从头到尾都很亲切,不会有尬住的时候,🐍的特别投入,敏感的一批,除了卧室灯光暗了点,其他都挺好的 【锐评】: 该老师处于御姐与少妇之间的类型,人照相似度比较高,颜值不错,妆容比较精致,大蟒蛇类型,舌吻侵略性十足;日感总体不错,敏感类型,…
艺名:沁颜 车牌:@qinyan111 被沁颜照片所吸引,是小狼比较喜欢的那种类型。见到真人,果然没失望,真人和自拍照9分像,就是本人。颜值属于那种比较有气质的御姐(气质方面可以参考容祖儿、姚晨那种感觉)。长相耐看,长发柔顺,第一印象温柔轻熟。重庆妹妹,性格好,热情。进门主动帮小狼拖鞋,服务意识和情商这块不得不表扬一下。 脱衣后身体曲线匀称紧致,腰臀比也不错。大长腿诱人,胸部虽然不大(B左右),但是整体和谐,穿上黑丝高跟,更有女人味了。 洗澡期间贴身前后胸推,女友感爆棚。前戏时间长,口技不浮夸,循序渐进,经验丰富,而且时不时抬头眼神拉丝的看着你,就问那个狼友能拒绝这种含情脉脉的眼神。爱爱时像蛇一样缠绕在小狼身上,主动迎合小狼各种姿势,不公式化。就像恋人一样,事后紧紧相拥不愿意拔出来。大蟒蛇持续不断,整个爱爱过程让小狼身心愉悦。沁颜算是近期遇到比较不错的老师,值得推荐,提前沟通可拍不露脸小视频,今天忘记了,下次回锅再补给兄弟…
❤2
Showing the 6 most recent of 6 posts we hold for @Lzzzz7777. 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
Citation-graph rank — 873,933 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.
Forward network
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.
Mentions
Named by 2 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“YYの回忆录” (@Lzzzz7777), 1,111 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Lzzzz7777.
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.