일본10엔 너무 많아서 처치곤란입니다

Channel
일본인은 무엇을 좋아할까 : 가슴벅찬 텔레그램 채널
@japanhitomi
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,744subscribers
+27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002384741084 |
|---|---|
| Type | Channel |
| Username | @japanhitomi |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/japanhitomi |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 13:04 | 1,744 | +4 |
| 14 Aug 2026, 09:45 | 1,740 | +24 |
| 11 Aug 2026, 08:57 | 1,716 | -1 |
| 7 Aug 2026, 16:03 | 1,717 | no change |
| 7 Aug 2026, 15:28 | 1,717 | first reading |
Engagement
19 posts held, back to 3 August 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 · 30 days
- 29.4%
- avg views ÷ 1,744 subscribers
- Avg views / post
- 513
- 19 posts measured
- Reaction rate
- 0.502%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 19 held
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 17 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (3 August 2026 – 7 August 2026) |
| Views total | 9,756 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:03 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.
Reaction mix
46 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 26.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 26.1% | |
| 😍 | 7 | 15.2% | |
| 🤯 | 6 | 13.0% | |
| 🖕 | 4 | 8.70% | |
| 😁 | 4 | 8.70% | |
| 🤪 | 3 | 6.52% | |
| 🥰 | 3 | 6.52% | |
| 🔥 | 2 | 4.35% | |
| 🤣 | 2 | 4.35% | |
| 👎 | 1 | 2.17% | |
| 😱 | 1 | 2.17% | |
| 🤔 | 1 | 2.17% |
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 17 of the 19 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 3 August 2026 to 7 August 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.
Recent posts
냐냐냐냐냐냐냐 냐냐냐냐냐냐
❤4😍2
움짤을 만들었습니다 냐냐냐냐냐냐냐 냐냐냐냐냐냐냐
😍3❤1
일본은 어떤 나라일까..
❤5🖕2🤯2
챗봇인데 아틀리에 안해봐서모름 https://ryzachat-ai.go-spiral.ai/%E3%85%85%E3%85%82
🥰1
일본에서 AI와이프가 출시되었습니다
😍2🖕1
Photo, posted without a caption
😁4
생각해보니 바니의 날을 잊고 지나쳐버렸습니다. 치명적인 실수입니다. 대단히 면목없습니다. 죄송합니다.
🔥2👎1🖕1
아베도 기시다도 재난현장가면 이러는게 디폴트였다네요
🥰1
김정은까지 소환되는게 유우모어
🤯1
덴노 부부랑 비교되면서 극딜당하는 타카이치
일본인들 대부분이 소고기+미역국 조합은 상상도 못한다고 합니다 진짜...?
🤔1
Showing the 12 most recent of 19 posts we hold for @japanhitomi. 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
Citation-graph rank — 606,254 of 1,480,975entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“일본인은 무엇을 좋아할까 : 가슴벅찬 텔레그램 채널” (@japanhitomi), 1,744 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/japanhitomi.
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.