Telegram RegisterThe public register of Telegram
Telegram profile photo for OnLyYuSuKe吃喝玩樂都最高

Channel

OnLyYuSuKe吃喝玩樂都最高

@yusukelove

On this record: Topic · Growth · Engagement · Posts · Cite this entry

12subscribers

+1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001273846329
TypeChannel
Username@yusukelove
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live15 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/yusukelove

Topic

Travel — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 15 November 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.

Growth

111211.58 August 2026 — 11 subscribers12 August 2026 — 11 subscribers15 November 2026 — 12 subscribers8 August 202615 November 2026
3 measurements spanning 100 days, net +1. 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 11–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 17:0712+1
12 Aug 2026, 08:1511no change
8 Aug 2026, 00:2211first reading

Engagement

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

Recent posts

21 Jun 2026, 02:36 UTC3 viewsread 12 August 2026

你們可能從來沒想過旅遊居然還能抽100萬! 那不就是一年可以繼續飛持續飛✈️的概念嗎? 平台大福利,粉絲專屬 滿額「單筆」5000元就抽,需要透過我提供粉絲的優惠連結才能參與抽獎。 https://yusuke.pse.is/98h2j5 只到6/30 那個如果您幸運抽到100萬大獎,記得包紅包🧧給我嘿! 特別選在我40歲生日這天發表好消息,祝大家都是幸運兒☘️

2 Apr 2026, 04:04 UTC8 viewsread 12 August 2026

我覺得人最重要的是堅持,我不保證你們繼續當我粉絲會得到什麼? 但我確信的事情是沒繼續進行追蹤我真的是很大的損失😐 https://yusuke.com.tw/blog/post/okinawa-american-village

5 Jan 2026, 03:38 UTC9 viewsread 12 August 2026

https://yusuke.com.tw/blog/post/okinawa-tk05-chatan-gateway

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

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

“OnLyYuSuKe吃喝玩樂都最高” (@yusukelove), 12 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/yusukelove.

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.