Telegram RegisterThe public register of Telegram
Telegram profile photo for ЖигаЖизнь

Channel

ЖигаЖизнь

@bucketravel

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

109subscribers

+0 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-1001852393139
TypeChannel
Username@bucketravel
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/bucketravel

Growth

108109108.59 August 2026 — 109 subscribers9 August 2026 — 109 subscribers17 August 2026 — 108 subscribers11 September 2026 — 109 subscribers9 August 202611 September 2026
4 measurements spanning 33 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 108–109 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 19:56109+1
17 Aug 2026, 09:45108-1
9 Aug 2026, 19:21109no change
9 Aug 2026, 18:16109first reading

Engagement

7 posts held, back to 30 June 2026the 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 7 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

22 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1463.6%
😁522.7%
313.6%

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 6 of the 7 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 30 June 2026 to 9 July 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.

Recent posts

9 Jul 2026, 15:52 UTC44 views3 reactionsread 9 August 2026
Photo

РеальнаЯпония #Япония #Срачъ

👍21

7 Jul 2026, 18:21 UTC54 views4 reactionsread 9 August 2026
Photo

«Я на стул сел - мне уже должны» - так однажды пошутил мой коллега в начале рабочего дня. Или не шутил? Сложно сказать… Вот будь мы японцами - эти слова звучали бы абсолютно серьезно! Реально, я не шучу) Такую историю расскажу. На одну международную конференцию по развитию компьютерных технологий и защите компьютерных программ приехали переводчики из разных стран. И вот после работы встречает наш переводчик своег

👍2😁2

6 Jul 2026, 16:37 UTC55 views5 reactionsread 9 August 2026
Photo

Там же и березки растут, какая милота) Япония прекрасна! #Япония #Norikura

👍32

6 Jul 2026, 16:31 UTC56 views2 reactionsread 9 August 2026
Photo

А, нет, это ещё не всё, тема японской кухни оказывается неисчерпаема) Warabi わらび Катался по лесным тропинкам в нацпарке Норикура и смотрю народ шастает по полю с корзинками, чёт высматривают в траве, словно грибники. Но какие грибы в начале июня? Один дядечка сам ко мне подошел, поинтересовался, мол, с какого района и вообще. Я, в свою очередь, спросил шо это он там собирает… Оказалось, собирают такое растеньице

👍2

2 Jul 2026, 19:13 UTC71 views4 reactionsread 9 August 2026
Photo

Ну и в завершение темы японской кухни, рубрика Подножный корм Недалеко от Токио попалось ранее невиданное дерево с такими вот ягодками. Что это такое я не знал, поэтому пробовал с осторожностью. Даже на пальцах спросил местного японца можно ли их есть? Получив на тех же пальцах предсказуемый ответ что есть нельзя, я продолжил поедание) Ягодки вкусные, кисло-сладкие, внутри косточка как у черешни. Клевая штука для

😁3👍1

2 Jul 2026, 19:10 UTC59 viewsread 9 August 2026
Photo

Японские микроапельсины - как ещё один противовес здоровенным яблокам) На вкус не особо сладкие, может недозрели чуток, но вообще норм! #Япония #яблоки

30 Jun 2026, 19:05 UTC61 views4 reactionsread 9 August 2026
Photo

Как японцы кормили меня Подкармливали) Такое бывало в предыдущих поездках, как я говорю, туристов везде любят) А в этот раз меня кормили дважды, и один эпизод запомнился особо. Токио. Прогноз обещал ночью дождь и не обманул. Поэтому вечером я искал лавочку под крышей. И нашел! Но нашел её не я один: к моменту моего появления, там уже спал японский бомж. Блин( Что делать? Да ничего! Прилег рядом просто на бетон,

👍4

Showing the 7 most recent of 7 posts we hold for @bucketravel. 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.

Mentions

Named by 1 registered channel — 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.

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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“ЖигаЖизнь” (@bucketravel), 109 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/bucketravel.

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.