Telegram RegisterThe public register of Telegram
Telegram profile photo for Luraine

Channel

Luraine

@liyo67

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

50subscribers

+26 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1003920177923
TypeChannel
Username@liyo67
CreatedBetween 1 April 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 17 September 2026
On Telegramt.me/liyo67

Growth

24543915 August 2026 — 24 subscribers15 August 2026 — 24 subscribers24 August 2026 — 54 subscribers31 August 2026 — 50 subscribers5015 August 202631 August 2026
4 measurements spanning 16 days, net +26. 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 20–59 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 13:2650-4
24 Aug 2026, 17:4754+30
15 Aug 2026, 17:0024no change
15 Aug 2026, 16:4524first reading

Engagement

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

Reaction mix

142 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 18.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓2618.3%
custom 54452644510349481952014.1%
🦄1913.4%
🎉1812.7%
custom 5463148810819628138149.86%
🕊149.86%
💘128.45%
🐳96.34%
42.82%
👀42.82%
🆒21.41%

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

Measured over the 18 most recent posts we hold, published 5 August 2026 to 14 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

14 Aug 2026, 21:52 UTC26 views12 reactionsread 15 August 2026
Photo

Ну симпатично выглядит ? Это скетч если что

🎉7🕊32

14 Aug 2026, 17:20 UTC25 views4 reactionsread 15 August 2026
Forwarded from @POPOTIK_13Photo

🤍🤍🤍🤍🤍🤍🤍🤍 👁🔤🔤🔤🔤🔤🔤🔤 🔤🔤 🔤🔤 🔤🔤🔤🔤🔤🔤🔤🎁 🅰️ — Попотик, худ самоучка. Канал посвящён моему творчеству и ОС😐😐. 🅰️олноценки, скетчи и видео вы увидите здесь. В основе тут мои персы, но будут и другие фд (жжк, игры от хоё и т.д.🙂) 🤍🤍🤍🤍🤍🤍🤍🤍 🧦е против мью / вз пиара (5+ пдп) связь со мной только через анон. 🌟🌟🌟🌟🌟🌟🌟🌟 \ ВП ПОСТ | НАВИГАЦИЯ /

🕊2🆒1custom 54631488108196281381

14 Aug 2026, 17:20 UTC21 views6 reactionsread 15 August 2026
Forwarded from @lizvxlPhoto

╭─────── < < < 🥹 Добро пожаловать в . . . « Храм Сукунафага » ! 🌟🌟 (( 😺 )) Я Хассен, художник-самоучка, и этот канал полностью посвящен моему творчеству. Основной фандом — магическая битва (жжк), но могут мелькать и другие Коллабы, трейды — по желанию Реквесты — 💔 Коммишки — ❤️ DNI:: антисш, хейтеры жжк Anon 🥹 shitpost 🥹 commissions 🥹 boost Не против мью / взаимного п

🕊32custom 54631488108196281381

14 Aug 2026, 15:11 UTC28 views10 reactionsread 15 August 2026
Photo

Коллаба с @UniL1na

custom 54631488108196281385🦄3🍓2

9 Aug 2026, 23:25 UTC37 views13 reactionsread 15 August 2026
Photo

Уже давно хочу закончить , но руки не доходят , да и надо скетч переделать чуть 🙂

🦄6custom 54631488108196281385🐳2

7 Aug 2026, 13:52 UTC44 views6 reactionsread 15 August 2026

МНЕ ОЧЕНЬ НРАВИТСЯ 💕💕

🎉5🦄1

7 Aug 2026, 13:51 UTC41 views11 reactionsread 15 August 2026
Forwarded from @Feran0lPhoto

Подарок для @liyo67

🐳5👀4🦄2

6 Aug 2026, 16:03 UTC51 views17 reactionsread 15 August 2026
Photo

Вот так я раньше рисовала 😐

🍓7🦄7custom 54452644510349481953

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

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 3 registered channels — 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.

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

“Luraine” (@liyo67), 50 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/liyo67.

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.