15 Jul 2026, 07:51 UTC74 viewsread 9 August 2026
Photo
🤏🏼🥹
Channel
Han Jihoon
@hoonxtws
On this record: Growth · Engagement · Posts · Citations · Cite this entry
95subscribers
-26 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003659543961 |
|---|---|
| Type | Channel |
| Username | @hoonxtws |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/hoonxtws |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 06:59 | 95 | +2 |
| 30 Aug 2026, 02:36 | 93 | -3 |
| 23 Aug 2026, 06:57 | 96 | -17 |
| 15 Aug 2026, 15:33 | 113 | -8 |
| 9 Aug 2026, 03:47 | 121 | no change |
| 7 Aug 2026, 19:32 | 121 | first reading |
Engagement
7 posts held, back to 29 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 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 7 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
1 Jul 2026, 12:38 UTC190 viewsread 9 August 2026
Photo
260701 @.tws_pledis Instagram Update 🚨💥 with Kyungmin
30 Jun 2026, 13:06 UTC156 viewsread 9 August 2026
Photo
260630 @.tws_pledis Twitter Update 이 부장님이 찍은 사진 별로야... 내 마음속의 별로…★
30 Jun 2026, 13:02 UTC194 viewsread 9 August 2026
Photo
260630 @.begins_official_ Instagram Update 𝘽𝙇𝙀𝙈𝙄𝙎𝙃 𝙎𝙏𝙍𝙄𝙆𝙀 🎳 𝘄𝗶𝘁𝗵 𝗧𝗪𝗦💙 비긴스 : 순한 사용감에, 그렇지 못한 파워풀 효능! TWS : 풋풋한 얼굴에, 그렇지 못한 프로페셔널함! 어쩐지 닮은 우리..💗💙 7일 만에 흔적 잡는 잡티샷세럼으로 얼룩덜룩한 색소 침착과 잡티는 물론, 칙칙한 피부톤과 트러블 후 남은 흔적까지! 완벽하게 𝗕𝗟𝗘𝗠𝗜𝗦𝗛 𝗦𝗧𝗥𝗜𝗞𝗘!💥 ✔ 나이아신아마이드 10% ✔ 순도 글루타치온 99% ✔ 알파-알부틴 2%
30 Jun 2026, 09:10 UTC205 viewsread 9 August 2026
Photo
GMP Airport 260630
29 Jun 2026, 06:52 UTC141 viewsread 9 August 2026
Photo
'24/7:FOR:YOU' IN SEOUL PRESS PHOTO
29 Jun 2026, 06:52 UTC132 viewsread 9 August 2026
Photo
Photo, posted without a caption
Showing the 7 most recent of 7 posts we hold for @hoonxtws. 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.
Mentions
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Han Jihoon” (@hoonxtws), 95 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/hoonxtws.
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.