Telegram RegisterThe public register of Telegram
Telegram profile photo for kaleos.p

Channel

kaleos.p

@kaleos_pp

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry

68,813subscribers

-2,192 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002093433296
TypeChannel
Username@kaleos_pp
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/kaleos_pp

Topic

Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

68,81371,00569,9097 August 2026 — 71,005 subscribers7 August 2026 — 71,005 subscribers8 August 2026 — 71,003 subscribers9 August 2026 — 70,974 subscribers10 August 2026 — 70,911 subscribers11 August 2026 — 70,867 subscribers12 August 2026 — 70,831 subscribers14 August 2026 — 70,780 subscribers15 August 2026 — 70,731 subscribers16 August 2026 — 70,694 subscribers17 August 2026 — 70,620 subscribers18 August 2026 — 70,574 subscribers20 August 2026 — 70,530 subscribers21 August 2026 — 70,499 subscribers22 August 2026 — 70,454 subscribers24 August 2026 — 70,412 subscribers25 August 2026 — 70,365 subscribers26 August 2026 — 70,333 subscribers27 August 2026 — 70,291 subscribers28 August 2026 — 70,252 subscribers29 August 2026 — 70,199 subscribers30 August 2026 — 70,169 subscribers31 August 2026 — 70,117 subscribers1 September 2026 — 70,078 subscribers2 September 2026 — 70,031 subscribers3 September 2026 — 69,980 subscribers4 September 2026 — 69,905 subscribers7 September 2026 — 69,776 subscribers11 September 2026 — 69,639 subscribers12 September 2026 — 69,567 subscribers14 September 2026 — 69,509 subscribers16 September 2026 — 69,445 subscribers18 September 2026 — 69,339 subscribers25 September 2026 — 69,096 subscribers3 October 2026 — 68,813 subscribers7 August 20263 October 2026
35 measurements spanning 57 days, net -2,192. 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 68,484–71,334 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
3 Oct 2026, 23:1668,813-283
25 Sept 2026, 07:3669,096-243
18 Sept 2026, 20:0169,339-106
16 Sept 2026, 10:3769,445-64
14 Sept 2026, 13:2069,509-58
12 Sept 2026, 23:0169,567-72
11 Sept 2026, 01:5569,639-137
7 Sept 2026, 23:1869,776-129
4 Sept 2026, 20:0269,905-75
3 Sept 2026, 06:2769,980-51
2 Sept 2026, 02:3570,031-47
1 Sept 2026, 03:1870,078-39
31 Aug 2026, 03:4470,117-52
30 Aug 2026, 07:1470,169-30
29 Aug 2026, 08:2570,199-53
28 Aug 2026, 05:1770,252-39
27 Aug 2026, 08:1570,291-42
26 Aug 2026, 05:4270,333-32
25 Aug 2026, 08:0970,365-47
24 Aug 2026, 06:0270,412first reading

Engagement

104 posts held, back to 23 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 131 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.3%
avg views ÷ 68,813 subscribers
Avg views / post
12,600
52 posts measured
Reaction rate
1.04%
reactions ÷ views · ER floor
Posts in window
52
of 104 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 30 September 2026
Posts held104 (23 July 2026 – 30 September 2026)
Views total654,100
Reactions total6,812
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Oct 2026, 13:58 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.

What this channel posts

Video runtime
52m 12s
Average length
5m 48s

Measured directly from 9 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.

Reaction mix

15,318 reactions across 104 posts, in 36 distinct kinds. The most used accounts for 37.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣5,76537.6%
🔥2,35715.4%
👍1,87512.2%
😁1,4199.26%
❤‍🔥8155.32%
🤯5733.74%
🫡4713.07%
🤔3152.06%
🤡3122.04%
🤬2811.83%
👀2141.40%
💯1891.23%
😭1200.783%
😈1110.725%
🎉1000.653%
👎890.581%
😢760.496%
🤓350.228%
🍾300.196%
🤝300.196%
16 further kinds1410.92%

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 104 of the 104 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 15,318 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 104 most recent posts we hold, published 23 July 2026 to 30 September 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.

Telegram Stars

Stars received
11
across the posts below
Posts paid on
9
of 104 we hold a reading for · 9%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kaleos_pp. 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 104 most recent posts we hold for this entry, published 23 July 2026 to 30 September 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.

Advertising

Ad load
0.962%
1 of 104 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
9,010
over 1 measured post
Median views · rest
15,300
over 103 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VfnxxBgRrt130 September 202630 September 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 104 most recent posts we hold, published 23 July 2026 to 30 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

30 Sept 2026, 21:03 UTC≈9,900 views177 reactionsread 3 October 2026
Photo

‼️Российский интернет — ВСЁ!⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ Уже 2017 году это было известно, прям на глазах у всех это сделали Подписаться

😁142🕊9🤯7👍4🤣4🤬4😭4💯2

30 Sept 2026, 12:12 UTC≈10,700 views117 reactionsread 3 October 2026
Video

🤝 СССР VS США ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ В Америке новый тренд: Родители всё чаще отдают детей на занятия по математике, которая ведется по советской системе. Они считают обычную школьную программу слишком медленной, а «Русская математика» учит ребёнка понимать и объяснять ход решения, а не механически применять заученные алгоритмы. Также, дети рано знакомятся с алгеброй, закономерностями…

🤣83👍25😁4🔥3👎1🤯1

30 Sept 2026, 10:09 UTC≈9,010 views16 reactionsread 3 October 2026
Advertisementerid 2VfnxxBgRrtPhoto

Осень — время, когда бизнес активно начинает искать подрядчиков: бухгалтеров, юристов, маркетологов, дизайнеров, IT-специалистов и всех, кто закрывает задачи без расширения штата. И тут появляется другая задача: где вообще искать этого человека? А если вы сами оказываете услуги, то вопрос работает и в обратную сторону. Где найти заказчика, которому вы нужны именно сейчас? Авито Услуги как раз помогают сократить эту…

👍6❤‍🔥3🤝2🤣2🤓1🫡1😱1

30 Sept 2026, 08:10 UTC≈8,320 views140 reactionsread 3 October 2026
Photo

😨 В России за период с 1 января по 30 июня 2026 г. было открыто приблизительно 37 тыс. новых компаний, связанных с информационными технологиями. — Михаил Мишустин. Скинь этот пост тому, кто ищет работу в айтишке, пусть он скажет, эти 37 тыс компаний сейчас с ним в одной комнате? Подписаться

🤣114🤡16🫡8🕊1🤪1

29 Sept 2026, 17:20 UTC≈9,250 views47 reactionsread 3 October 2026
Photo

‼️OpenAI сделали Codex для Linux и выпустили GPT-6.1 Sol, обещают мощность Astra, но в 5 раз дешевле в API. Также релизнули Dots: Это агенты, которые работают постоянно и сопровождают вас во всех рабочих процессах. Им можно делегировать длинные задачи и все, что связано с кодом, компьютером и браузером. Можно дать ему коннектор к Codex и любым приложениям. С этими агентами, в ближайшем будущем можно будет общаться…

❤‍🔥30👍7🤯5🥱2🤔1🤣1🫡1

29 Sept 2026, 09:39 UTC≈9,480 views98 reactionsread 3 October 2026
Photo

😵 Дженсен Хуанг заявил, что готов пожертвовать умами наших детей ради искусственного интеллекта А теперь как было на самом деле: Было проведено исследование, согласно которому использование ИИ улучшало выполнение домашних заданий, но впоследствии снижало экзаменационные результаты детей. Хуанг дал на это ответ, что базовые математические навыки, а именно деление столбиком, таблица умножения, извлечение корней — уже…

🫡62🤔14🤣9🔥5👎4🤝3👍1

28 Sept 2026, 10:03 UTC≈10,500 views229 reactionsread 3 October 2026
Photo

✅Есть пробитие ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀⠀ Парень отправил 3 резюме с одинаковым опытом, но разными формулировками и ключевыми словами. Первое резюме сразу отсеял алгоритм, Второе отсеяли после тестового, Третье пробило броню и его пригласили на на собес. Подписаться

🤣206🔥8👍7👀4🫡4

27 Sept 2026, 21:01 UTC≈11,100 views161 reactionsread 3 October 2026
Photo

🚑 Программирование — занятие для умственно отсталых. ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀⠀ Отправил ребенка на дополнительные курсы в школе — выдали учебник. Мнение? Подписаться

🔥80🤣72🤯6💯2👍1

24 Sept 2026, 21:21 UTC≈15,600 views124 reactionsread 3 October 2026
Photo

‼️СРОЧНО: ГЛАВА OpenAI ВЫСТУПИЛ ПЕРЕД СОВЕТОМ БЕЗОПАСНОСТИ ООН ПО ВОПРОСАМ ИИ. Краткая версия доклада: Сэм Альтман предупреждает мир о Сэме Альтмане и говорит, что нам нужно остановить Сэма Альтмана, потому что Сэм Альтман не может остановить Сэма Альтмана. Длинная версия: 🟣ИИ развивается слишком быстро, и если темп ещё ускорится, люди и институты могут перестать понимать, что происходит, и вовремя вмешиваться. 🟣Г…

😁77🤣24🤔7👍4🌚3😈3👀2❤‍🔥1

24 Sept 2026, 17:56 UTC≈12,400 views190 reactionsread 3 October 2026
Photo

AGI среди людей, ловите его пока не убежал Подписаться

🤣161🔥14🤬8❤‍🔥2🤯2😁2👍1

24 Sept 2026, 12:02 UTC≈12,800 views22 reactionsread 3 October 2026
Photo

😎 На E-CODE уже роботы готовят коктейли и мороженое Каждый год Ozon Tech ко Дню программиста готовит свою большую конфу. В этом году на E-CODE была целая Робозона: пространство, где говорили о роботах, изучали, как они устроены, соревновались в их проектировании. По пространству Робозоны гуляли робособаки и робокошки, а в робокафе можно было заказать еду и напитки. Там же прошёл финал инженерного хакатона Робозон: 9…

👍12🤣5🔥2🤝2🫡1

24 Sept 2026, 08:13 UTC≈10,900 views25 reactionsread 3 October 2026

😎 Нейрослоп интерфейсы — ВСЁ! Отрываю от сердца три скилла для фронтендеров, дизайнеров и всех кто собирает интерфейсы и цифровые продукты: UI/UX Pro Max — большая база знаний по дизайну для AI-кодера: стили, цвета, шрифты, UX-правила, accessibility, графики, рекомендации под разные стеки. Нужен, чтобы AI понимал, как правильно проектировать интерфейс. Impeccable — контролёр и редактор дизайна: Может проанализирова…

👍14🔥5❤‍🔥3😁2🤝1

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

Posts edited after publishing

@kaleos_pp edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
13 August 2026
Most recent edit
8 September 2026

Forward network

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.

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

“kaleos.p” (@kaleos_pp), 68,813 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/kaleos_pp.

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.