Telegram RegisterThe public register of Telegram
Telegram profile photo for Vilbux.com

Channel

Vilbux.com

@vilbux

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

73subscribers

+3 since we began measuring on 18 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002080182934
TypeChannel
Username@vilbux
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live26 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/vilbux

Growth

707371.518 August 2026 — 70 subscribers19 August 2026 — 71 subscribers26 August 2026 — 73 subscribers18 August 202626 August 2026
3 measurements spanning 8 days, net +3. 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 70–73 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Aug 2026, 05:5873+2
19 Aug 2026, 01:1571+1
18 Aug 2026, 03:3070first reading

Engagement

20 posts held, back to 2 November 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
131.5%
avg views ÷ 73 subscribers
Avg views / post
96.0
1 post measured
Reaction rate
14.6%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 held20 (2 November 202517 August 2026)
Views total96
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 03:30 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

68 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 45.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3145.6%
❤‍🔥1116.2%
👌913.2%
🔥57.35%
😁34.41%
🍾22.94%
👍22.94%
👏22.94%
🥰22.94%
🤷‍♂11.47%

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 15 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 68reactions 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 2 November 2025 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.

Recent posts

17 Aug 2026, 16:26 UTC96 views14 reactionsread 18 August 2026
Photo

👀 Анонсики, анонсы ​Уже несколько месяцев мы активно ведем разработку нового личного кабинета и очень хотим поделиться с вами прогрессом. ​Уже в начале осени мы выберем самых лояльных клиентов и дадим им доступ к закрытой бета-версии. С любовью, команда Vilbux 🫶

❤‍🔥83🔥3

Signed Ivan B.

13 Jul 2026, 08:40 UTC139 views1 reactionsread 18 August 2026

⚠️ Что произошло? Ситуация с защитным провайдером Mitelis всё ещё остаётся нестабильной. Это привело к сбою в работе наших панелей сегодня ночью. После нескольких попыток восстановить штатный режим, мы приняли решение временно перенести panel.vilbux.com на защиту Cloudflare в связи с чем могут быть проблемы с доступом у некоторых клиентов. Мы понимаем все неудобства и активно работаем над решением проблемы. Спасиб

🤷‍♂1

Signed vovamod

4 Jul 2026, 09:14 UTC172 views2 reactionsread 18 August 2026
Photo

⚠️ И снова инцидент... Наш провайдер защиты Mitelis столкнулся с сильной атакой, которая затронула работоспособность сети нашей инфраструктуры. В данный момент ведутся восстановительные работы. После восстановления сети вы получите компенсацию в виде +2 дней к тарифу.

2

Signed Ivan B.

1 Jun 2026, 11:20 UTC162 views2 reactionsread 18 August 2026
Photo

☀️ Пришло лето и улучшения Друзья с первым днём лета! В честь этого дарим промокод SUMMER2026 минус 20% на покупку новых серверов. Действует до 15 июня. Мы уже обновили главную страницу и дизайн сайта. Стало проще и приятнее. Дальше будет ещё лучше. Новая AI-friendly база знаний, обновлённая панель управления и личный кабинет. Всё благодаря прокачке инфраструктуры под капотом. Удачного лета! 🔥 Команда Vilbux

2

Signed Ivan B.

11 May 2026, 13:49 UTC156 viewsread 18 August 2026

✅ Сетевая доступность восстановлена Сетевая доступность нашей инфраструктуры была восстановлена. Извиняемся за предоставленные неудобства 🙏

Signed Ivan B.

11 May 2026, 13:22 UTC133 viewsread 18 August 2026

⚠️ Ой-ой... что-то пошло не по плану. Мы приносим извинения с нашей стороны, сейчас у хоста могут возникать трудности с подключением из-за проблем у вышестоящего провайдера. Мы сообщим когда сеть будет востановлена.

Signed vovamod | Go dev

6 Apr 2026, 21:08 UTC226 views6 reactionsread 18 August 2026

Отмена технических работ В связи со сложившейся ситуацией сообщаем об отмене запланированных технических работ и их дальнейшего проведения. Как только все внутренние вопросы будут решены и стабильность гарантирована, мы дополнительно уведомим вас о новых сроках проведения технических работ. Благодарим за понимание.

👌32❤‍🔥1

Signed vovamod | Go dev

6 Apr 2026, 18:17 UTC214 views9 reactionsread 18 August 2026

⚠️ Технические работы! Уважаемые клиенты, предупреждаем о проведении обслуживания сетевой части инфраструктуры сегодня в 00:00 по МСК. Работы продлятся около 30 минут и затронут все ноды. В ходе процесса возможна кратковременная недоступность серверов. Приносим извинения за временные неудобства и благодарим за понимание! 🤝

👌6👍2❤‍🔥1

Signed Ivan B.

1 Apr 2026, 07:46 UTC162 views3 reactionsread 18 August 2026
Photo

🚀 Мы обнесли завод AMD! ​Пока весь мир только ждет официального релиза, мы уже собрали 10 нод на невышедшем железе. Ночью наши парни в балаклавах аккуратно проникли на фабрику и вывезли первую партию процессоров прямо со сборочной линии. ​⚙️ Характеристики: • CPU: AMD Ryzen 9 9950X3D2 — тот самый невышедший флагман для идеального TPS. • RAM: 256 GB DDR5 — колоссальный объем под самые тяжелые сборки. • Диски: Топовы

😁3

Signed Ivan B.

25 Feb 2026, 19:01 UTC156 views6 reactionsread 18 August 2026
Photo

⚡️ Важно! Изменение цен! Привет! Ровно два года назад мы уже были вынуждены пойти на этот шаг, и сегодня история повторяется. С сегодняшнего дня мы обновляем тарифы и повышаем их стоимость. Почему так? Современные тенденции мира диктуют свои условия. Сейчас существенно растут расходы по всей цепочке. Также мы пересмотрели политику распределения ресурсов между клиентами. Чтобы серверы работали стабильнее, без прос

4❤‍🔥1🥰1

Signed Ivan B.

12 Feb 2026, 23:57 UTC189 views5 reactionsread 18 August 2026

💚 Тех. работы окончены. Для нашей новой, и в какой-то мере экспериментальной, ноды был добавлен DNS Anycast. При подключении по адресу helium.vilbux.com у вас автоматически выберется один из нескольких доступных адресов на основе наших фильтров. Если же у вас подключен свой домен, то проверьте настроен ли он в соответствии с нашей базой знаний. Мы благодарим нашего нового провайдера защиты за данную возможность.

4🥰1

Signed Ivan B.

12 Feb 2026, 21:01 UTC181 views1 reactionsread 18 August 2026

🚀 Helium, но ещё стабильнее Друзья, этой ночью будет улучшение сети на Helium. Мы подключаем технологию DNS Anycast, чтобы ваши проекты работали без сбоев. Технические работы займут около 30-45 минут. В это время сеть может быть нестабильна. Чтобы ощутить весь эффект ваш домен должен быть подключен не через A запись, а по гайду с нашей базы знаний: ГАЙД

🔥1

Signed Ivan B.

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

Citation-graph rank

Citation-graph rank — 107,396 of 1,620,105entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“Vilbux.com” (@vilbux), 73 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/vilbux.

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.