Channel
@awaiyume
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
255subscribers
-26 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002886770985 |
|---|---|
| Type | Channel |
| Username | @awaiyume |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/awaiyume |
Travel — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 11 Oct 2026, 14:19 | 255 | -4 |
| 30 Sept 2026, 19:56 | 259 | -3 |
| 16 Sept 2026, 03:36 | 262 | -5 |
| 8 Sept 2026, 13:01 | 267 | -9 |
| 31 Aug 2026, 04:53 | 276 | -1 |
| 23 Aug 2026, 22:04 | 277 | -1 |
| 16 Aug 2026, 22:24 | 278 | -3 |
| 8 Aug 2026, 08:32 | 281 | no change |
| 7 Aug 2026, 19:04 | 281 | first reading |
4 posts held, back to 29 April 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 4 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
эта была одна из самых атмосферных поездок в камакуру за все время.. 🤩раньше всегда передвигалась по ней исключительно пешком (ну или на энодене/автобусе, если нужно было далеко ехать), но в этот раз мы с подругой арендовали велосипеды и теперь будем делать только так! 🤩 с утра позавтракали в 🤩 кафе недалеко от станции, затем объездили кучу храмов, а ближе к вечеру поехали к пляжу☁️ ☕️ перед возвращением пр…
наша очередная поездка в камакуру!🫐🌟
любимая чайная в самом сердце мегуро🌟✉️
скоро летоо🌟🌟 в том году была невыносимая жара под 40‘, спасало только эстетическое удовольствие🐈
Showing the 4 most recent of 4 posts we hold for @awaiyume. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“淡い夢” (@awaiyume), 255 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/awaiyume.
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.