Telegram RegisterThe public register of Telegram

Channel

лина квазар

@l1nnaz

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

286subscribers

+2 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001898393693
TypeChannel
Username@l1nnaz
CreatedBetween 1 November 2022 and 31 July 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/l1nnaz

Growth

2842862859 Aug 2026, 21:16 — 284 subscribers10 Aug 2026, 16:04 — 286 subscribers9 Aug 2026, 21:1610 Aug 2026, 16:04
2 measurements taken within a single day, net +2. 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 284–286 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:04286+2
9 Aug 2026, 21:16284first reading

Engagement

20 posts held, back to 25 July 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
117.4%
avg views ÷ 286 subscribers
Avg views / post
336
20 posts measured
Reaction rate
8.87%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 9 August 2026
Posts held20 (25 July 20269 August 2026)
Views total6,718
Reactions total596
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 21:16 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

596 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 30.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 579402308832461452718130.4%
custom 545891138749546391313823.2%
custom 527155276787643118410517.6%
custom 5335000769257042565396.54%
custom 5285086068092200921355.87%
custom 5334740030382427455345.70%
custom 5211020576843395074223.69%
custom 5467692899103699674193.19%
custom 532351762443537879491.51%
🦄71.17%
custom 535731970424966141050.839%
custom 545839718971582023410.168%
10.168%

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

Measured over the 20 most recent posts we hold, published 25 July 2026 to 9 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

9 Aug 2026, 19:53 UTC69 views17 reactionsread 9 August 2026

храни господь славу кпсс

custom 545891138749546391311custom 52850860680922009213custom 57940230883246145273

Signed ム лина квазар₊⊹

6 Aug 2026, 21:13 UTC181 views23 reactionsread 9 August 2026
Forwarded from @mirosa44enko

я вознеслась от нового альбома ксб

custom 546769289910369967411🦄5custom 53347400303824274555custom 54589113874954639132

Signed ム лина квазар₊⊹

6 Aug 2026, 09:59 UTC258 views26 reactionsread 9 August 2026
Photo

дэкаонтурточкару

custom 527155276787643118418custom 579402308832461452761custom 54589113874954639131

Signed ム лина квазар₊⊹

5 Aug 2026, 15:47 UTC280 views47 reactionsread 9 August 2026

Posted without readable text

custom 533474003038242745524custom 579402308832461452710custom 54589113874954639138custom 52715527678764311842custom 52850860680922009211custom 53350007692570425651custom 54676928991036996741

Signed ム лина квазар₊⊹

5 Aug 2026, 11:18 UTC261 views27 reactionsread 9 August 2026

блин забанили в чате жанны кашенцовой о нет мой дом все пропало

custom 545891138749546391320custom 52715527678764311844custom 53350007692570425652custom 57940230883246145271

Signed ム лина квазар₊⊹

4 Aug 2026, 06:31 UTC314 views47 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 545891138749546391328custom 52850860680922009218custom 54676928991036996747custom 57940230883246145273custom 52715527678764311841

Signed ム лина квазар₊⊹

3 Aug 2026, 11:08 UTC381 views34 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 579402308832461452724custom 53347400303824274554🦄2custom 54589113874954639132custom 52715527678764311841custom 53350007692570425651

Signed ム лина квазар₊⊹

2 Aug 2026, 12:20 UTC328 views28 reactionsread 9 August 2026
Forwarded from @kuplinovtochkaruv

у меня не теневой бан,просто я снимаю хуйню

custom 528508606809220092122custom 53350007692570425654custom 53235176244353787942

Signed ム лина квазар₊⊹

1 Aug 2026, 19:37 UTC454 views51 reactionsread 9 August 2026
Photo

на фон уже сил не хватает айм соу сори

custom 545891138749546391331custom 579402308832461452711custom 52715527678764311846custom 52110205768433950743

Signed ム лина квазар₊⊹

1 Aug 2026, 16:38 UTC372 views47 reactionsread 9 August 2026

Posted without readable text

custom 579402308832461452725custom 52110205768433950749custom 53350007692570425656custom 54589113874954639133custom 52715527678764311842custom 53347400303824274551custom 53573197042496614101

Signed ム лина квазар₊⊹

1 Aug 2026, 05:19 UTC285 views24 reactionsread 9 August 2026
Forwarded from @ug_404Photo

Photo, posted without a caption

custom 579402308832461452716custom 52110205768433950744custom 52715527678764311844

Signed ム лина квазар₊⊹

31 Jul 2026, 08:53 UTC351 views39 reactionsread 9 August 2026
Photo

luv<3

custom 533500076925704256523custom 57940230883246145278custom 53573197042496614104custom 54589113874954639133custom 54583971897158202341

Signed ム лина квазар₊⊹

Showing the 12 most recent of 20 posts we hold for @l1nnaz. 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 — 804,212 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.

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

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

“лина квазар” (@l1nnaz), 286 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/l1nnaz.

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.