Channel
@fall_in_love00
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
130subscribers
+83 since we began measuring on 8 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004469954316 |
|---|---|
| Type | Channel |
| Username | @fall_in_love00 |
| Created | 19 October 2026 — measured — dated from the channel’s first post |
| First recorded | 8 November 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/fall_in_love00 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 18:50 | 130 | +83 |
| 8 Nov 2026, 07:22 | 47 | first reading |
14 posts held, back to 19 October 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 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 2 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 14 (19 October 2026 – 8 November 2026) |
| Views total | 923 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 07:22 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 14 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 19 October 2026 to 8 November 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.
Telegram’s own ‘edited’ marker: 5 of 14 posts held from the last 30 days (35.7%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎰 伯昌君每周出击福利🎉第5弹 📮 参与条件： 🌏️ 归属地 上海,江苏,浙江 🎫 加入-My treasure 🎫 加入-知夏🍒 频道（梦中紫霞） 🎫 加入-林林私人频道 🎫 加入-赫连小窝 🎫 加入-🍵伯昌君的休假记录 🎫 加入-久久的化妆间 🎫 加入-上海普陀 徐小雨 🎁 奖品内容： 💰️ 66元口令红包🧧 × 3 ⚠️ 抽奖说明： 👉 本期感谢深情LY Robert @fall_in_love417_00赞助，从用户名应该就能看出Robert的情况了，Robert的频道也是我见过唯一的只写1名老师的LY频道 👉 要求抽奖账号提供伯昌君频道目录任意老师的出击记录才可领取，出击时间需要在抽奖活动发起前，机器人无法领取，真实LY中奖率会很高 👉 抽奖每周一次，纯粹公益，帮助优秀老师获得流量，帮助热心LY传播理念，欢迎更多赞助商支持 📅 开奖日期：(北京时间) 2026年11月13日 12时00分00秒
浮梦一朝醒，闻声意未平。 敛思不赴扰，承君分外情。 他界堪奔赴，今生未有凭。 扶策从君志，知己伴余生。 ————梦醒有感
无论未来何去何从，希望她平安，快乐。 如此便好。
第n次相遇 《此刻，它为你而跳动》 我向来拙于描摹亲密的具体过程。因为我始终觉得，最初不过是肉体的缠绵，后来便成了肉体缠绵里灵魂的相触，最后抵达两个人的极乐巅峰，身心合一。那是深深刻进两颗心里的一份美好，不足为外人道；语言一旦落到具体处，反而容易磨损那份只属于两个人的光。 第一章 再相逢 晏几道《鹧鸪天》 彩袖殷勤捧玉钟，当年拚却醉颜红。 舞低杨柳楼心月，歌尽桃花扇底风。 从别后，忆相逢，几回魂梦与君同。 今宵剩把银釭照，犹恐相逢是梦中。 已经数不清这是第多少次相见了，想必早已越过十五回的门槛。可每一次，仍旧无比期待，无比思念。这份思念在分别的日子里一寸寸积累、沉淀、提纯，直到再相逢的那一刻喷涌而出，化作发自心底的喜悦与爱怜。门开的一瞬，旅途的疲惫像被谁轻轻掸落，只剩下眼前这个人，和一句再朴素不过的问候。 …… “我回来了，宝贝，我想你了。” “我也是。” 第二章 再相怜 欧阳炯《浣溪沙》 相见休言有泪珠，酒阑重…
第n次 回家 《家的感觉》 这是已经不知道多少次再见，可每一次，我仍旧满怀期待。期待那扇虚掩的门，期待门后熟悉的身影，期待一句轻轻的“好久不见”。 （一）好久不见 电梯门合上，走廊里只剩行李箱轮子碾过地面的声音。尽头那户人家的门没有关严，暖黄的光从门缝里漏出来，在地板上铺开窄窄一条。我拉着行李走过去，鞋底蹭过门槛，玄关的灯亮着，更亮的，是笑意盈盈的站在我身前的小小人儿。 行李还搁在脚边，一股幽香已先从身后漫过来。她悄悄环住我的腰，像一阵温软的风。我转过身，低头看这小小的人儿：大眼睛扑闪扑闪，鼻梁挺拔，腮边恰到好处地染着一点红；再往下，是圆润的唇、精致的颈线，以及小麦色的健康皮肤。我的双手早已忍不住环住她，蜻蜓点水般碰了碰她的唇。两个人安静地贴着，感受彼此的心跳，最后只归为一句：“好久不见。” （二）深深地吻 这一次，我没有想让她忙碌太久。刚在床上躺好，她便凑了过来。我伸手揽住，指尖不自觉地游走，抚过光滑的皮肤，目光…
第n章 久别重逢 距离上一次分别，已经整整三周。思念像一场慢性病，越拖越重，我终于抵挡不住，专程赶了回来。偏偏天公不作美，一场突如其来的暴雨打乱了所有安排，也把我淋得透湿。 重新推开那扇微掩的门，深吸一口气——屋子里那股熟悉的香气扑面而来，悬了一路的心，终于落了地。她从侧面缓步走出，看见我的瞬间，眼睛亮了一下，张开双臂就要扑过来。我下意识后退半步，低头看了看自己还在滴水的衣角，笑着挡了挡："别，落汤鸡一个，别糟蹋你衣服。"她嗔怪地看了我一眼，那眼神里有埋怨，更多的是藏不住的欢喜。 匆匆冲了个澡，再走进客厅时，终于可以好好看看她了。还是那张精致的小脸——腮红打得恰到好处，嘴唇泛着温润的红，眼角若有若无的亮粉在灯光下微微闪烁。还是那么好看，好看得让人心口发紧，还是我记忆中的模样。视线下移，一袭金色长裙勾勒出她玲珑的曲线，温柔又张扬。 她还是忍不住扑入我怀中，轻轻蹭着我的胸口，像一只终于等到主人归来的小猫，安静地感受着彼此熟悉的气…
中间有许多许多次再见，包夜，包天，数不清的次数，我都没有动笔，都没有留下记录，后来才发现，记忆是会变淡的。于是我又重新拿起笔，企图留下记忆中的，明珠。
❤1
第五章 夜 我已经不满足，所以开始了包夜之旅。我最喜欢的就是，睡醒能一眼看到她。 写在前面：硬件软件在我之前的报告，这一次，节选自我的随笔。 请兄弟们素质出击，珍惜好老师，桩基求放过，大吊也求放过。 已经是第五次相见。她在我的怀里睡着了，呼吸轻轻的，像一只放下戒备的猫，我低头看着她，心底的某一片柔软突然被触动，我想抱紧她，但又怕惊醒她，手指抽动间，好像在做噩梦，我不禁握紧她的手，不愿放开。 梦醒，相拥，动情深吻。 情动，沉沦，抵死缠绵。 时间终了，沐浴更衣， 临别深拥，最终吻别。 坐在车后座上，望着窗外车水马龙，我知道，这份回忆会变得醇厚，直到下一次相遇，很快的，会很快的。 心脏突然漏跳一拍，我猛然意识到，我上头了
第四章 温馨 后来我得知了，即将离开上海，万般不舍之下，提高了去找她的频率。 写在前面：硬件软件在我之前的报告，后面的报告大多数抒情随笔，主观性强。请兄弟们素质出击，珍惜好老师，桩基求放过，大吊也求放过，真不耐桩。 这是第四次相见，也是彻底袒露心扉的一次。一进门，今天的她好像不太一样，如果说之前的3次相遇是阳光少女，这一次相见便是娇柔美女。她轻轻靠了过来，我环住了她的腰，俯视之下的她看起来更加娇柔，我内心的保护欲也随之爆棚。 ...... 浴室中的湿吻，让我险些把持不住。看着她精致的小脸，注视着她的眼睛，如那山间清泉般清澈，流淌入我的内心，泛起一丝涟漪。 我翻身把她压在下面，提枪上马，温柔的一塌糊涂。窗外，是哩哩啦啦的雨声；窗内，是起起伏伏的喘息声。 ...... 肉身的交融是让我心旷神怡，心与心的贴合才是此行的最大收获。 回味着刚才的缠绵，我又将悸动深埋心间，然后期待着下一次相遇。
第三章 久别重逢 第三次相遇，已经是很久之后，中间诸多坎坷，这小笨蛋总是记不清我要什么时候来找她 写在前面：好ls需要爱护，这样才能享受复刷的感觉，不是吗？ 兄弟们记着。。。桩的时候请轻一点。。。 颜值：10分，基本上跟频道白衣服照片一模一样 妆品：10分，略施粉黛，挺自然，没有浓妆艳抹的感觉，眼影带小亮点，仔细看很好看 皮肤：9分，正常黄皮，皮肤光滑 身材：身高160cm，体重45kg左右，穿鞋大概165 胸：9分，B胸，刚好一只手把住，好吃。 腰：9分，偏向沙漏身材，后入有腰窝！ 臀：9分，正常，不瘦不胖。后入能撞出臀浪 腿：9分，正常腿型，不算长腿 【软件】 陪浴：10分，yyy很棒，人体浴球，洗澡就贴上来了，真让我欲罢不能。是我见过的唯一一位私处和身体不同沐浴露的。 亲吻：10分。刚开始浅浅舌吻，do起来化身大蟒蛇，gc时紧紧搂住亲。 口活：9分，边口边眼神交流，指滑，差点被秒。 吊感：10分，紧！水超多，咕…
第二章 重逢 第二次相遇，恰逢我连续踩雷之后，后来发现，不如她万一 【细节描述】：二刷林林了，太过期待导致早上5点就醒了，没睡好表现比较差。。。再次123。熟悉的位置上楼，开门之后还是林林小小的身影，拥抱之后就抚平了心中的波澜。我特地穿的跟第一次一样的衣服，ls果然认出我来了哈哈哈。服务还是那么舒坦，中场休息还是紧紧贴着我，女友感拉的满满的！小黄文部分一带而过，小萌新再次123，但是ls一直在安慰哈哈哈！林林不好看我把头拧下来给你当球踢，同时恳请各位大哥轻点桩，林林真刚开没多久，好不容易找到宝藏ls我还想多去几次。
第一章 初遇 最开始的相逢来自一场巧合，那时在栖心地做竞拍，无意之间我发现了各方面都符合我审美的她，与竞拍失之交臂之后，当天就兴冲冲赶去。于是，一发不可收拾。 老工作室很安全，正面有门禁和保安，从后门能直接进去，老师还想下来接我，结果我们岔开了哈哈哈哈。人照合一，硬说区别的话，照片有点网红风，冲颜值绝对没问题！真人更亲切一点。ls非常主动，本萌新刚开始还很紧张，慢慢在引导下放开了。课表内容都有，就是大蟒蛇的时候我把ls妆吃的差不多了。。。画的妆，应该算淡妆。一直在聊天，哪怕我有点i也在一直引导聊天。身材方面应该是b到c的雷，然后黄皮但是光滑，蝴蝶没亲，然后ls会主动引导亲亲和口，身高160，体重应该90多（ls自己说的），腰臀比方面不太懂，后入视角不错。另外老师长发披散下来太太太好看了！！！本萌新实验了很多姿势，全程非常温柔！
Showing the 12 most recent of 14 posts we hold for @fall_in_love00. 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.
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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“My treasure” (@fall_in_love00), 130 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/fall_in_love00.
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.