Ровно год назад ❤️🌟
🥰44custom 529671198192175464829❤19❤🔥10🎉5custom 52897712159871649662

Channel
@tokyotrip_ru
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
9,404subscribers
-184 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002112878337 |
|---|---|
| Type | Channel |
| Username | @tokyotrip_ru |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/tokyotrip_ru |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 19 Sept 2026, 01:57 | 9,404 | -4 |
| 14 Sept 2026, 21:00 | 9,408 | -14 |
| 10 Sept 2026, 21:41 | 9,422 | -28 |
| 5 Sept 2026, 10:18 | 9,450 | -25 |
| 1 Sept 2026, 22:55 | 9,475 | -31 |
| 30 Aug 2026, 02:45 | 9,506 | -22 |
| 26 Aug 2026, 22:53 | 9,528 | -35 |
| 23 Aug 2026, 22:25 | 9,563 | -2 |
| 20 Aug 2026, 04:54 | 9,565 | -1 |
| 16 Aug 2026, 21:56 | 9,566 | +9 |
| 13 Aug 2026, 09:56 | 9,557 | -8 |
| 10 Aug 2026, 12:53 | 9,565 | -25 |
| 7 Aug 2026, 06:10 | 9,590 | +2 |
| 6 Aug 2026, 20:31 | 9,588 | first reading |
16 posts held, back to 2 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 34 pages of 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 28 August 2026 |
|---|---|
| Posts held | 16 (2 August 2026 – 28 August 2026) |
| Views total | 1,810 |
| Reactions total | 192 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 06:02 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.
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.
1,462 reactions across 16 posts, in 18 distinct kinds. The most used accounts for 39.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 581 | 39.7% | |
| ❤🔥 | 354 | 24.2% | |
| custom 5296711981921754648 | 109 | 7.46% | |
| 🥰 | 105 | 7.18% | |
| custom 5289771215987164966 | 100 | 6.84% | |
| 😍 | 88 | 6.02% | |
| 😁 | 60 | 4.10% | |
| 👍 | 11 | 0.752% | |
| 🎉 | 10 | 0.684% | |
| custom 5389022378279842177 | 8 | 0.547% | |
| 👏 | 7 | 0.479% | |
| 😭 | 6 | 0.41% | |
| 🤩 | 6 | 0.41% | |
| 🔥 | 5 | 0.342% | |
| 🍾 | 4 | 0.274% | |
| 🤔 | 4 | 0.274% | |
| ⚡ | 2 | 0.137% | |
| 🏆 | 2 | 0.137% |
Custom emoji. 3 of the rows above are 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 16 of the 16 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 1,462 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 2 August 2026 to 28 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.
Ровно год назад ❤️🌟
🥰44custom 529671198192175464829❤19❤🔥10🎉5custom 52897712159871649662
Друзья, мне не хватит слов ни на русском, ни на английском, ни на японском, чтобы выразить свои чувства касательно нашей поездки, поэтому я выберу язык фактов: вы просто обалденная команда (в самом прямом смысле этого слова), мне было с вами очень комфортно, весело и приятно проводить время. К сожалению, я далеко не тот человек, который оказывается своим в доску со всем коллективом, но я очень рада, что нашла здесь с…
❤🔥47❤24🥰8😭2custom 52897712159871649662
🎤🎶 боже, 3 ЧАСА ПОДРЯД прощального караоке в такоой атмосфере… обожаем лето подходит в концу и наша поездочка тоже 💔 место, люди, атмосфера – все сошлось, не передать словами хочется своё караоке открыть в Токио 😅
❤🔥40😍18❤14custom 52967119819217546486custom 52897712159871649663🔥2🏆1custom 53890223782798421771
🍥🍜 Фанаты Наруто, АТЕНШН ❗️Рядом с Токио есть настоящая Коноха …и мы там побывали 😍 Недавно ездили в парк аттракционов Fuji-Q Highland у подножия Фудзи, а внутри него – целая деревня NARUTO × BORUTO Тут можно погулять по маленькой Конохе, пофоткаться с Наруто, Саске и другими героями, закупиться мерчем, а главное… 🍜 зайти в Ichiraku Ramen и попробовать тот самый рамен Наруто! Ресторан специально сделали по мотива…
❤🔥41❤14🥰10custom 52897712159871649669custom 52967119819217546483
Обещай, что поедешь со мной в Японию смотреть 花火
❤🔥87🥰27❤16custom 52897712159871649669custom 52967119819217546485😭2
✖️⛩️Съездили в Кавагоэ – скрытую жемчужину рядом с Токио! а это самый атмосферный город около Токио, всего 30 минут 🚃🚃🚃 А тут прям атмосфера Цусимы или Сёгуна Его называют «маленьким Киото», здесь столько всего сохранилось: 🟠деревянные домики 🟠старые храмы 🟠улочки эпохи Эдо 🟠башня Токино Канэ, ей 400 лет 🟠маленькие магазинчики а еще зашли в один из таких локальных магазинчиков – мастерскую колец glänta Kawagoe …
❤51custom 529671198192175464811👏4❤🔥3custom 52897712159871649661custom 53890223782798421771
хейтеры скажут ИИ (новый символ на Одайбе)
❤64😁38custom 529671198192175464820custom 52897712159871649668👏2🤔2⚡1🤩1
ОНА 😍 признайтесь все тоже залипли
❤81❤🔥46😍24custom 52897712159871649669🤔2😭2custom 52967119819217546482⚡1
смотрите какие красивые!! ❤️🔥👘
❤63😍34custom 528977121598716496619❤🔥4🎉4
❤️🔥В этом году 7 человек приехали во второй раз! Сняли рилс про них →
❤43❤🔥16custom 529671198192175464813custom 52897712159871649667🔥1😍1
хорошо когда можно положиться на токиотрип.
❤40😁19custom 52967119819217546487custom 53890223782798421773custom 52897712159871649662
Photo, posted without a caption
❤🔥42custom 528977121598716496613custom 529671198192175464810❤6🤩5😁3🎉1🏆1
Showing the 12 most recent of 16 posts we hold for @tokyotrip_ru. 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.
Named by 9 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.
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.
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 7 seed channels' Telegram-generated recommendation lists 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“TokyoTrip • Учеба и жизнь в Японии ⛩” (@tokyotrip_ru), 9,404 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/tokyotrip_ru.
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.