Channel
@L0ryXD
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
1,106subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003006711657 |
|---|---|
| Type | Channel |
| Username | @L0ryXD |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/L0ryXD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 20:13 | 1,106 | -1 |
| 9 Aug 2026, 14:12 | 1,107 | no change |
| 8 Aug 2026, 14:47 | 1,107 | first reading |
16 posts held, back to 25 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.
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 August 2026 |
|---|---|
| Posts held | 16 (25 June 2026 – 5 August 2026) |
| Views total | 5,386 |
| Reactions total | 925 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 14:47 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.
1,874 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 19.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5278531587221269173 | 363 | 19.4% | |
| custom 5283231140436523985 | 305 | 16.3% | |
| ❤ | 280 | 14.9% | |
| custom 5280478379932426247 | 149 | 7.95% | |
| 💘 | 147 | 7.84% | |
| custom 5278218965141726608 | 128 | 6.83% | |
| 🔥 | 111 | 5.92% | |
| custom 5280937533411204791 | 101 | 5.39% | |
| 💋 | 78 | 4.16% | |
| 🍓 | 71 | 3.79% | |
| custom 5280926327841529149 | 65 | 3.47% | |
| 🌭 | 50 | 2.67% | |
| custom 5424809587683401940 | 18 | 0.961% | |
| custom 5278497287612440453 | 5 | 0.267% | |
| ⚡ | 3 | 0.16% |
Custom emoji. 8 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 16 of the 16 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 1,874reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 25 June 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @L0ryXD. 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 16 most recent posts we hold for this entry, published 25 June 2026 to 5 August 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.
Эхэх ребя, скорее всего где-то 19 августа я перееду в другой канал, подробности напишу позже. Надеюсь вы не будете кусаца в комментариях
❤38custom 527853158722126917320custom 542480958768340194018🍓3
Posted without readable text
💋63custom 528323114043652398522custom 527853158722126917315💘5🍓2
Гипер быстрый #гифт для любимки (@Vestik_arts)) аррррр⭐️ Рендер говнище, надо чота менять
custom 528323114043652398567🍓26💘17custom 52785315872212691737custom 52809263278415291494💋3🔥2❤1
Рисую адоптыша на совместную лоту с моей любимой джейннн аррр ..Думаю.. Может снова брать коммишки
🌭42custom 528323114043652398522custom 527853158722126917320💘6❤5⚡3🍓3💋2
Опачки попачки Кстати, кто играет в пт? Просто скоро (через 84 дня) у меня др, хочеца сходку организовать, побалакать с вами🙄
custom 527853158722126917379💘30❤22🍓4custom 52809263278415291494custom 52832311404365239854💋3🔥3
Дайте мне сил дорисовать это ьевьвогавго😞
❤63custom 527853158722126917324custom 528323114043652398516🌭3custom 52809263278415291493🍓2
Скиньте пажалуста каких нибудь к*сточек для ибиса
custom 527853158722126917356custom 52809263278415291495💋1custom 52832311404365239851
Кушайте рефы, скора дроп с новыми персами ⭐️— #loryXD
❤45custom 528092632784152914919custom 528323114043652398516custom 52785315872212691737🍓5💘4🌭1
Чуваки всем превед, я жиф🙏🙏🙏
custom 528323114043652398553custom 528092632784152914914💘11🌭4custom 52785315872212691733🍓2
Превед папищеки Вам нравица такой рендер?
custom 527853158722126917394custom 528323114043652398528🔥25❤6🍓5custom 52782189651417266085💘1
Папищеки помогите джейн держит меня в подвале и заставляет рисовать Ала в стрингах сос что делать
custom 527821896514172660851❤16custom 527853158722126917313🔥5custom 52832311404365239852🍓1💘1
Эххх, мне так лень это рендерить 💣
🔥69custom 527853158722126917325custom 528093753341120479121🍓11custom 52782189651417266083💋2💘1
Showing the 12 most recent of 16 posts we hold for @L0ryXD. 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.
Citation-graph rank — 157,193 of 1,336,469entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@L0ryXD named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“✧˚∘˙𝗟𝗢𝗥𝗬 | ᴩᴇᴋʙᴇᴄᴛы•°” (@L0ryXD), 1,106 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/L0ryXD.
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.