Telegram RegisterThe public register of Telegram
Telegram profile photo for Лис

Channel

Лис

@Lis1450

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

462subscribers

-14 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-1002195509106
TypeChannel
Username@Lis1450
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/Lis1450

Topic

Gaming — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.

Growth

4624764699 August 2026 — 476 subscribers10 August 2026 — 476 subscribers17 August 2026 — 473 subscribers31 August 2026 — 471 subscribers9 September 2026 — 467 subscribers18 September 2026 — 465 subscribers3 October 2026 — 464 subscribers13 October 2026 — 462 subscribers9 August 202613 October 2026
8 measurements spanning 64 days, net -14. 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 460–478 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 01:20462-2
3 Oct 2026, 05:00464-1
18 Sept 2026, 09:16465-2
9 Sept 2026, 14:56467-4
31 Aug 2026, 19:48471-2
17 Aug 2026, 22:32473-3
10 Aug 2026, 12:35476no change
9 Aug 2026, 16:46476first reading

Engagement

20 posts held, back to 29 July 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

43 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 55.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥2455.8%
❤818.6%
🔥818.6%
🥰24.65%
🤩12.33%

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 12 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 43 reactions 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 29 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, 09:21 UTC19 views3 reactionsread 9 August 2026
Photo

Доброе дня, Лисята. Я прошёл наконец-то первую часть оригинального резика и победил тирана, одним лишь ножом 😁(у меня все патроны кончились до него). Что там по песням. 1) Делается песня по такому аниме. Как "Я стала Секретарем гильдии, но я не люблю Сверхрочную работу". 2) Пишется Песня по первому резику. 3) постараюсь выпустить песню по игре как " Outlast" , а то текст лежит, осталось его закинуть в суно и подобрат…

❤‍🔥3

9 Aug 2026, 06:16 UTC27 viewsread 9 August 2026

Это альфа версия если что, текст ещё улучшается и расширяется. Как вам звучание?

7 Aug 2026, 05:18 UTC44 views1 reactionsread 9 August 2026

https://youtu.be/o2KqUsrTNhM?si=XOvBmbjDZjg47-yl

❤‍🔥1

7 Aug 2026, 04:30 UTC44 viewsread 9 August 2026
Photo

Доброго утра, лисята. Как ваше ничего? В первом резике, дошёл до деревянного дома и после этой локации, меня ждал звиздец:). Толстые враги которых можно быстро убить только с дробовиком, держа их на дистанции. Но для этого нужны Патрончики, а их нема. 😁 (крч страдаю пока что в резике)

4 Aug 2026, 07:24 UTC64 views2 reactionsread 9 August 2026
Photo

Добрый день, лисята. Какие противники в оригинальных резиках самые опасные, как думаете? Зомби, лизуны а может большие насекомые? . А вот и нет, это чёрные вороны по которым легко можно промахнуться и вы потеряете драгоценную полоску хп. Дошёл первого босса Змеи, даже не почувствовал (взял гранатомёт, пару выстрелов и победа), но теперь резик просит меня, еще раз себя от бежать и посмотреть что, я пропустил 😁🦊. А вы…

❤‍🔥2

3 Aug 2026, 13:06 UTC63 viewsread 9 August 2026
Photo

Сейчас не ночь, ну лучше скину сейчас пока есть интернет :) (песня грузится)

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

Mentions

Named by 1 registered channel — 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 13 October 2026 — this entry's latest reading, not the date you are reading this.

“Лис” (@Lis1450), 462 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/Lis1450.

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.