11 Aug 2026, 09:17 UTC1 viewsread 11 August 2026
Photo
ꕀ #Denonbu ‧₊ .ᐟ Tokyo Dennou выступят на Gold Disc ~ ㅤ
Channel
Hamu-chan was here! ໒꒱₊˚
@Ichigorinahamu
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
21subscribers
-3 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003840473235 |
|---|---|
| Type | Channel |
| Username | @Ichigorinahamu |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Ichigorinahamu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:01 | 21 | -1 |
| 31 Aug 2026, 11:59 | 22 | -1 |
| 24 Aug 2026, 12:04 | 23 | -1 |
| 11 Aug 2026, 10:45 | 24 | no change |
| 9 Aug 2026, 04:15 | 24 | first reading |
Engagement
6 posts held, back to 1 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 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 6 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 14s
- Average length
- 7s
Measured directly from 2 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.
Recent posts
4 Aug 2026, 02:05 UTC8 viewsread 11 August 2026
Скорее всего, это небольшой бэкстейдж к будущему клипу. Недавно в сторис, Хаму упоминала, что снимает клип в Англии 🇬🇧
4 Aug 2026, 02:01 UTC8 viewsread 11 August 2026
Photo
˚₊‧ 「 обновление инст сторис певицы MARiMARi с Хаму 」 ㅤ
2 Aug 2026, 05:14 UTC11 viewsread 11 August 2026
Photo
₊ ᨦ rinahamu ꕀ iNST ‧₊ .ᐟ 𝒻𝒾𝓇𝓈𝓉 𝑒𝓃𝑔𝓁𝒶𝓃𝒹 𝓈𝒽𝑜𝓌 🇬🇧 𝓉𝑜𝓀𝓎𝑜 𝒹𝑒𝓃-𝓃𝑜𝓊 𝓈𝓎𝓃𝒸 𝓉𝒽𝒶𝓃𝓀 𝓎𝑜𝓊 ♡໒꒱ 01.08_#SNS ㅤ
1 Aug 2026, 03:56 UTC6 viewsread 11 August 2026
Photo
₊ ᨦ rinahamu ꕀ iNST ‧₊ .ᐟ Ранее𓂃 ࣪˖ ִֶཐི༏ཋྀ 31.07_#SNS ㅤ
1 Aug 2026, 03:54 UTC5 viewsread 11 August 2026
Photo
₊ ᨦ rinahamu ꕀ iNST ‧₊ .ᐟ Хаму, Почи и Ями набили одинаковые татуировки ~ _#SNS ㅤ
Showing the 6 most recent of 6 posts we hold for @Ichigorinahamu. 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.
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.
Mentions
Named by 10 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.
ೃ ܹ ꒰꒰۪֟︶݄Twil4ght.Toku. ꠥ۫ ׅ 𓐇۪ۜܵ ݂ ৎ୭
@TW1L4T0KU · 233 posts血オ66
@chio66_off · 562 postsFRUITS ZIPPER FAN [REST]
@fruitszipperfan · 3101 postワンsachu 𖧷 ˚｡
@kakkoestkdaily · 1571 postྀི𝓵ove for atom | daily
@ki_ki_Atom · 761 postMADOROMI / マドロミ
@madoromiinfo · 2461 postmiuholic
@mydearmiu · 1461 postPiKi
@PiKi_fan · 1311 post^𝗋𝗂𝗇𝗆𝗈𝗄𝖺 𝖽𝗎𝗈!!^
@rinmokaduo · 121 post𝐍AKASO 🐈⬛
@Uokochan · 201 post
@TW1L4T0KU · 233 posts血オ66
@chio66_off · 562 postsFRUITS ZIPPER FAN [REST]
@fruitszipperfan · 3101 postワンsachu 𖧷 ˚｡
@kakkoestkdaily · 1571 postྀི𝓵ove for atom | daily
@ki_ki_Atom · 761 postMADOROMI / マドロミ
@madoromiinfo · 2461 postmiuholic
@mydearmiu · 1461 postPiKi
@PiKi_fan · 1311 post^𝗋𝗂𝗇𝗆𝗈𝗄𝖺 𝖽𝗎𝗈!!^
@rinmokaduo · 121 post𝐍AKASO 🐈⬛
@Uokochan · 201 post
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Hamu-chan was here! ໒꒱₊˚” (@Ichigorinahamu), 21 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Ichigorinahamu.
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.