Telegram RegisterThe public register of Telegram
Telegram profile photo for Li.Vi.An 🤍

Channel

Li.Vi.An 🤍

@livian09

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

155subscribers

+0 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-1002424311206
TypeChannel
Username@livian09
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/livian09

Growth

15513 Aug 2026, 00:48 — 155 subscribers14 Aug 2026, 07:57 — 155 subscribers13 Aug 2026, 00:4814 Aug 2026, 07:57
2 measurements spanning 1 day. 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 154–156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:57155no change
13 Aug 2026, 00:48155first reading

Engagement

16 posts held, back to 10 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 155 subscribers
Avg views / post
39.7
16 posts measured
Reaction rate
32.9%
reactions ÷ views · ER floor
Posts in window
16
of 16 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held16 (10 August 202612 August 2026)
Views total635
Reactions total209
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00:48 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.

Reaction mix

209 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 35.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7435.4%
custom 52380304880016063804521.5%
custom 6021613126166780450199.09%
custom 5370886904642303606188.61%
custom 5463168043683178995188.61%
custom 604207715497856899794.31%
custom 546091661323668281983.83%
🌚62.87%
❤‍🔥41.91%
👀41.91%
💋20.957%
🔥20.957%

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

Measured over the 16 most recent posts we hold, published 10 August 2026 to 12 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

12 Aug 2026, 18:01 UTC25 views7 reactionsread 13 August 2026
Photo

Cпокойной ночи Ливинация! Twt: @kiwofj #Harumasa

custom 52380304880016063805custom 53708869046423036061custom 60420771549785689971

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

12 Aug 2026, 15:01 UTC27 views9 reactionsread 13 August 2026
Photo

🥺 Х: @Konro_kon #Fairy #Yokai

4💋2custom 60216131261667804502custom 52380304880016063801

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

12 Aug 2026, 12:01 UTC32 views14 reactionsread 13 August 2026
Photo

Чего не сделаешь ради любимого Вайза ❤️ Twt: @oimo8929 #Sunna #Dialyn #Harumasa #Wise

6custom 54631680436831789956custom 60216131261667804502

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

12 Aug 2026, 09:01 UTC36 views10 reactionsread 13 August 2026
Photo

Как вы думаете, Фея получит свой облик? 👀 Twt: @yun_yun_cloud #Fairy #Belle

4custom 52380304880016063804❤‍🔥2

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

12 Aug 2026, 06:01 UTC37 views12 reactionsread 13 August 2026
Photo

C добрым утро! Twt: @mu_zz_404 #Harumasa

9custom 60216131261667804502custom 52380304880016063801

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

11 Aug 2026, 18:01 UTC43 views9 reactionsread 13 August 2026
Photo

Спокойной ночи 😌 Twt: @amdzz15_ #Wise #Belle

custom 537088690464230360642🔥2custom 60216131261667804501

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

11 Aug 2026, 15:01 UTC41 views14 reactionsread 13 August 2026
Photo

Вайз что-то удумал 👀 Twt: @nowbringa #Harumasa #Wise

custom 52380304880016063807custom 60420771549785689974❤‍🔥21

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

11 Aug 2026, 12:01 UTC43 views14 reactionsread 13 August 2026
Photo

🛐 Twt: @kiiru_rkgk #Wise

custom 54609166132366828196custom 53708869046423036064custom 523803048800160638031

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

11 Aug 2026, 09:01 UTC41 views14 reactionsread 13 August 2026
Photo

Каковы красавцы 🙏 Twt: @tonotsu_ #Wise #Harumasa

custom 52380304880016063808custom 53708869046423036063custom 60420771549785689973

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

11 Aug 2026, 06:01 UTC40 views13 reactionsread 13 August 2026
Photo

С добрым утром 🌟 Rednote: @26117805699 #Harumasa

5custom 53708869046423036065custom 60216131261667804503

Signed . ݁₊ 𝕳𝖚𝖗𝖒𝖆 ⊹.ᐟ

10 Aug 2026, 18:03 UTC46 views17 reactionsread 13 August 2026
Photo

Фу быть таким ленивым и забывчивым владельцем как я, но что уж поделать. Этот канал вывозят только мои любимые админы🌷 Сладких снов вам, котятки💋 Х: @takashinayuu #Harumasa

custom 5463168043683178995124custom 52380304880016063801

Signed Livian

10 Aug 2026, 15:02 UTC47 views21 reactionsread 13 August 2026
Photo

КАКОЙ ЖЕ ВАЙЗ СЛАДЕНЬКИЙ, КАК ЕГО ВООБЩЕ МОЖНО СЪЕСТЬ 😭😭😭 Х: @oimo8929 #Wise #Harumasa

16custom 52380304880016063803custom 54609166132366828192

Signed Livian

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

Citation-graph rank — 1,465,021 of 1,481,306entries 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.

Forward network

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

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

“Li.Vi.An 🤍” (@livian09), 155 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/livian09.

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.