Channel
@lomomo4464
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,028subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003584494387 |
|---|---|
| Type | Channel |
| Username | @lomomo4464 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/lomomo4464 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 00:44 | 1,028 | -3 |
| 7 Aug 2026, 10:30 | 1,031 | +1 |
| 6 Aug 2026, 19:51 | 1,030 | first reading |
11 posts held, back to 20 July 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 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 6 August 2026 |
|---|---|
| Posts held | 11 (20 July 2026 – 6 August 2026) |
| Views total | 185 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:51 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.
免费互推【频道A5】 黄色交流群 1. 校园贷泄密 2. 日本无码破解 3. 可爱少女 4. 大理上门约 5. 黄色交流群 6. 电报低成本引流｜高质量增粉 7. 福利姬轮奸海角社区 8. 日本AV|FC2小站 9. 无锡非常不错的妹子真实靠谱喝茶 10. 伦理乱伦护士处 11. 日本AV| JAV |中文字幕|番号资源库 12. 纯色怀旧猫片（陆港台3-4级） 13. 武汉外围上门喝茶 14. 日本无码破解av母狗荡妇 15. 初中老师被学生偷拍 16. 高中小妹第一次 17. 裸贷秘密 18. 💋日本超清无码AV|熟女反差少妇💋 19. 18岁妹妹 20. 裸贷泄密资源 21. 绿帽人妻足交乱伦玉足 22. 日本AV|高清无码 23. 大学生宿舍和男的一起自拍泄露 黄色交流群
⭐️⭐️⭐️星链互推 - B03车⭐️⭐️⭐️ AD：十万全国楼凤资源🔥每日更新 AD：海量资源免费搜片群 1. 深圳品茶外围认证 2. TT 一对一 裸聊 四爱 sm 3. 裸贷裸条肉偿大学生曝光 4. 免费机器人 机器人定制 5. OK潮物工作室 6. SPA按摩/男技师/夫妻SPA👅 7. 西安嫩妹外出品茶 8. OK潮物包 9. 直播反差婊 10. 【推特 探花 onlyfans】精选 11. 北京兼职楼凤大全 12. QCQ—精神小妹 AD：引流神器自动发片机 AD：👉全网破解资源免费搜索👈
一个很邪恶的频道 未满十八岁禁止入内 🚀来自百度互推【 E12 】组🚀 1. 菲菲情趣裸聊馆1v1视频 2. 菲菲 情趣馆 🔞裸 聊 视 频 1V1 3. 菲菲🎀1v1裸聊专属频道 4. 户口地址⛳️邮政快递地址⛳️顺丰单号地址 5. 车牌号查车档-认准户部查档_提供车牌号查车辆详细档案_包... 6. 只爱无码！白虎少女欧美AV 7. 抖音网红|反差母狗|黑料福利姬 8. 性感尤物💄反差乱伦 9. 【兰州全区高端外围 】只做真人真照兰州 10.福州外围品茶 11.南昌外围品茶 12.💯反差少女日记🔞 13.👺小骚货求着要吃🔞鸡巴深喉口爆吞精 14.连云港超敏感在校小姐姐可约可品茶 15.导航大全 更多资源 每日更新 😍一个很牛逼的频道 限时免费开放 👙失足少女求调教（人妻被逼出轨😍） 💋性瘾少女嫩穴想被插入😍
原味互推【频道A2】 神马搜索 1. 电报低成本引流｜高质量增粉 2. 反差/少妇/母狗 3. 11傲慢人妻连体衣 4. 12黑丝的高跟鞋空姐 5. 🏆新闻黑料曝光吃瓜•bg196📨 6. 电报智能吸粉流量翻倍 7. 多人乱伦酒吧精神小妹 8. 小学老师和学生会长 9. 59把同事约到家里玩 10. 49欲求不满的长腿巨乳嫂子 11. 街边喝酒醉女孩 12. 原味 13. 31我的大奶女领居 极搜搜索
川普大流量引流互推【频道B0】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 香港onlyfans合集 2. 泰州~高端外围 3. 绿帽 人妻 换妻 4. 少萝少御御姐在线裸聊一对一 5. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 6. 光年-抖音粉丝小红书粉丝快手粉丝抖音点赞微博数据快手视频号涨粉 7. 韩国性感热舞 8. 极品身材 9. 电报精准获客｜高效涨粉 10. 韩国主播热舞 11. 第一視角我和女神的浪漫視頻💞 12. 最牛的ai脱衣机器人🤖 13. 韩国热舞 直播录制 14. 广州一手妹妹上门 15. 超可爱清纯巨乳嫩妹少女反差婊 16. 超级无敌免费ai脱衣机器人 17. 在线裸聊一对一👅包射包爽歪歪 18. 【TG】大小事🤌🏻 19. 电报精准获客｜高效涨粉 20. 💦 终极快感体验 🔥 21. 付费资源免费看的福利搜索引擎✅ 22…
大流量互推首选【频道B1】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 日本无码系列 2. 付费资源免费看的福利搜索引擎✅ 3. 日本无码破解av 4. 热门音乐｜抖音神曲｜BGM 5. 欧美精选无码Av 6. 神仙文案集 一句入心 7. 爽翻天妹妹在线视频裸聊👄等你来哟 8. 导航大全 更多资源 每日更新 9. 绿帽 人妻 换妻 10. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 11. 南京嫩妹上门服务 12. 一对一视频裸聊馆精品妹妹 13. 日本欧美AV 14. av少妇人妻 15. 江门上门约 16. 电报引流｜持续增粉 17. 日本AV|高清无码 18. 义乌JK纯欲小妹妹外出品茶 19. 频道帖子浏览量｜群组上粉 20. 成都嫩妹上门服务 21. 内涵✨吃瓜娱乐🌱搞笑视频 22. 经典极品反差 23. 马来 修车高端外围 24. 日本无…
马云互推【频道A3】 最爱反差婊🌹爸爸你不要这样，小穴要裂开了，你都让女儿怀孕了！ 1. 忧伤的女孩子 2. 又是种草的一天 3. 49欲求不满的长腿巨乳嫂子 4. 🐶 晨光的母狗日记 5. 付费资源免费看的福利搜索引擎✅ 6. 你心中的欲望女孩 7. 有气质的老板娘 8. 商务女王 9. 美女私密写真 10. 大雪中的女孩子 11. 柏林引流｜Telegram引流增粉｜Telegram频道运营｜Telegram涨粉技巧｜推广方法 12. 反差素人约炮骚逼 13. 孙滢心预览 【孟婆来碗汤 】 14. 在公园里面爽爆了 15. 36老婆很保守 16. 电报零粉起步轻松涨粉 17. 43犯禁修女的折磨 18. 我想做你的🐶 19. 59把同事约到家里玩 20. 大爷，来玩呀！ 21. 小妖精魅力四射 好看的公众号🍑妈妈的屁股太大了，尤其是在练瑜伽的时候，爸爸太幸福了，可以天天👅我妈的大屁股🌹
1️⃣【凶器罩杯】：B+ 2️⃣【身高身材】：166 3️⃣【大概年纪】：30 4️⃣【 体重 】：105 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：姐姐人很好 好聊 不冷场，我们一起看电影吃东西像情侣一样 情绪价值拉满，服务也很周到 ，美好的一晚 下次还会找姐姐的
1️⃣【凶器罩杯】：B 2️⃣【身高身材】：160 3️⃣【大概年纪】：20 4️⃣【 体重 】：93 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：一直在找优秀的环保ls，今天找到西西，真的是来对了，所有细节拉满，老师的身材长相也是我喜欢的类型，皮肤很白，胸抓起来也很舒服，老师舌头口活超级顶，毒龙做的很到位，服务时间做满，真的很用心，必须反食
1️⃣【凶器罩杯】：A+ 2️⃣【身高身材】：165 3️⃣【大概年纪】：25 4️⃣【 体重 】：98 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：今天起得很早，在群里刷到妹子，一看还可以就私了老师，刚问老师是早上，老师说刚醒还没起床，她说她还没化妆问我介意不。我就过去了，没想到老师真的纯素颜，颜值太抗打了，长得太可爱了，太可爱呀，老师是自聊验证过，放心冲狼友们。
1️⃣【凶器罩杯】：B 2️⃣【身高身材】：167 3️⃣【大概年纪】：21 4️⃣【 体重 】：95 5️⃣【服务内容】： #一条龙💋#洗澡💦#调情 💦#舌吻💦#制服💦💦#口爆💦#深喉💦#69互动💦#胸推💦#臀推💦#独龙🐲💦#舔蛋💦#做爱💦#无套💦 狼友精选好评：妹子真人确实比图好看，身材瘦瘦的，但有料，我喜欢的类型，进门引诱我洗澡，一边口一边抚摸，舌头非常柔软，对着床边镜子那个画面感确实棒！可能是我太久没有做了，加上妹子太骚了，下面太紧了，水又多，换了几个姿势 我就射了，完事妹子也很耐心的陪我聊天，让我感觉挺放松的
Showing the 11 most recent of 11 posts we hold for @lomomo4464. 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 — 454,687 of 1,480,688entries 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.
Named by 8 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.
@lomomo4464 named 15 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“福州外围品茶” (@lomomo4464), 1,028 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lomomo4464.
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.