Считаю это успех - быть на стикерах с Baltic Digital Days 😆 P.S. Только вот у меня таких нет🥹. Кто то утащил мою сумку #Post_42 #юмор@altayseo #конференция@altayseo
🔥4👍2

Channel
@altayseo
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
100subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002519658769 |
|---|---|
| Type | Channel |
| Username | @altayseo |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/altayseo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 16:26 | 100 | +3 |
| 9 Aug 2026, 11:46 | 97 | no change |
| 8 Aug 2026, 05:54 | 97 | +1 |
| 7 Aug 2026, 17:27 | 96 | first reading |
20 posts held, back to 15 April 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 8 August 2026 |
|---|---|
| Posts held | 20 (15 April 2026 – 8 August 2026) |
| Views total | 373 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 11:46 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.
Measured directly from 2 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.
77 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 66.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 51 | 66.2% | |
| 👍 | 14 | 18.2% | |
| 🤣 | 6 | 7.79% | |
| 👏 | 3 | 3.90% | |
| 😁 | 3 | 3.90% |
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 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 77reactions 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 15 April 2026 to 8 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 @altayseo. 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 20 most recent posts we hold for this entry, published 15 April 2026 to 8 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.
Считаю это успех - быть на стикерах с Baltic Digital Days 😆 P.S. Только вот у меня таких нет🥹. Кто то утащил мою сумку #Post_42 #юмор@altayseo #конференция@altayseo
🔥4👍2
Это я на Baltic Digital Days 2026 выступаю совсем не с сеошным докладом. Точнее стендапом. Странный опыт. Волновался. Этот монолог у меня родился буквально за пару недель до выступления и он получился совсем не таким, каким я его планировал. И я даже подумал, что я зря «вывалил» все свои мысли на слушателей, но после выступления ко мне подходили люди и благодарили за искренность. Отзывы были разные. Особенно мне пон…
🔥6👍4👏3
В общем, тут на днях с клиентом обсуждали проект. Отвечал на вопросы по сделанному аудиту. Клиент сделал запись созвона и прогнал его через ИИ агента в Битрикс 24. На скрине краткое резюме по встрече, касаемо меня. Почитал. Улыбнулся. Оставлю это здесь. Пусть висит как доказательство моих компетенции😂... Можно кейсы то и не публиковать теперь? #post_40 #клиенты@altayseo
🔥3
Еще одно SEO расширение для Chrome, но уникальное Создал SEO-расширение для Chrome. Точнее как сказать создал, давно уже создал, но для себя, а здесь его упаковал более красиво и выложил в свободный доступ. Нынешние SEO-расширения, которые есть на рынке, меня не устраивали своим юзабилити. Чтобы посмотреть проблему, нужно в них было заходить, что не совсем удобно, в своем расширении я сделал цветную индикацию пробле…
👍5
В мониторинге запросов в Вебмастере теперь доступны почасовые данные о видимости сайта в поиске (данные за сутки, с отставанием от реального времени на несколько часов). Это позволяет оперативно увидеть запросы, по которым начала показываться страница после публикации, чтобы скорректировать заголовок, описание или контент для лучшего соответствия ожиданиям пользователя. Пользуйтесь)
Вот такая сегодня новость. Я как бы не сотрудник, но уже вместе почти три года. Ну вы поняли, есть у меня хорошие клиенты, а еще есть клиенты с которыми мне прям интересно работать и отдыхать😊 #post_39 #клиенты@altayseo
🔥7
🔥Последний день, когда можно купить билеты на SEO-конференцию "Высоко в ТОП!" в Волгограде по самой низкой цене! Купить билет по лучшей цене здесь ☝️ Завтра цена повысится! Купить билет по лучшей цене здесь 🤯 Что за конференция? Планируемое количество участников - 150 человек. 18 топовых спикеров и экспертов (Михаил Шакин, Денис Нарижный, Олег Шестаков, Сергей Погодаев, Алексей Адищев, Илья Горбачев и другие …
🔥3
Неожиданно Stand Up! 🙈Билеты по ссылке 👌. Рекомендую быть. Мероприятие Топчик #post38 #юмор@altayseo #конференция@altayseo
🔥5
Большой разговор про роль оптимизатора, аспекты ЭПОСа, нестандартные источники контента, омниканальность пути пользователя, агентную коммерцию и много другое - в вебинаре с Димой Севальневым. Смотрите на YouTube и в VK.
Пипец как мы с @ie_seo профессионально делаем вид что все понимаем 🤣 на SEO in Minsk #post37 #юмор@altayseo
🤣6
А теперь викторина для коллег!!! Смотрим скрин из отчета, который я подготовил сегодня с утра для клиента и отвечаем на вопрос: Это хороший результат или нет? Что думаете? Сравнение с маем 2025 года, а то вдруг кто то не заметил 😏 #post36 #seo@altayseo #кейс@altayseo
В общем, после посещения двух конференции подряд на которых так активно форсились нейросети, их влияние на выдачу и тп, я до сих пор придерживаюсь мнения что: 1. В GEO денег нет. Деньги будут только у подрядчика, который навязал это как отдельную услугу своим клиентам. Максимум что сейчас получит клиент за свои деньги - это ощущение удовлетворенного ЧСВ. 2. Все GEO держится только на хорошем SEO. Делайте его хорошо…
🔥6
Showing the 12 most recent of 20 posts we hold for @altayseo. 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.
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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“#АлтайскоеSEO inside!🍌” (@altayseo), 100 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/altayseo.
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.