Channel
@CallmeVidairy
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
224subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001895391174 |
|---|---|
| Type | Channel |
| Username | @CallmeVidairy |
| Created | Between 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/CallmeVidairy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:24 | 224 | -2 |
| 8 Aug 2026, 10:19 | 226 | no change |
| 7 Aug 2026, 14:38 | 226 | first reading |
19 posts held, back to 2 August 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. It is computed over the 13 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (2 August 2026 – 7 August 2026) |
| Views total | 1,120 |
| Reactions total | 64 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:19 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.
64 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 32.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 32.8% | |
| 👍 | 12 | 18.8% | |
| 🔥 | 11 | 17.2% | |
| custom 5787388437594116153 | 9 | 14.1% | |
| custom 5807528471252962886 | 4 | 6.25% | |
| custom 5994712526221216919 | 3 | 4.69% | |
| 🐳 | 3 | 4.69% | |
| 💯 | 1 | 1.56% |
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 areTelegram’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 13 of the 19 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 64reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 August 2026 to 7 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.
#заметкиосмене внезапно смена выдалась насыщенной, особенно под конец смены. Я даже задержалась на 30 мин. Еще рилс утром улетел в космос по просмотрам, и продолжает набирать. Отсюда бешеный траф на лоял какойто. я даже чувствую фомо, что не всех лидов могу обработать. довольна сменой, можно идти отдыхать
👍3
#AI в моей работе и жизни часть 2 Планирование Вы наверное заметили что рубрика ежедневный #план пропала с радаров. Я подумала что она скучновата для читателя. решила все мои планы объединить в одном месте. В целом я довольно давно веду для планов обычный Гугл календарь. Пробовала Notion, но для меня он слишком перегружен функционалом. Когда Моя подруга, которая шарит за IT рассказала что сделала под себя бота, и в…
🐳2💯1
#почитать
#25книг книга 1️⃣8️⃣ Вы когда-нибудь задумывались почему мазохисты названы так? так вот, благодаря этому чуваку. Это один из первых литературных авторов, герои которых подчинялись сильным женщинам, страдали и любили унижения. Пишет он своеобразно, конечно, либо это особенности русской локализации. А еще заметны одни и те же элементы из повести в повесть. Не забывайте историческую особенность автора, он жил в Австрии …
🔥5
#хвастаюсь я кажется карму почистила☺️ подоила мужика 30 на стриме 30 мин пока убиралась☺️, храни тебя бог чувак.
#заметкиосмене не смотря на то что было скучно один кусок смены, в целом норм. я довольна неделей, пусть и филонила в пятницу. А теперь пора отдыхать и драить хату.
upd: я докрутила продажу уже сама и лид принес мне хороший чек, сегодня лоял тащит👌
custom 57873884375941161536
#хвастаюсь как ты поймешь что траф с инсты работает? когда пока ты в офлайне гуляешь с кофе, какой-то теплый лид с ноги врывается на лоял и делает продажу на 56$, приятна😌 значит все работает👌 для заметки, у меня основные продажи на лояле с онлайна, пока я стримлю или прям на стриме, это второй раз за все 3 года на площадке, когда чел просто покупает контент.
👍6custom 57873884375941161533custom 59947125262212169193
#заметкиосмене внезапно пришел постоянник, он как красно солнышко приходит под конец смены. в целом было тухловато, но что поделать лето
custom 58075284712529628864
Кажется мы с Песцом совпали по вайбам августа?
👍 Сколько чужих сервисов держат твой бизнес за горло? В комментариях в Content Secrets я не так давно жаловалась, что у нас отлетело достаточно большое сообщество на Reddit, а в выходные отлетело ещё одно. В связи с этим на меня напала рефлексия, и в воскресенье я посчитала, на скольких чужих сервисах висит мой доход прямо сейчас, всплакнула над грустными историями, когда из-за чьих-то косяков или изменения правил л…
❤4
Короч сняла контент, мне понравилось очень удобно, надо привыкнуть и не дергать камеру каждые 10 мин
Showing the 12 most recent of 19 posts we hold for @CallmeVidairy. 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Call_me_Vi” (@CallmeVidairy), 224 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/CallmeVidairy.
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.