Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐿𝑖𝑜𝑟𝑎

Channel

𝐿𝑖𝑜𝑟𝑎

@Liora_veil

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

27,474subscribers

-290 since we began measuring on 15 September 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002451353578
TypeChannel
Username@Liora_veil
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 September 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Liora_veil

Growth

27,47427,76427,61915 September 2026 — 27,764 subscribers15 September 2026 — 27,764 subscribers16 September 2026 — 27,677 subscribers18 September 2026 — 27,474 subscribers15 September 202618 September 2026
4 measurements spanning 3 days, net -290. 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 27,431–27,808 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:1627,474-203
16 Sept 2026, 02:5627,677-87
15 Sept 2026, 04:2227,764no change
15 Sept 2026, 03:4727,764first reading

Engagement

43 posts held, back to 3 September 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 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.3%
avg views ÷ 27,474 subscribers
Avg views / post
3,650
43 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
43
of 43 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 27 September 2026
Posts held43 (3 September 2026 – 27 September 2026)
Views total157,131
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 20:27 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.

What this channel posts

Photos
127
Videos
125
Links
28

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

26 Sept 2026, 20:30 UTC≈1,020 viewsread 27 September 2026

میك‌لاو باید جوري باشه که نفس کم بیاري ولي از بوسیدنِ لباش سیر نشي.

26 Sept 2026, 19:53 UTC42 viewsread 26 September 2026

میك‌لاو باید جوري باشه که نفس کم بیاري ولي از بوسیدنِ لباس سیر نشي.

24 Sept 2026, 22:18 UTC≈2,360 viewsread 27 September 2026
Photo

⠀ ⠀ ⠀ ⠀ ⠀‌‌‌‌⠀ ‌‌ ⠀‌‌‌‌‌‌‌‌⠀ ‌‌‌‌‌⠀ ‌𝗆𝖾 ₊ 𝗒𝗈𝗎

24 Sept 2026, 20:34 UTC≈2,360 viewsread 27 September 2026

یه پوزیشن 69ـمون نشه؟! هم من واست بخورم هم تو واسه من بخوري.

24 Sept 2026, 20:29 UTC≈2,350 viewsread 27 September 2026
Photo

⠀ ⠀ ⠀ ⠀ ⠀‌‌‌‌⠀ ‌‌ ⠀‌‌‌‌‌‌‌‌⠀ ‌‌‌‌‌⠀ ‌𝗆𝖾 ₊ 𝗒𝗈𝗎

23 Sept 2026, 21:17 UTC≈2,670 viewsread 27 September 2026

همین که صورتمو لاي پاهات مي‌بیني اثباتِ اینه که چقدر دوستت دارم.

23 Sept 2026, 12:29 UTC179 viewsread 23 September 2026

خب چالش داریم چالش شات از سکس چتاتون با رلتون شات بدین بزارم چنل ببینیم چخبره تو پیوی رلاتون شاتای ارسالی در - > @Shatoli 💋

22 Sept 2026, 22:01 UTC168 viewsread 23 September 2026

خب چالش داریم چالش شات از سکس چتاتون با رلتون شات بدین بزارم چنل ببینیم چخبره تو پیوی رلاتون شاتای ارسالی در - > @Shatoli 💋

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

Posts edited after publishing

@Liora_veil edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
27 September 2026
Most recent edit
27 September 2026

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

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

“𝐿𝑖𝑜𝑟𝑎” (@Liora_veil), 27,474 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Liora_veil.

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.