Channel
@Lupinchikarrrr
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
133subscribers
+12 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003281187082 |
|---|---|
| Type | Channel |
| Username | @Lupinchikarrrr |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/Lupinchikarrrr |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 19:55 | 133 | +6 |
| 31 Aug 2026, 13:03 | 127 | +5 |
| 24 Aug 2026, 18:55 | 122 | +1 |
| 9 Aug 2026, 04:01 | 121 | no change |
| 8 Aug 2026, 14:15 | 121 | first reading |
12 posts held, back to 4 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 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
56 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 51.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5278228031817656421 | 29 | 51.8% | |
| custom 5325958544544000861 | 10 | 17.9% | |
| custom 5298532223421555454 | 9 | 16.1% | |
| custom 5393116044753662289 | 6 | 10.7% | |
| custom 5244984302046841031 | 2 | 3.57% |
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 12 of the 12 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 4 August 2026 to 8 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.
Мне пришел паричок на Дотторе и я почти его уложила 😋 Давно не было контента в новых косплеях, так что хочети или не хочети контента с закосом Дотторе??
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 52782280318176564214custom 53259585445440008613custom 53931160447536622892
✨✨✨✨✨✨✨✨ 狐は狡猾なほど美しい。🦴 #椒丘. 🤍尻尾の裏に、狐の本心が隠れている。⭐ 🌟🌟🌟🌟🌟🌟🌟🌟 реак/рп?? #POST #cosplay #Jiaoqiu
custom 52782280318176564212
🤩🤩🌸🌱🌸🌿🌱🌸🌿🤩🤩🤩 🤩🤩🤩 🤩🤩 Куй, кузнец, пока горячо Было сердце - станет мечом 🤩🤩🤩 ⚡⚡⚡ 🤩🤩🤩 🤩🤩 🤩🤩🤩 Репост, мью? 🤩🤩🤩 #личноепубличное #магистр #косплей
custom 53931160447536622892custom 52782280318176564211
❤🐚🐚✅🔠🔠🔠⛈ 🩵🩵🩵❤️❤️❤️❤️❤️ — Вокс (me)🌟 — Вал💕🌟 ✨✨✨ #staticmoth #cosplay #hazbinhotel ✨✨✨✨✨
custom 52782280318176564212custom 52985322234215554542
🖤🖤🐚🐚✅🐚🐚🐚🖤🖤 ㅤㅤㅤㅤㅤㅤ🖤🖤🖤 •отсняли воксвалов) сегодняшним мемом была мой жопа, вокак •Вокси💙 •Валентино(me)🌟 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
custom 52782280318176564213
🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 ★::Се Лянь::★ 🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 Рт/реакции?) #Благословение_Небожителей #Косплей #СеЛянь
custom 52782280318176564213custom 52985322234215554542
Принесла вам даму. Не могу сказать что она меня сильно зацепила, я достаточно равнодушно к ней отношусь, но вам нарисовала) #монолог_фармацевта
custom 52985322234215554543custom 52782280318176564212
Первые 30 круток после ивент леги принесли мне второго Блэйда 🌟 Уж очень мне захотелось Анаксу (его я тоже выбила, но после 70+ крутки), короче удача Хуа Чэна не подводит
custom 53259585445440008615custom 52985322234215554542
Sticker, posted without a caption
custom 52782280318176564215custom 52449843020468410312custom 53259585445440008612
😀😀😀😀 😀😀😀😀 🇯🇵🇯🇵🇯🇵 🇯🇵🇯🇵🇯🇵🇯🇵 😀😀😀😀 ✦~｡ﾟ･⋆﹕🌸﹕⋆･ﾟ｡~✦ — 🤩 Тук-тук, есть кто дома? Улыбочку шире, сегодня праздник будет весёлым) ✦~｡ﾟ･⋆﹕🌸﹕⋆･ﾟ｡~✦ song: mzlff - чёртово колесо #cosplay #yaemiko #genshinimpact #genshin
custom 52782280318176564213
☑️☑️☑️☑️☑️☑️
custom 52782280318176564212custom 53931160447536622892
✧ ˚ · . МО СЮАНЬЮЙ . · ˚ ✧ ㅤㅤㅤㅤㅤㅤ𝐌𝐎 𝐗𝐔𝐀𝐍 𝐘𝐔 ━─━─────────────━─ 「 ᴧюди чᴀᴄᴛо ᴨиɯуᴛ нᴀ ɸонᴀᴩях ㅤㅤᴄʙои жᴇᴧᴀния, ʙᴇᴩя, чᴛо они доᴄᴛиᴦнуᴛ нᴇбᴇᴄ и будуᴛ ㅤㅤㅤㅤ ㅤㅤиᴄᴨоᴧнᴇны... 」 ᴀ ᴇᴄᴧи я ᴛожᴇ ᴨоᴨᴩобую? ʙдᴩуᴦ уᴄᴧыɯᴀᴛ... ━─━─────────────━─ ㅤㅤРт/реакции? ✦•···················•✦•···················•✦
custom 52782280318176564212
Showing the 12 most recent of 12 posts we hold for @Lupinchikarrrr. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Мне пришел паричок на Дотторе и я почти его уложила 😋 Давно не было контента в новых косплеях, так что хочети или не хочети контента с закосом Дотторе??
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 12 most recent posts we hold, published 4 August 2026 to 8 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“cosplay Люпинчикаrrr” (@Lupinchikarrrr), 133 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Lupinchikarrrr.
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.