Telegram RegisterThe public register of Telegram
Telegram profile photo for 🎀☀️I Love Vi ka☀️💐🎀

Channel

🎀☀️I Love Vi ka☀️💐🎀

@LoveViKALoveViKA

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

29subscribers

-1 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003952959777
TypeChannel
Username@LoveViKALoveViKA
CreatedBetween 1 April 2026 and 25 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/LoveViKALoveViKA

Growth

29313013 August 2026 — 30 subscribers13 August 2026 — 30 subscribers26 August 2026 — 31 subscribers11 September 2026 — 29 subscribers13 August 202611 September 2026
4 measurements spanning 29 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 29–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 07:5629-2
26 Aug 2026, 09:5331+1
13 Aug 2026, 15:0730no change
13 Aug 2026, 08:0330first reading

Engagement

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

What this channel posts

Video runtime
32s
Average length
32s

Measured directly from 1 video 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.

Reaction mix

28 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5206454309348196935725.0%
custom 5465568393530722370725.0%
🔥414.3%
custom 5465147890462640190310.7%
💋310.7%
custom 520402946530215640813.57%
👍13.57%
😍13.57%
🥰13.57%

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

Measured over the 5 most recent posts we hold, published 25 July 2026 to 11 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.

Recent posts

11 Aug 2026, 15:33 UTC8 views6 reactionsread 13 August 2026
Photo

Лето, подружки, велики и сладости — идеальный день! ☀️🍬 Кто тоже так проводит каникулы? ✌️

custom 52064543093481969352custom 54651478904626401902custom 52040294653021564081custom 54655683935307223701

8 Aug 2026, 14:27 UTC13 views5 reactionsread 13 August 2026
Photo

Учёба подождёт, сейчас время для вайба ✌️😎⚡️

💋2🥰1😍1custom 52064543093481969351

6 Aug 2026, 08:46 UTC19 views5 reactionsread 13 August 2026
Photo

Немного солнца, пластырь на пальце, но улыбка никуда не делась! ☀️ Привет от Вики!

custom 52064543093481969353💋1custom 54655683935307223701

31 Jul 2026, 11:41 UTC31 views5 reactionsread 13 August 2026
Photo

Жёлтый арбуз — какая неожиданность! 💛 Какая сладость! 🍉

🔥4custom 54655683935307223701

25 Jul 2026, 20:21 UTC38 views7 reactionsread 13 August 2026
Photo

Всем привет! 👋 Сегодня решил(а) достать маркеры и дать волю творчеству. 🎨 Как вам мои новые персонажи? Разноцветный монстрик или Патрик с шариками? Пишите в комментариях, кто понравился больше! 😊✨

custom 54655683935307223704👍1custom 52064543093481969351custom 54651478904626401901

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

Forward network

Republished by

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

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 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.

“🎀☀️I Love Vi ka☀️💐🎀” (@LoveViKALoveViKA), 29 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/LoveViKALoveViKA.

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.