я уже очень давно не делала йогу поэтому я 4 часа играла в симс и заставляла это делать свою симку.. мне понравилось (я в восторге)
custom 5294355427855722463124custom 527615814104884209346custom 522197674206276011739

Channel
@lucholyyaa
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
9,410subscribers
-129 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001454637386 |
|---|---|
| Type | Channel |
| Username | @lucholyyaa |
| Description | тревожный человек, излучающий спокойствие ✩ .•°*” «Вы так торопитесь в будущее, что отводите настоящему роль средства для достижения цели?» инст: 108.56.23 co-op: @chumworks |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/lucholyyaa |
Other / unclassifiable — 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 75% 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 |
|---|---|---|
| 12 Nov 2026, 21:44 | 9,410 | -23 |
| 8 Nov 2026, 16:06 | 9,433 | -2 |
| 5 Nov 2026, 01:00 | 9,435 | -9 |
| 2 Nov 2026, 02:56 | 9,444 | -5 |
| 29 Oct 2026, 17:56 | 9,449 | -7 |
| 26 Oct 2026, 10:30 | 9,456 | -15 |
| 23 Oct 2026, 00:37 | 9,471 | -17 |
| 20 Oct 2026, 06:48 | 9,488 | -8 |
| 17 Oct 2026, 07:06 | 9,496 | +2 |
| 14 Oct 2026, 15:05 | 9,494 | -7 |
| 11 Oct 2026, 01:39 | 9,501 | +73 |
| 5 Oct 2026, 03:37 | 9,428 | +17 |
| 26 Sept 2026, 14:38 | 9,411 | -51 |
| 15 Sept 2026, 04:22 | 9,462 | +5 |
| 11 Sept 2026, 20:38 | 9,457 | -8 |
| 7 Sept 2026, 13:59 | 9,465 | +25 |
| 2 Sept 2026, 11:23 | 9,440 | -3 |
| 30 Aug 2026, 17:14 | 9,443 | -20 |
| 27 Aug 2026, 11:06 | 9,463 | -17 |
| 24 Aug 2026, 00:36 | 9,480 | first reading |
90 posts held, back to 3 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 57 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 14 November 2026 |
|---|---|
| Posts held | 90 (3 August 2026 – 14 November 2026) |
| Views total | 91,920 |
| Reactions total | 8,136 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 00:44 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 15 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 11 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.
25,541 reactions across 90 posts, in 11 distinct kinds. The most used accounts for 13.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226698251150855717 | 3,321 | 13.0% | |
| custom 5294355427855722463 | 2,986 | 11.7% | |
| custom 5276158141048842093 | 2,686 | 10.5% | |
| custom 5221976742062760117 | 2,464 | 9.65% | |
| custom 5461048627646469668 | 2,294 | 8.98% | |
| custom 5292264899769035518 | 2,249 | 8.81% | |
| custom 5215621264206477593 | 2,232 | 8.74% | |
| custom 5267416907643896098 | 2,137 | 8.37% | |
| custom 5215441373796253612 | 2,124 | 8.32% | |
| custom 5307774022379927373 | 1,870 | 7.32% | |
| custom 5460803535337710114 | 1,178 | 4.61% |
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 90 of the 90 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 25,541 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 90 most recent posts we hold, published 3 August 2026 to 14 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 @lucholyyaa. 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 90 most recent posts we hold for this entry, published 3 August 2026 to 14 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: 1 of 32 posts held from the last 30 days (3.13%) 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).
я уже очень давно не делала йогу поэтому я 4 часа играла в симс и заставляла это делать свою симку.. мне понравилось (я в восторге)
custom 5294355427855722463124custom 527615814104884209346custom 522197674206276011739
физически находишься*
custom 529435542785572246366custom 522197674206276011724custom 527615814104884209324
Video message, posted without a caption
custom 527615814104884209383custom 522197674206276011742custom 529435542785572246341
я умру от ностальгии
custom 5276158141048842093111custom 529435542785572246347custom 522197674206276011739
Video message, posted without a caption
custom 5276158141048842093100custom 522197674206276011752custom 529435542785572246343
из того, что меня реально обрадовало, так это шерстяные носки которые вывешивают у нас в деревенском магните на продажу за 450₽. я скуплю все. и хочу научиться их вязать! придумывать самые крутые сочетания..
custom 5276158141048842093190custom 522197674206276011772custom 529435542785572246363
блин так круто я в любую минуту могу спросить у своих читателей любую информацию типа ребят предлагают вот стока зп стрем не стрем вот такой тариф вот вот такое выписал врач че дум и мне ответят… спасибо……….
custom 5294355427855722463144custom 527615814104884209358custom 522197674206276011747
а еще из грустного… Т мобайл повысил абонентскую плату за месяц учитывая, что у меня даже не безлимитный интернет до 718₽/мес. я считаю, что это грабеж. куда переходить? очень важные взрослые советы в этом канале сегодня 🙏🏻 а цены на коммуналку в этом месяце вы видели ваще?
custom 5294355427855722463151custom 527615814104884209344custom 522197674206276011740
Video message, posted without a caption
custom 529435542785572246389custom 527615814104884209334custom 522197674206276011728
и вообще вчера разбилась моя любимая кружка, черный кот перебежал дорогу и «правое легкое не слышно», а сегодня сказали, что гайморит это опасно потому что все рядом с мозгом.. я ваще боюсь теперь.. кто-нибудь лечил это? вроде и чувствую себя нормально почти, кроме ужасной слабости, но чета стремно…
custom 5276158141048842093102custom 529435542785572246354custom 522197674206276011743
впервые в жизни эта штукенция а с моей носовой перегородкой которая буквально выглядит так 🪱🪱🪱 даже удивительно.. а вообще вчера мне ставили подозрение на пневмонию.. щас в моменте поняла почему меня так ебут… у меня же скоро день рождения!!!!!!! точно… но мне выписали огромную кучу лекарств за 3,5 тысячи рублей включая противовирусные ни одно из которых не признал чат джипити…. и что теперь.. кому верить… это же в…
custom 5294355427855722463129custom 527615814104884209348custom 522197674206276011746
бууууу я двусторонний острый гайморииииттт… испугался…. не бойся…. он не твой… он оли 108.56.23….
custom 5294355427855722463191custom 522197674206276011761custom 527615814104884209352
Showing the 12 most recent of 90 posts we hold for @lucholyyaa. 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.
We recorded 1 post on @lucholyyaa 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 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“108.56.23” (@lucholyyaa), 9,410 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/lucholyyaa.
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.