Telegram RegisterThe public register of Telegram
Telegram profile photo for Саня знает, Саня пожил

Channel

Саня знает, Саня пожил

@AlexsKnows

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

121subscribers

+0 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-1001056390896
TypeChannel
Username@AlexsKnows
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/AlexsKnows

Growth

120121120.57 August 2026 — 121 subscribers9 August 2026 — 121 subscribers29 August 2026 — 120 subscribers15 September 2026 — 121 subscribers7 August 202615 September 2026
4 measurements spanning 39 days. 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 120–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 15:37121+1
29 Aug 2026, 04:24120-1
9 Aug 2026, 04:01121no change
7 Aug 2026, 16:57121first reading

Engagement

16 posts held, back to 25 September 2025the 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 16 posts for this entry, the most recent from 1 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

253 reactions across 16 posts, in 23 distinct kinds. The most used accounts for 28.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7228.5%
👏249.49%
custom 5188292275632873125207.91%
197.51%
🥰197.51%
custom 5273769559411662435176.72%
👍145.53%
custom 5855054367442341245103.95%
93.56%
🐳83.16%
💯62.37%
custom 583219531454244773051.98%
custom 585941677001985642651.98%
🤔51.98%
custom 518823310816340309541.58%
custom 523567219447379481741.58%
🤝41.58%
😱31.19%
🌚10.395%
💩10.395%
3 further kinds31.19%

Custom emoji. 7 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 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 253 reactions 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 September 2025 to 1 April 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

1 Apr 2026, 14:33 UTC138 views13 reactionsread 9 August 2026

То ли мёртвой водой по складкам морщин Отходящей старухи зимы, То ли счастья слезой в смешливых глазах Вечно юной весны Берут разбег ручьи. Один исток, один исход. Един для всех урочный час. И каждый раз Одна мечта, напомнить: «Кто жгёт траву — тот пидорас».

🔥6👍4custom 51882922756328731252👏1

22 Mar 2026, 19:16 UTC213 views11 reactionsread 9 August 2026
Photo

Вы думали, я шучу?

🔥6🤔3🐳1custom 51882922756328731251

11 Mar 2026, 17:26 UTC259 views12 reactionsread 9 August 2026
Photo

Это я успешно решаю взрослые дела. Жизнь даёт мне лимоны, а я ем не их. Кажется, у меня есть новая аватарка

custom 51882922756328731255👍21🐳1🗿1🤔1custom 58321953145424477301

8 Mar 2026, 05:19 UTC291 views8 reactionsread 9 August 2026

— Уважаемые знатоки. Против вас играет безработный Игорь Фëдорович из Омска. Он интересуется: что общего у 8 марта и винтовки?

custom 58594167700198564265🐳1🤔1🤯1

18 Feb 2026, 06:32 UTC328 views17 reactionsread 9 August 2026
Photo

Я изготовил для вас изображение развлекательного характера. Как говорит молодёжь, 'мэм'. Распространите среди участников своего домового чата.

custom 52737695594116624357custom 51882922756328731254💯31🐳1😱1

22 Dec 2025, 10:57 UTC435 views17 reactionsread 9 August 2026
Photo

С Днём Энергетика 💡

🔥74custom 58550543674423412454🐳1custom 51882922756328731251

11 Dec 2025, 19:04 UTC478 views22 reactionsread 9 August 2026
Photo

С ума сойти. Первые деньги из-под пера. Ведро керосина в костёр моего синдрома самозванца.

👏1352custom 51882922756328731252

11 Dec 2025, 07:28 UTC365 views22 reactionsread 9 August 2026

В Цветочном городе пахло не цветами. Пахло углëм, машинным маслом и вечной усталостью, которая вместе с бесконечной пылью оседает на подоконниках серых пятиэтажек. В одном из таких домов жил Незнайка. Вылинявшая синяя шляпа с прожогами на полях висела на вешалке у входа. Иногда, распивая с Винтиком и Шпунтиком после смены, Незнайка показывал на нее пальцем и говорил: «А помнишь?» Они хмыкали — помнили. Но особо вс

🔥11👏4custom 523567219447379481742custom 52737695594116624351

2 Dec 2025, 09:57 UTC254 views13 reactionsread 9 August 2026
Photo

С такой зимой урожая не жди. Проклятые электромобили — довели экологию.

👏5custom 51882331081634030954👍2💯2

1 Dec 2025, 10:03 UTC251 views11 reactionsread 9 August 2026
Photo

Человек-Зажигалочка. Задор и веселье.

custom 58321953145424477304🐳2👍1👏1💯1🔥1🤷‍♂1

18 Oct 2025, 06:18 UTC336 views28 reactionsread 9 August 2026
Photo

Я вам про первого кота так и не собрался рассказать, а тут уже второй завëлся. И снова, не то что бы мы искали этой встречи. Но теперь эта Марфуша с нами, нервирует Яяшу

🥰16custom 52737695594116624358🔥3👍1

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

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

“Саня знает, Саня пожил” (@AlexsKnows), 121 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/AlexsKnows.

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.