новая грвмшка вышла!! ⤵️ https://vt.tiktok.com/ZSpY79Gf3/
custom 5368375289371975550159custom 533696678624183330142custom 522898851669165077332custom 537069387592712699017custom 53368982643335911413

Channel
@linasfalv1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
10,768subscribers
+3,819 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002495644567 |
|---|---|
| Type | Channel |
| Username | @linasfalv1 |
| Description | всем приветики! я Лина, блогер💗🎀 основные темы здесь: ・ мода ・ красота ・ лайфстайл @linasfalvshop ←👚 реклама @linasfalvpr @linasfalvcooperation мой ТТ → https://www.tiktok.com/@linasfalv_?_t=8r40Xdk3Fe0&_r=1 мой ЛАЙК → https://l.likee.video/p/R98wPH |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/linasfalv1 |
Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 09:17 | 10,768 | +13 |
| 4 Nov 2026, 06:46 | 10,755 | +10 |
| 3 Nov 2026, 05:16 | 10,745 | +1 |
| 2 Nov 2026, 02:37 | 10,744 | +34 |
| 31 Oct 2026, 23:20 | 10,710 | +19 |
| 31 Oct 2026, 00:39 | 10,691 | +19 |
| 30 Oct 2026, 00:36 | 10,672 | +33 |
| 29 Oct 2026, 01:20 | 10,639 | +28 |
| 28 Oct 2026, 00:31 | 10,611 | +38 |
| 27 Oct 2026, 02:25 | 10,573 | +22 |
| 26 Oct 2026, 00:16 | 10,551 | +47 |
| 24 Oct 2026, 21:54 | 10,504 | +29 |
| 23 Oct 2026, 19:46 | 10,475 | +37 |
| 22 Oct 2026, 17:47 | 10,438 | +65 |
| 21 Oct 2026, 14:27 | 10,373 | +21 |
| 20 Oct 2026, 08:06 | 10,352 | +32 |
| 19 Oct 2026, 08:38 | 10,320 | +11 |
| 18 Oct 2026, 11:08 | 10,309 | +8 |
| 17 Oct 2026, 12:10 | 10,301 | +9 |
| 16 Oct 2026, 11:49 | 10,292 | first reading |
62 posts held, back to 1 August 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 26 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 62 (1 August 2026 – 5 November 2026) |
| Views total | 91,130 |
| Reactions total | 10,102 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 21:19 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.
Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 2 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.
23,789 reactions across 60 posts, in 63 distinct kinds. The most used accounts for 6.55% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5215404587401365088 | 1,558 | 6.55% | |
| custom 5906654512558382224 | 1,479 | 6.22% | |
| custom 5402378571224230056 | 1,371 | 5.76% | |
| custom 5188681923655920333 | 1,272 | 5.35% | |
| custom 5292084206199919122 | 1,244 | 5.23% | |
| custom 5312032877590911513 | 1,173 | 4.93% | |
| custom 4981204569120834506 | 721 | 3.03% | |
| custom 5337270045292667517 | 708 | 2.98% | |
| custom 5411379104689721446 | 675 | 2.84% | |
| custom 5411314396712443005 | 670 | 2.82% | |
| custom 5417846870170966806 | 622 | 2.61% | |
| custom 5370693875927126990 | 596 | 2.51% | |
| custom 6111693416591001596 | 585 | 2.46% | |
| custom 5391020620404264938 | 579 | 2.43% | |
| custom 5339409428632346149 | 541 | 2.27% | |
| custom 5228988516691650773 | 499 | 2.10% | |
| custom 5368746224222483392 | 497 | 2.09% | |
| custom 5435967521876386108 | 493 | 2.07% | |
| custom 5404429104575458733 | 461 | 1.94% | |
| custom 5291851882828943468 | 448 | 1.88% | |
| 43 further kinds | 7,597 | 31.9% |
Custom emoji. Every row above is a 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 60 of the 62 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 23,789 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 62 most recent posts we hold, published 1 August 2026 to 5 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @linasfalv1. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 62 most recent posts we hold for this entry, published 1 August 2026 to 5 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 2 of 18 posts held from the last 30 days (11.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
новая грвмшка вышла!! ⤵️ https://vt.tiktok.com/ZSpY79Gf3/
custom 5368375289371975550159custom 533696678624183330142custom 522898851669165077332custom 537069387592712699017custom 53368982643335911413
Video message, posted without a caption
custom 5370693875927126990365custom 5336966786241833301123custom 522898851669165077393custom 533689826433359114125custom 536837528937197555025
я просто изначально вообще хотела платье не розовое и не этот парик, но мне посылка с тао не доехала 😭 она уже в мск.. блина вот бы пришла до того момента, как у меня торт развалится
custom 5228988516691650773359custom 533689826433359114187custom 537069387592712699070custom 536837528937197555013custom 529185188282894346811custom 533696678624183330111
вчерашний макияж настолько имба, что я считаю мои липсинги достойны перевыкладки сюда делала блина фотки в платье, они мне не понравились, переделаю в другом!! ˚ ༘ ೀ⋆。˚🥵˚ ༘ ೀ⋆。˚ @linasfalv1 𑣲𝒿 (づ๑•ᴗ•๑)づ ⋆.ೃ🌟 ࿔
custom 5291851882828943468437custom 5370693875927126990137custom 536837528937197555090custom 533696678624183330116custom 522898851669165077315custom 533689826433359114115
linasfalv♡ (лина сфалв) pinned Deleted message
я сегодня весь день была в депрешен, поэтому праздновать др я буду не в др, а в др я поеду НА МАНИКЮР… который вообще-то должен был быть сегодня, эм да… буду 31 отмечать 🙂
custom 5215404587401365088463custom 5409357214475399080113custom 498120456912083450695custom 540932772093497547111custom 54114184981297656568custom 53369667862418333012
НЯВУШКА ПЕРВАЯ ПОЗДРАВИЛА НУ МОЯ В СОЛЛ
custom 4981204569120834506400custom 540932772093497547186custom 541141849812976565674custom 540935721447539908020custom 521540458740136508810
лина сфалв больше не бейбик, мне 18 ревем
custom 5215404587401365088550custom 4981204569120834506116custom 540935721447539908087custom 541141849812976565623custom 54093277209349754719custom 53706938759271269907
@linasfalv1 𑣲𝒿 ִֶָ. ..𓂃 ࣪ ִֶָ 🤩 ་༘࿐ •ﻌ•
custom 5215404587401365088535custom 5411418498129765656143custom 4981204569120834506110custom 540932772093497547118custom 540935721447539908016
🍫🍫離れないでいたいの夢を葉えて 🍫🍫➖➖➖➖➖➖𝔟𝔩𝔢𝔰𝔰 𝔪𝔢 𝔪𝔶 𝔞𝔫𝔤𝔢𝔩 💌 ˖ ₊⋆.˚⋆ ‧. ݁ ݁˚. ݁ 🤩 ⋆.˚໑ ݁༝ ۫ ׅ @linasfalv1 𑣲𝒿 .𖥔 ݁ 📚 ୭˚. 💡⋆✮⋆˚࿔
custom 6111693416591001596585custom 5409327720934975471186custom 6134110710629664650144custom 540935721447539908026custom 541141849812976565625
лайкаю все ваши коммы под видео до вечера, кто не напишет тот какашка 😊 (шучу)
custom 5368746224222483392310custom 540237857122423005664custom 518868192365592033356custom 540442910457545873323custom 536630784673449233211custom 539341200665506632511
https://vt.tiktok.com/ZSggmBkxG/ уснула в 7 вечера, поэтому выкладываю только сейчас эхх
custom 5393412006655066325231custom 518868192365592033356custom 540237857122423005644custom 536630784673449233214custom 53687462242224833925custom 54044291045754587335
Showing the 12 most recent of 62 posts we hold for @linasfalv1. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
We recorded 6 posts on @linasfalv1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“linasfalv♡ (лина сфалв)” (@linasfalv1), 10,768 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/linasfalv1.
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.