Channel
@lost_in_japan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
18,305subscribers
-45 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001183379773 |
|---|---|
| Type | Channel |
| Username | @lost_in_japan |
| Description | Япония и всё, что с ней связано! ⛩ Обратная связь, реклама: @frank_adv |
| Created | 31 August 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/lost_in_japan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 12:17 | 18,305 | -3 |
| 16 Aug 2026, 04:14 | 18,308 | -3 |
| 14 Aug 2026, 13:27 | 18,311 | -9 |
| 13 Aug 2026, 02:55 | 18,320 | -1 |
| 12 Aug 2026, 01:33 | 18,321 | -5 |
| 10 Aug 2026, 22:57 | 18,326 | -4 |
| 9 Aug 2026, 23:35 | 18,330 | -6 |
| 9 Aug 2026, 01:10 | 18,336 | -4 |
| 8 Aug 2026, 04:18 | 18,340 | -3 |
| 7 Aug 2026, 03:24 | 18,343 | -7 |
| 6 Aug 2026, 04:12 | 18,350 | no change |
| 6 Aug 2026, 03:45 | 18,350 | first reading |
10 posts held, back to 22 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 24 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 August 2026 |
|---|---|
| Posts held | 10 (22 July 2026 – 17 August 2026) |
| Views total | 15,986 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 16:44 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.
Lifetime counters from Telegram’s own channel header, read 17 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
⚡️🇷🇺 Разыгрываем билеты на концерт Канье Уэста в Питере! Всего подарим 5 билетов, потом вы их уже не достанете. Для участия нужно просто быть подписанным на @trendsetter и @lider и прожать кнопку «ХОЧУ НА КОПАТЫЧА» под постом. Победителей рандомно выберет бот ровно через 10 дней. Поехали! 🇷🇺🇷🇺🇷🇺
Вечер в историческом районе Хигаси Тяя, Каназава. Является крупнейшим сохранившимся районом в городе, где выступали гейши
Распыление холодной воды для охлаждения в жару по дороге в святилище Исияма-дера
❤️Признайтесь, вы же любите японскую культуру и хотите попасть в Японию? Для этого нужен базовый уровень японского языка хотя бы N5, ведь в Японии мало кто знает английский язык, тем более русский:) Хотим поделиться с вами авторской методологией, по которой японский учится намного легче! Регистрируйтесь на онлайн-курс "Японский для начинающих", это бесплатно😊 https://mnlp.cc/mini?domain=japanonline&id=24&utm_source…
Вход в святилище Акасака Хикава
Озеро Аойке в Японии — совершенно особенное, такое голубое, словно его искусственно раскрасили. На глубине 9 метров можно увидеть увядшие буки, лежащие под слоем темно-синей воды. Лучший сезон для посещения — с весны до лета, когда листья свежие. Вид Аойке, когда солнечные лучи просвечивают сквозь деревья, просто захватывает дух
Фигурные онигири
Храм Сэнсо-дзи в токийском районе Асакуса
Статуя Синего Дракона в храме Киёмизу-дера в Киото
Фото Токио 60-х годов
Showing the 10 most recent of 10 posts we hold for @lost_in_japan. 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 — 602,558 of 1,481,502entries 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Lost in Japan” (@lost_in_japan), 18,305 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/lost_in_japan.
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.