Telegram RegisterThe public register of Telegram
Telegram profile photo for Лисья нора | Малфой мэнор 🦚

Channel

Лисья нора | Малфой мэнор 🦚

@ElliotLav

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

636subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001560668565
TypeChannel
Username@ElliotLav
Created22 May 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/ElliotLav

Growth

636639637.57 August 2026 — 637 subscribers7 August 2026 — 637 subscribers22 August 2026 — 639 subscribers30 August 2026 — 636 subscribers7 August 202630 August 2026
4 measurements spanning 23 days, net -1. 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 636–639 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 05:28636-3
22 Aug 2026, 15:24639+2
7 Aug 2026, 15:41637no change
7 Aug 2026, 04:01637first reading

Engagement

14 posts held, back to 21 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.7%
avg views ÷ 636 subscribers
Avg views / post
126
2 posts measured
Reaction rate
31.1%
reactions ÷ views · ER floor
Posts in window
3
of 14 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 6 August 2026
Posts held14 (21 July 20266 August 2026)
Views total251
Reactions total78
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 04:01 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

460 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 23.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥10823.5%
8718.9%
custom 53260075157610902096113.3%
custom 53257282398076345895612.2%
🔥4910.7%
🌚265.65%
custom 5233664765414352059255.43%
🍓183.91%
🍌91.96%
😭91.96%
💔61.30%
custom 532823998392699502251.09%
custom 627602151533078598710.217%

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

Measured over the 14 most recent posts we hold, published 21 July 2026 to 6 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

6 Aug 2026, 22:23 UTC56 views23 reactionsread 7 August 2026
Photo

Смешные и ооочень эмоциональные кадры со сцены ВК Феста, где мы то орём на зал, то оскорблены невыносимой жарой, то танцуем канкан ✌️ Отыгрыш 🔴☝️🔝

🍓11custom 53260075157610902096custom 523366476541435205941custom 62760215153307859871

5 Aug 2026, 13:06 UTC195 views55 reactionsread 7 August 2026
Photo

Фотос на Маму отстрелян ❤️ Любимка Блэк снял нам милую, тёплую и очень мемную историю. Кстати, шип кадры Вас тоже ждут 😏🌚 Спойлер 🤩

❤‍🔥18custom 532600751576109020917🔥144🌚1custom 52336647654143520591

4 Aug 2026, 15:03 UTC202 views21 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 5326007515761090209107🔥4

3 Aug 2026, 17:19 UTC226 views23 reactionsread 7 August 2026
Video message

Video message, posted without a caption

❤‍🔥9custom 532600751576109020986

2 Aug 2026, 15:14 UTC280 views50 reactionsread 7 August 2026
Photo

Оттрубили вчера первую бальную вечеринку по ГП 😳 Формат оказался интересным, второй затест уже 8 числа ✌️

❤‍🔥26🍌9custom 52336647654143520597custom 53260075157610902097💔1

1 Aug 2026, 02:27 UTC294 views28 reactionsread 7 August 2026
Video

Это мы в пол 6 утра собираем треки для дискотеки..

🌚25❤‍🔥3

31 Jul 2026, 13:49 UTC338 views59 reactionsread 7 August 2026
Photo

Фотки с Эпика в Мамми 🙏 и Дэдди 😒 Увидимся в этих двоих уже на ВайбКоне, а также, снимаем на них наконец то фотос уже в начале августа 🌚 Планируем снять некоторое напряжение между ними 😏 Не разрушим Ваше детство? 😏😏😏

❤‍🔥2717🔥12custom 53260075157610902093

28 Jul 2026, 17:27 UTC385 views34 reactionsread 7 August 2026
Photo

Будем на ВайбКоне с Боярским и Гурченко раздавать тёплого деревенского вайба! Последний выход в этих прелестниках в этом году ✨ Мамми и Дэдди будут Вас ждать!

custom 532572823980763458915❤‍🔥10🍓72

25 Jul 2026, 12:52 UTC557 views10 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 532600751576109020910

23 Jul 2026, 12:34 UTC494 views52 reactionsread 7 August 2026
Photo

С каждый разом всё больше заебываемся с деталями. Активно готовим реквизит и украшения для феста 🤩

23❤‍🔥13custom 532572823980763458912custom 53282399839269950224

23 Jul 2026, 01:31 UTC475 views63 reactionsread 7 August 2026
Photo

Активно готовимся к мэджику✨

27custom 532572823980763458919🔥17

Showing the 12 most recent of 14 posts we hold for @ElliotLav. 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.

Forward network

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.

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

“Лисья нора | Малфой мэнор 🦚” (@ElliotLav), 636 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ElliotLav.

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.