Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑴.𝑻𝑶𝑲𝑰𝑶 𝑯𝒐𝒕𝒆𝒍

Channel

𝑴.𝑻𝑶𝑲𝑰𝑶 𝑯𝒐𝒕𝒆𝒍

@Tokio_Hotel_Model

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

166subscribers

+23 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-1003813569800
TypeChannel
Username@Tokio_Hotel_Model
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live1 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/Tokio_Hotel_Model

Growth

143166154.59 August 2026 — 143 subscribers9 August 2026 — 143 subscribers9 August 2026 — 145 subscribers17 August 2026 — 160 subscribers25 August 2026 — 157 subscribers1 September 2026 — 166 subscribers9 August 20261 September 2026
6 measurements spanning 23 days, net +23. 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 140–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 08:35166+9
25 Aug 2026, 02:07157-3
17 Aug 2026, 17:56160+15
9 Aug 2026, 21:12145+2
9 Aug 2026, 01:30143no change
9 Aug 2026, 01:17143first reading

Engagement

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

Reaction mix

316 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 22.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54698452446546833657222.8%
custom 54204851010771699814313.6%
custom 53773228830705779943912.3%
custom 53796476586735890563812.0%
custom 53844306158588056073812.0%
custom 5447439667286801603309.49%
custom 5298851902132342456288.86%
custom 5377653088746227376288.86%

Custom emoji. Every row above is a 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 9 of the 20 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 316 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 August 2026 to 9 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 20 we hold a reading for · 15%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Tokio_Hotel_Model. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 2 August 2026 to 9 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

9 Aug 2026, 00:30 UTC16 viewsread 9 August 2026

Очень нравится коллаба

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

9 Aug 2026, 00:29 UTC6 viewsread 9 August 2026
Forwarded from @Error_404Not_Found3File

File, posted without a caption

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

9 Aug 2026, 00:29 UTC6 viewsread 9 August 2026
Forwarded from @Error_404Not_Found3Sticker

Sticker, posted without a caption

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

9 Aug 2026, 00:29 UTC6 viewsread 9 August 2026
Forwarded from @Error_404Not_Found3Photo

🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔤RROR404 🔠 🔤ARRIS 😇😇And we go on ˚₊·— ‌‌‌♡ And we go on and on and on and on 🫥⭐⭐🌸We don’t belong °❀⋆.ೃ࿔*:・ ⭐⭐⭐⭐ We don’t belong, belong, belong ⭐⭐⭐⭐To anyone ࿔‧ ⁠⁠⁠˚˖𐦍˖˚⁠⁠⁠ ‧࿔ ⭐⭐⭐The pain of love will last forever 🔤🔤🔤Promise me ˖ ݁𖥔 ݁˖ 𐙚 ˖ ݁𖥔 ݁˖ 🔤🔤Promise me ˖ ݁𖥔 ݁˖ 𐙚 ˖ ݁𖥔 ݁˖ 🤩ᴠᴏʟᴜᴍᴇ : ▮▮▮▮▮▮▯▯▯

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

8 Aug 2026, 23:17 UTC13 viewsread 9 August 2026
Forwarded from @w1dnnfe1Photo

– Ну же, привет, котёнок 👋 В поисках красивых, горячих, ночных и атмосферных ботов по Tokio Hotel? Тогда ты заглянул куда нужно. 🤩десь тебя ждут любимые лица, интересные сюжеты, ночная эстетика и настроение, от которого так просто не уйти 🤩ыбирай своего фаворита, устраивайся поудобнее и оставайся дальше будет только интереснее. Click

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

7 Aug 2026, 19:21 UTC108 viewsread 9 August 2026

Мнение, звезды, рк. Всему буду благодарна. Мью отметка сюда.

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

7 Aug 2026, 19:20 UTC149 viewsread 9 August 2026
Sticker

Sticker, posted without a caption

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

7 Aug 2026, 19:20 UTC820 views62 reactions1 Starread 9 August 2026
Photo

🤩🤩🤩🤩🪦🪦🤩🪦🪦🤩🤩🤩 Я лежала под пылью и снегом. Меня звали ненужной давно. Но железо запомнило небо, Хоть его не касалось оно. Я скрипела от каждого ветра, Будто тело просило тепла. И в прожилках ржавого цвета Мне мерещилась алая мгла. Я лежала во тьме, неподвижно, Подбирая остатки тепла. Я молчала в холодном подвале. На поверхности старой стали. Как будто имя моё сохранил. 🪦🪦 Я дрожала от каждого звука, Я молчала, пока ме

custom 546984524465468336522custom 537732288307057799415custom 544743966728680160314custom 53776530887462273766custom 52988519021323424562custom 53796476586735890562custom 54204851010771699811

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

6 Aug 2026, 13:30 UTC186 views3 reactionsread 9 August 2026
Sticker

Sticker, posted without a caption

custom 53773228830705779943

Signed 𝙑𝙞𝙠𝙨𝙙𝙨 #шуба

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 3 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.

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

“𝑴.𝑻𝑶𝑲𝑰𝑶 𝑯𝒐𝒕𝒆𝒍” (@Tokio_Hotel_Model), 166 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/Tokio_Hotel_Model.

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.