Channel
@lindreamhynlix
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
183subscribers
+17 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002578739474 |
|---|---|
| Type | Channel |
| Username | @lindreamhynlix |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/lindreamhynlix |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 21:41 | 183 | -1 |
| 8 Sept 2026, 09:15 | 184 | -1 |
| 31 Aug 2026, 00:26 | 185 | +9 |
| 23 Aug 2026, 08:17 | 176 | +7 |
| 15 Aug 2026, 20:48 | 169 | +2 |
| 9 Aug 2026, 01:31 | 167 | +1 |
| 8 Aug 2026, 16:01 | 166 | no change |
| 8 Aug 2026, 06:30 | 166 | first reading |
15 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 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 15 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
138 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 37.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5251476149409716621 | 52 | 37.7% | |
| custom 5253449394824455086 | 47 | 34.1% | |
| custom 5132104976595682370 | 28 | 20.3% | |
| custom 5294461659576832255 | 11 | 7.97% |
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 14 of the 15 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 138 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 1 August 2026 to 8 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.
мы с вами кстати потеряли очень много реакшен, так что проголосуйте, кому не жалко, за канальчик пожалуйста https://t.me/boost/lindreamhynlix пы.сы. вам готовится зарисовка по минсонам, её осталось немного дописать и отредактировать))
custom 52514761494097166211
кстати, напоминаю про свой приват, где я делюсь своей жизнью и ОЧЕНЬ громко кричу по скизам))
custom 52514761494097166213
— Давай сбежим с травологии и пойдем на озеро? — тихо шепчет Минхо, паралельно снимая грязные от земли перчатки. —Давай. или hogwarts ау, в которой Минхо и Джисон очень близкие, неразлучные друзья, которые полностью разделяют интересы, цели и всегда находятся вместе, испытывая полное взаимопонимание, даже не смотря на разные факультеты. В какой-то момент что-то внутри обоих щёлкает и чувства меняются на нечто больше…
признавайтесь, какие песни из кб вам понравились?
custom 525147614940971662111custom 52534493948244550862
сынмин меня заманил в свои сети, хохохо... не теряйте!
custom 525147614940971662113
МАМА
custom 525344939482445508613custom 52514761494097166217
https://youtu.be/BZ4UzthYTss С КАМБЭКОМ
custom 525344939482445508613
там стекло блин
custom 52944616595768322556custom 51321049765956823701
блин, мне кажется вы не осилите
custom 51321049765956823707custom 52534493948244550862
напоминаю!
custom 52514761494097166216
эх, и всё же вы нежные. оке, услышала вас🥺
custom 525147614940971662111
Posted without readable text
custom 513210497659568237011
Showing the 12 most recent of 15 posts we hold for @lindreamhynlix. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“𝑳𝒊𝒏𝒏𝒊 𝒊𝒏 𝒚𝒐𝒖𝒓 𝒅𝒓𝒆𝒂𝒎” (@lindreamhynlix), 183 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/lindreamhynlix.
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.