Telegram RegisterThe public register of Telegram
Telegram profile photo for Waicore

Channel

Waicore

@waicore

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

9,685subscribers

-287 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001663890244
TypeChannel
Username@waicore
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/waicore

Growth

9,6859,9739,8297 August 2026 — 9,972 subscribers7 August 2026 — 9,973 subscribers11 August 2026 — 9,955 subscribers14 August 2026 — 9,923 subscribers18 August 2026 — 9,880 subscribers21 August 2026 — 9,841 subscribers25 August 2026 — 9,808 subscribers28 August 2026 — 9,799 subscribers30 August 2026 — 9,779 subscribers3 September 2026 — 9,741 subscribers9 September 2026 — 9,685 subscribers7 August 20269 September 2026
11 measurements spanning 33 days, net -287. 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 9,642–10,016 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 08:589,685-56
3 Sept 2026, 17:189,741-38
30 Aug 2026, 23:579,779-20
28 Aug 2026, 07:139,799-9
25 Aug 2026, 03:289,808-33
21 Aug 2026, 11:439,841-39
18 Aug 2026, 01:079,880-43
14 Aug 2026, 19:169,923-32
11 Aug 2026, 00:149,955-18
7 Aug 2026, 18:149,973+1
7 Aug 2026, 16:159,972first reading

Engagement

21 posts held, back to 31 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
26.6%
avg views ÷ 9,685 subscribers
Avg views / post
2,580
2 posts measured
Reaction rate
1.65%
reactions ÷ views · ER floor
Posts in window
2
of 21 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 17 August 2026
Posts held21 (31 March 202617 August 2026)
Views total5,150
Reactions total85
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 05:02 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

1,895 reactions across 21 posts, in 13 distinct kinds. The most used accounts for 26.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
50026.4%
custom 540674124867963290327514.5%
🔥22812.0%
🤡21111.1%
👍1668.76%
🥰1437.55%
👏1055.54%
😁663.48%
custom 5388597069143357073633.32%
🍾552.90%
👾311.64%
custom 5388976976180557359271.42%
😎251.32%

Custom emoji. 3 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 21 of the 21 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 1,895 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 31 March 2026 to 17 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.

Telegram Stars

Stars received
562
across the posts below
Posts paid on
16
of 21 we hold a reading for · 76%
Most on one post
152
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @waicore. 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 21 most recent posts we hold for this entry, published 31 March 2026 to 17 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.

Recent posts

17 Aug 2026, 16:09 UTC≈2,520 views41 reactions4 Starsread 29 August 2026
Photo

📸 Большое обновление imgdb.io - теперь с личным кабинетом и API Мы видим по активности что многим понравился наш сервис, поэтому продолжаем развивать imgdb и добавили сразу несколько полезных возможностей. ✍️ Личный кабинет Теперь после авторизации в одном месте доступны все ваши загрузки: - фотографии и альбомы; - запароленные изображения; - one-time фото. При этом авторизация по-прежнему не обязательна, можно по

🔥16👍109custom 54067412486796329032🍾1👏1👾1😎1

15 Aug 2026, 15:11 UTC≈2,630 views44 reactionsread 29 August 2026
Forwarded from @waicore_alerts

🔥Крупная авария во Франкфурте - затронута связность в локации FRA (Германия, Франкфурт) 🔽 Примерно с 05:30 (UTC+3) мы начали фиксировать потери пакетов и деградацию связности на части направлений в Германии. Сразу успокоим: наша площадка и оборудование в полном порядке, все сервера работают, данные в полной сохранности. Авария произошла не у нас, а уровнем выше - в дата-центре Equinix FR5. Это один из крупнейших тел

custom 5406741248679632903366😁2

3 Aug 2026, 17:20 UTC≈4,790 views233 reactionsread 29 August 2026

Забыли? 😮 Хотим вспомнить про наш другой инструмент paste.waicore.com, который не был обделен вниманием. За 4 месяца мы увидели, что людям действительно не хватало удобного инструмента для работы с текстом (пастами): логи, конфигурации, любовные записки и не только. Если кто-то не знаком - это бесплатный инструмент для разработчиков, сисадминов и всех остальных. Сохраняете текст, получаете ссылку. Можно защитить п

👏6655👍50🔥46😁9custom 54067412486796329035👾1😎1

24 Jul 2026, 12:38 UTC≈5,620 views124 reactions96 Starsread 29 August 2026

😎 бескомпромиссная сказка про деда Как и обещали, мы продолжаем нашу небольшую рубрику "мини-блога" и в этот раз обсудим такую тему как бич современного хостинга 😱 В рамках конкретно данной статьи мы рассмотрим 2 основных вопроса, которые интересуют наших клиентов/пользователей: 1. Почему у нас так мало локаций, пока у других их с полсотни? 2. Почему у нас такие цены на услуги? 🥇Нам постоянно пишут "Почему у вас т

69👍32🍾11🔥5👏2👾2🤡2🥰1

12 Jul 2026, 10:21 UTC≈6,150 views67 reactionsread 29 August 2026

⚡️⚡️⚡️ Х О С Т И Н Г — В С Ё? Это новый формат небольшого блога. Если вам интересно - поддержите нас лайком ❤️ Сегодня разбираем главный вопрос: почему соседство на хостинге - риск для бизнеса или сайтов размещенных на них? Инструменты для поиска и эксплуатации уязвимостей за последние годы стали куда доступнее - в том числе благодаря ИИ. Найденные дыры начинают использовать быстрее, а на классическом shared-хостин

custom 54067412486796329033319🤡9👏5🍾1

6 Jul 2026, 08:18 UTC≈6,180 views37 reactionsread 29 August 2026

Запускаем летние скидки ☀️ Лето, жара, все в отпусках, а мы работаем без выходных. Решили вас немного побаловать, чтобы не было обидно. 💰 С сегодняшнего дня: • 30% скидка на покупку любого тарифа • 10% скидка на продление Акция работает прямо сейчас и до 13 июля. Берите, продлевайте, пользуйтесь. Следите за нашими новостями, мы готовим много нового для вас. Лето же, надо успеть закупиться, пока все на пляже. Кс

🍾158custom 54067412486796329036🔥3🤡2👍1👾1😎1

2 Jul 2026, 08:03 UTC≈6,900 views41 reactionsread 29 August 2026

imgdb.io уже получил обновление 📷 Мы рады что вам понравился сервис, с его открытия уже загрузили 1000 изображений. Поэтому мы поковырялись в сервисе: • Добавили режим альбома - кидаешь сколько угодно фоток за раз, а получаешь одну единственную ссылку на всю пачку. Удобно для скринов, галереи, отчётов. • В приложении пофиксили баги, сильно уменьшили потребление оперативки (минус 80%) • Добавили инструмент «сетка

17custom 54067412486796329039🤡4😎4👏2👾2🔥2👍1

27 Jun 2026, 13:12 UTC≈7,940 views70 reactions43 Starsread 29 August 2026

🖼 Запустили свой сервис скриншотов и картинок - imgdb.io Достало, когда кидаешь скрин в чат, а через день ссылка уже мертвая? Поэтому сделали imgdb.io - свой сервис загрузки картинок и скриншотов, как замена imgur для России и СНГ. Работает на наших серверах, так что грузит шустро и не норовит исчезнуть в неизвестном направлении. Короче, теперь можно спокойно кидать скрины багов, мемы, и все остальное. 😬 Кстати

37🔥13👍7🤡7🍾2👾2custom 54067412486796329032

19 Jun 2026, 13:06 UTC≈8,810 views63 reactions133 Starsread 29 August 2026

⚡ Веб-хостинг, ispmanager, SSL и BitNinja - теперь у нас Мы изменили сайт на многостраничник - теперь это не просто лендинг, а красивый и структурированный сайт. Мелочь конечно, но решили поделиться с вами нашей маленькой победой. 👑 Главное нововведение: теперь мы сотрудничаем с ispmanager. Вы можете сразу заказать VPS с предустановленной панелью ispmanager, быстро настроить сайты, почту, базы данных и всё остально

30👾12🍾7custom 54067412486796329037🔥3🤡3😎1

31 May 2026, 11:12 UTC≈9,780 views93 reactions152 Starsread 29 August 2026
Photo

✔️ На днях побывали на «ХостОбзор» - конференции, которой в этом году исполнилось 25 лет. Для нас это был первый визит, и приходить туда молодым хостингом, когда половина зала знает друг друга со времен, когда облако означало погоду, - отдельный жанр. По итогу попали в свою среду. Познакомились с коллегами по цеху и партнерами из смежных сфер: дата-центры, железки, сетевое оборудование, юриспруденция. Несмотря на ст

59🔥13👍10custom 54067412486796329034🥰3🍾2👾2

12 May 2026, 13:05 UTC≈10,600 views67 reactions14 Starsread 29 August 2026

🤖 Запускаем серию гайдов по AI-агентам Мы начинаем большую серию материалов про AI-агентов - одну из самых горячих тем 2026 года, из каждого утюга про них говорят. Простыми словами: автономный цифровой сотрудник, который сам ставит задачи, работает с инструментами, принимает решения и выполняет многошаговые процессы. В серии гайдов разберем: Что такое AI-агенты и чем они круче обычных промптов. Как запустить перво

👍29🔥12👏65🥰5🍾4🤡3custom 54067412486796329033

1 May 2026, 09:15 UTC≈12,700 views74 reactions10 Starsread 29 August 2026

⚠️ Обнаружена уязвимость в ядре Linux (Copy Fail) Появилась информация о новой уязвимости в ядре Linux - Copy Fail (CVE-2026-31431). Уязвимость позволяет локальному пользователю повысить привилегии до root. Проблема присутствует в ядре уже несколько лет и может затрагивать различные дистрибутивы Linux. Новости уже пару дней, может уже видели, но на всякий случай тоже сообщим. По механике атака частично напоминает

custom 540674124867963290349🔥87👏3🤡3🍾2👾1😎1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

Named by 2 registered channels — 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.

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

“Waicore” (@waicore), 9,685 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/waicore.

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.