Channel
@amanogawa_jp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
599subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003095462048 |
|---|---|
| Type | Channel |
| Username | @amanogawa_jp |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/amanogawa_jp |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 45% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 20:01 | 599 | -6 |
| 7 Sept 2026, 03:17 | 605 | -5 |
| 28 Aug 2026, 21:34 | 610 | -3 |
| 14 Aug 2026, 14:36 | 613 | -5 |
| 7 Aug 2026, 23:16 | 618 | -1 |
| 7 Aug 2026, 04:00 | 619 | first reading |
11 posts held, back to 26 July 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 11 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
413 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 32.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5303409403599274429 | 134 | 32.4% | |
| custom 5303438523477538236 | 108 | 26.2% | |
| custom 5242611968270946371 | 88 | 21.3% | |
| custom 5240225559887236300 | 83 | 20.1% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 11 of the 11 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 413 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 26 July 2026 to 6 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.
✨ Секретные материалы ✨ 📍 Чуть-чуть показываем оригинал песни, под которую мы репетировали этот момент! 👛
custom 530340940359927442916custom 53034385234775382369custom 52402255598872363007custom 52426119682709463711
🌟 А это кусочки видеофона kawaikute gomen🌟 На самом деле, мы всегда в восторге от красивого оформления на фоне выступления и очень рады, когда на сцене есть возможность дополнить танец красивым видео 🫥 Такую красоту к нашим выступлениям делает Maneja и мы ей очень благодарны!!~
custom 524022555988723630013custom 53034385234775382369custom 53034094035992744297custom 52426119682709463714
Немного фотокарточек с прошедших двух фестивалей🎀 🌟На самом деле, те дни были очень насыщенные – мы потратили оочень много сил, но получили невероятное количество положительных эмоций!!~🌟 📍На Акамару у нас кстати был просто чудесный видеофон🧷
custom 530340940359927442916custom 52402255598872363008custom 53034385234775382368custom 52426119682709463713
✨ Убегать со сцены, держась за руки – становится маленькой традицией ✨
custom 530340940359927442922custom 524261196827094637113custom 52402255598872363009custom 53034385234775382364
❤️🤫🤫🤫🤫❤️ Мы даже не верим, что это произошло 🎀 👍 Наша первая тысяча звёздочек в Тиктоке 👍 📍За это время с нашей командой произошло так много всего – были и падения и подъемы, но больше всего мы рады что за этот год у нас появились вы и мы можем разделять эту мечту 🌟 Мы искренне благодарны вам за всю поддержку, любовь и теплые слова, что мы слышали на нашем пути ໒꒰˵- ˕ -˵꒱১ 🪽🪽🪽🪽🪽🪽 ❤️ Мы надеемся, что дальше буде…
custom 530340940359927442919custom 524022555988723630010custom 524261196827094637110custom 53034385234775382364
🧷🍥🍥🍥🍥🍥🍥 🍥🍥🍥🍥🍥🍥 🍥🍥🍥🍥🧷 📍А мы собрали немного наших общих эмоций от прошедшего в эту субботу фестиваля🎀 Благодарим каждого за приятные слова, поддержку во время выступления и, конечно, организаторов фестиваля за такое чудесное мероприятие и возможность выступить на сцене с j-pop кавером!!~ ⊹₊˚‧︵‿₊୨ᰔ୧₊‿︵‧˚₊⊹ Мы на самом деле очень любим записывать вложики и очень надеемся, что совсем скоро сможем открыть для себя бол…
custom 524022555988723630011custom 53034094035992744297custom 53034385234775382367custom 52426119682709463713
📍Это мы после фестиваля бежим к вам рассказывать как наши дела 💖
custom 524261196827094637123custom 530343852347753823611custom 52402255598872363007custom 53034094035992744292
А мы выступили второй раз с нашим танцем и очень были рады поддержке зала 𐔌՞ ܸ.ˬ.ܸ՞𐦯 На самом деле, каждое выступление для нас как в первый раз, это просто непередаваемые эмоции 👛 📍Были очень счастливы стать частью программы и выступить с нашим танцем, спасибо огромное за эту возможность организаторам фестиваля🎀🎀 ⭐⭐⭐⭐⭐⭐ Видеть фонарики и лайтстики со сцены во время выступления – что-то, что мы даже не можем описат…
custom 530340940359927442923custom 52402255598872363009custom 53034385234775382369custom 52426119682709463713
Video message, posted without a caption
custom 530343852347753823611custom 52426119682709463716custom 53034094035992744295custom 52402255598872363003
🧷Второй день активностей вместе с нами 🧷 Сегодня с удовольствием будем выступать на сцене Акамару Феста в 14:15 🌟 А пока готовимся, немного репетируем и бегаем по интересным стендам фестиваля!!~
custom 530343852347753823617custom 524261196827094637112custom 530340940359927442910custom 52402255598872363003
✨ Все: сколько нам нужно лайтстиков? ✨ Энчи: да 𑣲⋆
custom 530343852347753823619custom 524261196827094637110custom 53034094035992744297custom 52402255598872363003
Showing the 11 most recent of 11 posts we hold for @amanogawa_jp. 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.
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.
Named by 3 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Amanogawa️️ | 天の川 ⋆｡°” (@amanogawa_jp), 599 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/amanogawa_jp.
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.