Channel
@L_nea
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
110subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002139571556 |
|---|---|
| Type | Channel |
| Username | @L_nea |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/L_nea |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 07:16 | 110 | no change |
| 6 Aug 2026, 22:02 | 110 | first reading |
13 posts held, back to 2 June 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 pageof 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 13 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 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.
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.
103 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 36.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5307842441208937672 | 38 | 36.9% | |
| custom 5287510620080447506 | 24 | 23.3% | |
| custom 5217887782873095075 | 20 | 19.4% | |
| custom 5407027838962385537 | 13 | 12.6% | |
| custom 5406952707099475585 | 7 | 6.80% | |
| custom 5253487830486760910 | 1 | 0.971% |
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 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 13 of the 13 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 103reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 2 June 2026 to 9 July 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.
кашалот, лнеа — плюшевые игрушки Вызвали по фамилии, голос взбодрил приёмный покой… слушать
custom 53078424412089376728custom 52178877828730950751custom 52534878304867609101
кто сделает пресейф - найдет завтра под подушкой айфон
custom 52178877828730950756custom 52875106200804475061custom 54069527070994755851
это первая моя проба в совместном творчестве, которая получилась, и я очень горжусь тем, что я залетела к этим крутым ребятам !!!! это мясо, клянусь !
custom 53078424412089376724custom 52178877828730950751custom 54069527070994755851
сюрприз там я буду. ПРЕСЕЙВИМ УМОЛЯЮ !!!
custom 52178877828730950755
ПРЕСЕЙВ
custom 53078424412089376724
дузья, прощупываю почву, пробую\ищу новый звук, если есть биты, демки, че поглазеть\залететь попробовать можно, жду в лс срочно ! https://t.me/lneaneas
custom 52875106200804475064
kitssvie.ru
custom 53078424412089376728custom 54070278389623855375custom 52875106200804475063custom 54069527070994755853
ph: kitssvie
custom 53078424412089376729custom 52875106200804475064custom 54070278389623855374
ого !
custom 52875106200804475061
кашалот — сегодня Пуговичка выпрыгивает из засаленной петельки… слушать
custom 52178877828730950754custom 52875106200804475062
Черно-белый пазл жанрового баланса, конструктор, собранный по схеме, нарисованной на песке теплых воспоминаний, интроспективная анемоя на стыке всего. ПРЕСЕЙВ
custom 52875106200804475064custom 54070278389623855373
Video message, posted without a caption
custom 53078424412089376725custom 52875106200804475062custom 54069527070994755852
Showing the 12 most recent of 13 posts we hold for @L_nea. 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 — 471,096 of 1,169,250entries 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.
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 2 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Lnea” (@L_nea), 110 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/L_nea.
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.