Channel
@lukaclaude
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
15subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003999596957 |
|---|---|
| Type | Channel |
| Username | @lukaclaude |
| Created | Between 1 April 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lukaclaude |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:45 | 15 | no change |
| 7 Aug 2026, 03:15 | 15 | first reading |
20 posts held, back to 30 June 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 1 pageof 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. It is computed over the 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (30 June 2026 – 6 August 2026) |
| Views total | 28 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 23:45 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 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
32 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 71.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357163144101784916 | 23 | 71.9% | |
| 💘 | 5 | 15.6% | |
| custom 5330535536572525301 | 2 | 6.25% | |
| 🍓 | 1 | 3.13% | |
| 💋 | 1 | 3.13% |
Custom emoji. 2 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 areTelegram’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 12 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 32reactions 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 30 June 2026 to 6 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.
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 💕обрый вечер, дорогие читатели моего блога. Сегодня закончился мой отпуск... И я отлично провела время, фу-фу~ 💕автра надо рано приезжать на работу, поэтому, мне нужно закругляться с разбором вещей после отпуска и лечь спать. А пока можете о чем-нибудь спросить~ 🎀🎀🎀🎀🎀🎀🎀🎀
💘1
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
🌟🌟 ＝ 𝐖𝐀𝐈𝐓 ❗️ ⋮ 🥹 ︶⏝ ❓ #𝓻𝐞𝐬𝐭 ⎯ׅ⎯ׄ ໒ ۫🤩🤩 ᛝ Кто-то из сотрудников наконец-то выпросил отпуск у Мику! Пожелаем удачи ? 🥹 ⇉ мегурине лука ⵂ @lukaclaude ♡ 12.О7 - О6. О8 ⌢ִ⃔ ₎ ˗ˏˋ ⎯ׅ⎯ׄㅤ ִ֮ просьба не беспокоить сотрудника до окончания его отпуска и дать отдохнуть ! ︶🐟
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 💕ука стремительно бродила по магазину обуви, выискивая новые сапожки по акции. От нее доносились фразы вроде "мм, такие классные... В следующий раз схожу и куплю", либо "ой, Кайто, а тебе бы подошла эта обувь..." 💕пустя где-то полчаса беготни по магазину, она уже готовилась идти к кассе и купить себе... Три пары обуви. Сапожки, босоножки и туфельки на каблуках. Она посмотрела на Кайто и у…
custom 53571631441017849161
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 💕ука улыбнулась и впихнула ему половину пакетов - один набит одеждой, другой - какими-то коробками, а третий - всякой всячиной, видимо, украшения в коробочках. — Ну, пойдем, мне нужно сапожки купить. Если хочешь, за помощь могу и тебе чего-нибудь взять~ 🎀🎀🎀🎀🎀🎀🎀🎀
custom 53571631441017849164🍓1💋1
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 — А я думала ты рад.. 💕ука хихикнула и повернулась к цветам... Так, интерьер... Хм, белая роза. Подойдёт.. 💕евушка подошла к продавцу, вежливо попросив о белой розе. Лука думала - мол, в вазочку поставит и будет красота. 💕огда Лука оплатила розу, она повернулась в сторону Кайто. — Раз уж так... Не поможешь немного с пакетами? Мне ещё нужно в несколько отделов зайти, а у меня рук совсем…
custom 53571631441017849163💘1custom 53305355365725253011
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 💕на рассмеялась. Да, он был абсолютно прав. Что раньше она таскалась по дорогущим магазинам, что сейчас. 💕слышав слова Кайто о его работе, она удивилась и склонила голову набок. Интересно... Неужели правда? — Да лаадно! Я только недавно туда су-шефом устроилась, представляешь? Вот это ничего себе совпадение~ 💕ука хмыкнула, уставившись с хитрой улыбкой на Кайто. 🎀🎀🎀🎀🎀🎀🎀🎀
custom 53571631441017849163💘1custom 53305355365725253011
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 💕ел обычный выходной. Но... Куда потратить целый день? Неужели опять на шоппинг? Не опять, а снова. 💕евушка уже пол дня гонялась по магазинам за новыми брендами - обувь, духи, одежда, платья, часы... Чего только она не купила за один вечер.... 💕сталось зайти за цветами. Давненько Лука не покупала живые цветы... Нужно это исправить. 💕ройдя в магазин цветов, Мегурине посмотрела на свои ру…
custom 53571631441017849163
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 Лука, если я вас позову на свидание, то пойдете со мной? Ваша Мику💋. 💕ику? Что же, я подумаю... У меня обычно много дел, и я, наверно, откажусь... 🎀🎀🎀🎀🎀🎀🎀🎀
custom 53571631441017849162
ㅤㅤㅤㅤㅤ🎀😍🎀ㅤㅤㅤㅤ 🤩🤩🤩ㅤㅤㅤㅤ🤩🤩🤩🤩 лука ! ты успела уже познакомиться с другими в ресторане ?? надеешься ли ты , что ты можешь кого то из знакомых встретить там ? 💕ет, ещё не успела. Завтра я должна познакомиться со всем персоналом, и думаю, это будет весело~ 💕накомых? Не думаю, что мои знакомые будут работать в ресторане... Жизнь, все таки, полна сюрпризов. Вдруг встречу кого нибудь? 🎀🎀🎀🎀🎀🎀🎀🎀
custom 53571631441017849163
Showing the 12 most recent of 20 posts we hold for @lukaclaude. 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 — 1,232,329 of 1,336,469entries 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“𓏵ㅤㅤ𝓛𝓾𝓴𝓪 𝓜𝓮𝓰𝓾𝓻𝓲𝓷𝓮” (@lukaclaude), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lukaclaude.
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.