Channel
@lv868923
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
52subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002319588485 |
|---|---|
| Type | Channel |
| Username | @lv868923 |
| Created | Between 1 September 2024 and 30 November 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/lv868923 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 17:55 | 52 | -1 |
| 24 Aug 2026, 23:37 | 53 | -1 |
| 16 Aug 2026, 14:37 | 54 | -1 |
| 10 Aug 2026, 08:16 | 55 | no change |
| 7 Aug 2026, 14:05 | 55 | first reading |
13 posts held, back to 30 November 2024 — 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 13 posts for this entry, the most recent from 5 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
8 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 62.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 62.5% | |
| 👍 | 2 | 25.0% | |
| 💋 | 1 | 12.5% |
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 5 of the 13 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 30 November 2024 to 5 January 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.
#東京23區 #外約酒店 💖 名前：薫（かおる） 💖 スペック：158cm、45kg、Dカップ、20歳 💖 体型特徴：かおるちゃんは、清純で小柄な若い女性です。大きなバストが好みの方には合わないかもしれませんが、彼女のサービス精神と協力的な態度は素晴らしいです。彼女はパートタイムで働いていますが、満足していただけると思います 📱TG： @hu532 ⭐️Gleezy：w23231 ————————————— ⭐️初心者向けのヒント ⭐️お客様のフィードバック 🔥ワンクリックでKitano Worldに参加しましょう 🔥東京の老年ドライバー・AV女優交流会
❤1
日本風俗出差旅行找小姐：@hu532 ✅見面滿意 現金消費 ✅本人照片 ⭐️東京出張： t.me/hubl521 ⭐️大阪出張： t.me/gd19811 在日本🇯🇵需要找小姐的可以找北野 @hu532
🇯🇵东京のジャンル別女性紹介【高端】外送茶上门服务 pinned «https://t.me/gd19811»
🇯🇵 美亚 170cm 50kg Ecup 27岁 强力推荐 大奶骚骚女生 高挑美腿诱惑你 巨乳と高身長のセクシーな女の子があなたを誘惑します 💟可接待外国客 💟外国人ゲストにも対応可能 💟LINE https://line.me/ti/p/DHfRLlMuui 💟预约 @gd19810 💟午夜场 @gd19814 📌营业时间：上午11:00-晚上24:00 现金消费 不需要押金 不接受汇款
❤2💋1
https://t.me/gd19811
许岁月一个回眸，愿清浅的岁月里，风景依然，初心依旧。祝大家圣诞节快乐呀。。。！
渡生活的难，谢时光的暖，让喜欢的事情成为生活。境随心转，把自己变成糖，生活就甜了。
人闲情绪多，百忙解千愁。 有目标的人在奔跑， 没目标的人在流浪。 好与不好都是生活， 尽力就好，允许所有的事与愿违。
👍1
美咲：167cm E+cup 49kg 25歲 服务地区：东京23区 她不僅長得溫柔 還熱愛運動 常常去健身放鍛鍊曲線 身材練得緊實誘人呢 穿了白色緊身小背心和褲裝的運動造型 曲線超級吸睛 ミサキ：身長167cm、Eカップ、体重49kg、25歳 サービスエリア：東京23区 彼女は優しい容姿だけでなく、スポーツやフィットネスにも熱心で、美しいボディラインを維持しています。白のタイトなタンクトップとパンツのスポーツウェアを着こなし、セクシーで魅力的な曲線美を披露しています。 Misaki: Height - 5'6", E-cup, 108 lbs, Age - 25 years old Service area: Tokyo's 23 special wards She not only has a gentle appearance but also loves sports. She often goes to t…
❤1
詩織：164cm 50kg E+ 24歲 服务地区：东京23区 爆乳米咖 堅挺自然的傲人雙峰 免費奶炮享受全自動的優質服务 積極主動的 好色正妹 詩織：164cm、50kg、Eカップ、24歳 サービスエリア：東京23区 爆乳で美巨乳、形の良い自慢の双丘。 無料で乳射を楽しめる、全自動のハイクオリティサービス。 積極的で淫乱な美少女。 Shiori: 164cm, 50kg, E-cup, 24 years old Service area: Tokyo's 23 wards A buxom beauty with firm and natural assets. Enjoy a free breast shot with a fully automated premium service. An active and eager lover. ✈️純粋で素敵な狼友達✈️ 🆔LINE：https://line…
❤1👍1
战袍已准备好了 哥哥来加入战斗吧~😍 戦闘の準備は整いました。さあ、兄さん、一緒に戦いましょう。😍
菜菜子：163cm 48kg D+ 25歲 服务地区：东京23区 清純慾女 長相清純身材豐盈本性饑渴浪蕩 想要純純的愛意來呵護她 喜歡挑逗你 讓你慾火焚身 ななこ：身長163cm、体重48kg、Dカップ、25歳 サービスエリア：東京23区 清純な顔立ちと豊満なプロポーションを持つ彼女は、本来は情熱的で色っぽい女性。純粋な愛に包まれて、大切にされたいと願っている。あなたをからかうことが好きで、あなたを欲望で燃え上がらせるでしょう。 Nanakko: 5'4", 105 lbs, D+, 25 years old Service area: Tokyo's 23 wards Innocent and lustful, Nanakko has a pure look but a voluptuous body that's always thirsty for more. She wants a pure love to …
Showing the 12 most recent of 13 posts we hold for @lv868923. 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.
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.
@lv868923 named 4 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵东京のジャンル別女性紹介【高端】外送茶上门服务” (@lv868923), 52 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/lv868923.
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.