Channel
@vivilalav0
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002312429453 |
|---|---|
| Type | Channel |
| Username | @vivilalav0 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/vivilalav0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 09:01 | 10 | -1 |
| 26 Aug 2026, 02:53 | 11 | +1 |
| 12 Aug 2026, 10:33 | 10 | no change |
| 10 Aug 2026, 21:17 | 10 | first reading |
17 posts held, back to 4 April 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 17 posts for this entry, the most recent from 12 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.
Серелиз ты очень хорошо поешь, но ты не репер Тера хорошо читаешь рэп, но нету эмоций в практиках Мицу ты шикарно поешь в свои года!! я уверена в будущем ты будешь сиять!! Амико ты не репер Виви хорошо, но гармоний слишком много Хими ты хороша, почти попала Лэйн норм Сливка красиво поешь, не репер Миззи молодец Киен шикарна!! почти попала Нацуко не совсем репер
🤍 ➤ 𝒢rαsⲓαs あ trυe 𝔅P 🤩 ✨ Yoυ cαn't control the wαy I ժrⲓp う り𝔄υժⲓtⲓon 🎤⩇⩇ blαckpⲓnk🥹 🎀 tαken : ℛose 〢free : ᨵt3 🥹🥹 grαsⲓαs ℳiα more 🤩 𝔔uestⲓonnαⲓre & rυles ⲓn cᨵmm | bot tαgs : #audition #grasias #covergroup
🎀𝐀𝜐d 🇪🇸@offside_cov : 🥹 🇪🇸true soccer 🤎 OFF 🥹🇦🇷- oh my goddess what happen with KCA 🎀🎀➿➖🎀🎀➖➿🎀 🥹🔡REE— ronaldo, mbappe, kane, neymar, yamal 🤍 🥹🔡ake: σ𝕥1 ( jude) 🤍🎀 𝓐𝗻︢︣𝗸︪︩𝝴ׅ𝘁ֺsׅ 𐐼𝗻︢︣𝗱 ɾ𝗎𝗹𝝴ׅsׅ ı𝗻︢︣ 𝗰ׅᦅ𝗺𝗺🎀 aww🥹🤩🤩🤩🤩🤩🤩🤩 🎀🎀➿➖🎀🎀➖➿🎀 do u play with me?🎀
хотяб в кандидаты
💝ЛИСТ КАНДИДАТОВ!!!🤩 💝💝спасибо всем тем , кто подавал к нам заявку ! мы очень любим вас 🩷🩷
ᅠⓘ 𝖨𝗍'𝗌 𝔄𝗎𝖽Ꭵ𝗍𝗂𝗈𝗇 /. 📕 정은𝖥𝗈𝗎ղ∂ᧉɾ * ᅠ💎· 𝖳𝗁𝖾 𝗐𝗈𝗈∂𝗌 ɾᧉ𝗆𝖾𝗆ɓ𝖾𝗋 𝖾𝗏ᧉɾ𝗒𝗍𝗁Ꭵ𝗇𝗀. ᅠ𝖳αӄ𝖾ղ : 𝖲ᧉ𝗎𝗀𝗇𝗆Ꭵ𝗇 & 𝖧𝗒𝗎𝗇𝗃Ꭵ𝗇 & 𐋏ᥲᥒ ⌗.❤️ ᅠ« 𝖥ɾᧉ𝖾 —— 𝖮𝗍5 .🍄╷ 𝖦ɾα𝗏Ꭵ𝗍𝗒 𝔉α𝗅𝗅𝗌 ᅠ 사렁🎁 › ℑ𝗇𝖿𝗈 𝖨𝗇 𝖢𝗈𝗆𝗆ᧉղ𝗍𝗌 ! @.looӄ ᅠ' 𝖥α𝗅𝗌ᧉ ɾ𝖾α𝗅Ꭵ𝗍𝗒. » t.me/Oufnder : 🎁. ᅠ . #𝖠𝗎∂𝗂𝗍Ꭵ𝗈𝗇 ﹙🎩﹚#𝖥𝗈𝗎ղ∂ᧉɾ ›ᅠ
📰NEW 🎀over🤩#hot ?¿? YOU&ME(jennie) -i love u and me #cover🔤иви @vivilalav0 _*
🎀 🤩 ‘𝐀𝗎∂𝗶𝗍𝗶𝗼𐓣 ㋦ 𝗖Ꮏ𝗋ɭ + Ⲍ 🤩 🎀 𝗪𝖾𝗹𝖼σ𝗺𝖾 𝘁𝗈 🤩 𝗰𝗍𝗿𝗅 + 𝗓 🎀 🎀 · – ➿ · — · ➿ – · 🎀 🎀🎀🎀 𝐒𝖾𝗮𝗋𝗰𝗁𝗶𐓣𝗴 !! 🎀🎀 ❤️ 𝗌𝗵𝗎𝗵𝘂𝖺 : 𝗌𝗼𝗈𝗷𝗂𐓣 : [ 𝗪hσ ?? ] 🎀 𝐓𝘄𝖾𐓣𝗍𝘆 ❤️𝗳𝗈𝘂𝗋 𝘀𝖺𝗺𝖾 𝗌𝗵𝖺𝗱𝖾 𝐀𝗅𝗹 𝗶𐓣𝗳𝗈𝗿𝗆𝗮𝗍𝗶𝗈𐓣 𝗶𐓣 𝗰𝗈𝗺𝗆𝗲𐓣𝘁𝗌 🎀 · – ➿ · — · ➿ – · 🎀 🎀 𝗪𝖾𝗹𝖼σ𝗺𝖾 𝘁𝗈 🌹 𝗰𝗍𝗿𝗅 + 𝗓 🎀 🌹 | 𝖢𝘁𝗋𝗹+𝗓 𝗀𝗿𐐫𝘂𝗉 !!
у меня тут кст новое видео
𝒱iv͟i͟lalav#rap pinned a video
📰NEW 🎀over🤩#hot ?¿? PINKY UP-(KATSEYE) - Pinky UP! #cover🔤иви @vivilalav0 _*
🎀🤩𝔠𝔬ɭɭαϸ𝔬𝔯𝔞𝔱𝔦o̤̤n̤̤🌟🌟#ศรีตรัง 🔤ong: 𝔐ONO🌿 씨바* 0.002? @vusalesh_kca & @vivilalav0 -ᴍɪxɪɴɢ ʙʏ ᴠᴜsᴀʟᴇsʜᴋᴀ -ᴄᴏʟᴏᴜʀ ᴄᴏᴅᴇᴅ ʟʏʀɪᴄs ʙʏ ɴᴀʀᴋᴏʟᴏᴋ -ᴛᴇxᴛ ᴘᴏsᴛ ʙʏ ᴠɪᴠɪ REACTIONS*. & coMMENTS🎀
Showing the 12 most recent of 17 posts we hold for @vivilalav0. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“𝒱iv͟i͟lalav#rap” (@vivilalav0), 10 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/vivilalav0.
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.