Telegram RegisterThe public register of Telegram
Telegram profile photo for 日本🇯🇵韩国

Channel

日本🇯🇵韩国

@hanguoribe

On this record: Growth · Engagement · Posts · Cite this entry

107subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001867999501
TypeChannel
Username@hanguoribe
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 3 September 2026
On Telegramt.me/hanguoribe

Growth

1061081076 August 2026 — 107 subscribers7 August 2026 — 106 subscribers9 August 2026 — 106 subscribers14 August 2026 — 107 subscribers22 August 2026 — 108 subscribers28 August 2026 — 107 subscribers6 August 202628 August 2026
6 measurements spanning 21 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 106–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 03:34107-1
22 Aug 2026, 02:39108+1
14 Aug 2026, 09:15107+1
9 Aug 2026, 08:46106no change
7 Aug 2026, 22:00106-1
6 Aug 2026, 22:42107first reading

Engagement

3 posts held, back to 17 June 2026the 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 3 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Jul 2026, 11:10 UTC99 views0 reactionsread 9 August 2026
Photo

🇯🇵新人一次来菲,hrio ●身高(身長):163 ●體重(体重):41 ●罩杯(カップ数):G ●年紀(年齢):22 ●真胸或假奶(豊胸ありなし):あり ●下面是否有除毛(下の毛処理):有り 会讲韩语 ■extra ⭕️❌でお答えください 舌吻LG(ディープキス):⭕️ 小親(フレンチキス):⭕️ 無套口交(生フェラ):⭕️ 無套性交(NS):⭕️ 内射(中出し):⭕️ 69 :⭕️ 毒龍(アナル舐め)⭕️ 口爆(口内射精)⭕️ 肛交(アナルファック): ❎ 2女一男(雙飛)(3P):⭕️ 二男一女(逆3P):❎ 舔乳头(乳首舐め):⭕️ 舔B(クンニ):⭕️ 自拍撮影(撮影):⭕️ 脸部射精(顔射):❎ 工作细节 90分钟一次 ( 50000p ) 3个小时两次 ( 80000p ) 8个小时三次 ( 160000p )

5 Jul 2026, 11:10 UTC82 viewsread 9 August 2026
Photo

日本🇯🇵新茶,女优yukari 身高161,体重48kg,胸围F,年纪25 喜欢口爆吹箫,气质美女 ■サービス面⭕️❌でお答えください 無套口交(生フェラ):⭕ 無套性交(NS): ⭕ 内射(中出し): ⭕ 69 :⭕ 毒龍(アナル舐め)⭕ 口爆(口内射精): ⭕ 肛交(アナルファック): ❌ 2女一男(雙飛)(3P):⭕ 二男一女(逆3P):⭕ 舔乳头(乳首舐め): ⭕ 舔B(クンニ):⭕ 自拍撮影(撮影):❌ 脸部射精(顔射):⭕ 工作细节 90分钟一次 ( 50000p ) 3个小时两次 ( 80000p ) 8个小时三次 ( 160000p ),无套,拍摄另收小费

17 Jun 2026, 08:27 UTC138 views0 reactionsread 9 August 2026
Photo

韩国🇰🇷🇰🇷🇰🇷新人 名字:kuki 身高:165 年龄:25 体重:44 胸围:C 鸳鸯浴,🉑口交,🉑69🉑3p🉑双飞 🉑SM+5000🉑无套➕2万p,🉑服务好 皮肤好 90分钟50000p一次 6小时80000p 二次 12小时150000p三次

Showing the 3 most recent of 3 posts we hold for @hanguoribe. 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.

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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“日本🇯🇵韩国” (@hanguoribe), 107 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/hanguoribe.

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.