Telegram RegisterThe public register of Telegram

Channel

Підваал Ваала 🚜

@vaal_dub

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

25subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002569738361
TypeChannel
Username@vaal_dub
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/vaal_dub

Growth

2325246 August 2026 — 23 subscribers11 August 2026 — 23 subscribers13 August 2026 — 25 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, net +2. 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 23–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:4325+2
11 Aug 2026, 11:3123no change
6 Aug 2026, 05:3823first reading

Engagement

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

ERR · 30 days
228.4%
avg views ÷ 25 subscribers
Avg views / post
57.1
10 posts measured
Reaction rate
2.57%
reactions ÷ views · ER floor
Posts in window
10
of 17 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held17 (17 March 20268 August 2026)
Views total571
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 11:31 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
7m 10s
Average length
1m 01s

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

27 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 51.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1451.9%
🔥622.2%
🤣27.41%
🌚13.70%
🤯13.70%
🥰13.70%
🥱13.70%
🫡13.70%

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

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

Recent posts

8 Aug 2026, 19:04 UTC13 views1 reactionsread 11 August 2026
Forwarded from @robotaholosomPhoto

Героїня зі стрічкою [WEBRip Ai Rem 2160p x265 АС3 5.1] [UKR MVO, UKR SUB] Додано з субтитрами і озвученням! Жанр: бойовик, пригоди, драма, фентезі, романтика Опис: Сапфіра — принцеса королівства, якого більше не існує. Втративши все на батьківщині, у Сільверленді, через катастрофу, відому як «Нерґал», вона блукає у відчаї, аж поки зрештою не дістається Ґолдленду. Обтяжена своїм минулим, вона поступово починає зна

1

8 Aug 2026, 19:04 UTC26 viewsread 11 August 2026

я тут озвучив одного дуже класного хлопця, хто здогадається, того цьомну. Тому всі нумо дивитися!

31 Jul 2026, 17:49 UTC57 views1 reactionsread 11 August 2026
Video

ну мені дали ще одного тут класного персонажа, по інтонації зрозумієте)

1

31 Jul 2026, 17:43 UTC67 views2 reactionsread 11 August 2026
Video

ну... я незнаю, пропозиція спокуслива, але краще я стану чарівником вже таким чином...

2

31 Jul 2026, 10:07 UTC38 views2 reactionsread 11 August 2026
Forwarded from @robotaholosom

Наш актор Va'al завітав на гостину до Єдиного Україномовного Ком'юніті та взяв участь у новому випуску подкасту! Мали дуже теплу та затишну розмову: поговорили про світ озвучення, тонкощі роботи з голосом, улюблені тайтли й популяризацію українського контенту. 🎬 Запрошуємо до перегляду на YouTube: • Єдине Україномовне Ком'юніті — це спільнота, що просуває українську мову в інтернеті. Посилання на Discord-сервер: ht

1🔥1

31 Jul 2026, 10:07 UTC48 views2 reactionsread 11 August 2026

прикиньте, я на інтерв'ю був

🔥2

19 Jul 2026, 17:48 UTC75 views1 reactionsread 11 August 2026
Forwarded from @robotaholosomPhoto

Ким ти хочеш стати після переродження в іншому світі Я «Ребром героя» [02 з 12] [WEBRip Ai Rem 2160p x265 AAC 2.0] [UKR SUB, UKR MVO] Перекладено і озвучено на замовлення сайту Coani.net Перезалито першу та викладено другу серію з субтитрами та озвученням! Переглянути можна сайті за посиланням: https://coani.net/catalog/my-ribdiculous-reincarnation/my-ribdiculous-reincarnation-season-1 Онлайн в телеграм: https://

🥰1

19 Jul 2026, 17:48 UTC68 views1 reactionsread 11 August 2026

Так, всім обов'язково дивитися хто любить крінж і ісекаї!

🫡1

17 Jul 2026, 08:48 UTC87 views2 reactionsread 11 August 2026
Video

Мені треба брати уроки пікапу у цього хлопця

🔥2

5 Jul 2026, 15:41 UTC146 views1 reactionsread 11 August 2026
Video

Якого цікавого персонажа мені дали, хлопців за дружину бере

🌚1

31 May 2026, 12:52 UTC231 viewsread 11 August 2026
Forwarded from @robotaholosomPhoto

Наш етер вже сьогодні о 18:00 ‼️‼️‼️ Приєднуйтеся до нас на нашому 😊 YouTube 😊 😊 YouTube 😊 😊 YouTube 😊 Будемо дивитися презентацію, трейлери та обговорювати тайтли які вийдуть вже цього літа 🔥 Тим часом у нас є ще нові донатики, щиро вам дякуємо! 😘 (1000 грн від котика який нам довіряє спрямували на Перекур за супермаркетом з тобою) Умови збору ‼️ - 3 000 грн. для перекладу аніме - 5 000 грн. озвучення одного а

Showing the 12 most recent of 17 posts we hold for @vaal_dub. 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 — 201,490 of 1,340,412entries 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

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

“Підваал Ваала 🚜” (@vaal_dub), 25 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vaal_dub.

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.