Telegram RegisterThe public register of Telegram
Telegram profile photo for Вероника Дичка

Channel

Вероника Дичка

@VeronikaDichka

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

7,678subscribers

+136 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-1001612347987
TypeChannel
Username@VeronikaDichka
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 live19 September 2026
Measurements held13
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/VeronikaDichka

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 72% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

7,5307,6937,611.57 August 2026 — 7,542 subscribers7 August 2026 — 7,542 subscribers10 August 2026 — 7,540 subscribers14 August 2026 — 7,536 subscribers17 August 2026 — 7,530 subscribers20 August 2026 — 7,536 subscribers23 August 2026 — 7,560 subscribers26 August 2026 — 7,562 subscribers30 August 2026 — 7,565 subscribers1 September 2026 — 7,566 subscribers6 September 2026 — 7,693 subscribers11 September 2026 — 7,691 subscribers14 September 2026 — 7,678 subscribers7,6787 August 202614 September 2026
13 measurements spanning 38 days, net +136. 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 7,506–7,717 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 23:017,678-13
11 Sept 2026, 05:377,691-2
6 Sept 2026, 10:377,693+127
1 Sept 2026, 21:357,566+1
30 Aug 2026, 02:337,565+3
26 Aug 2026, 17:427,562+2
23 Aug 2026, 19:557,560+24
20 Aug 2026, 05:217,536+6
17 Aug 2026, 13:487,530-6
14 Aug 2026, 07:377,536-4
10 Aug 2026, 20:387,540-2
7 Aug 2026, 17:317,542no change
7 Aug 2026, 17:297,542first reading

Engagement

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

ERR · 30 days
23.0%
avg views ÷ 7,678 subscribers
Avg views / post
1,770
5 posts measured
Reaction rate
4.00%
reactions ÷ views · ER floor
Posts in window
5
of 39 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 28 August 2026
Posts held39 (28 July 202628 August 2026)
Views total8,830
Reactions total353
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 21:52 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
4m 16s
Average length
18s

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

3,706 reactions across 39 posts, in 29 distinct kinds. The most used accounts for 30.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,14430.9%
99726.9%
👍85523.1%
😁3168.53%
❤‍🔥742.00%
🥰581.57%
💅571.54%
👏401.08%
🤣401.08%
😱170.459%
🍾140.378%
🏆140.378%
🐳130.351%
🤔130.351%
💊100.27%
🙈100.27%
70.189%
🙏70.189%
😘60.162%
💯30.081%
9 further kinds110.297%

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

Measured over the 39 most recent posts we hold, published 28 July 2026 to 28 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

28 Aug 2026, 15:23 UTC≈1,580 views42 reactionsread 28 August 2026
Video message

Video message, posted without a caption

👍2412🥰4🐳1💅1

27 Aug 2026, 11:53 UTC≈1,510 views102 reactionsread 28 August 2026
Video message

Video message, posted without a caption

🔥39❤‍🔥26👍199👏32🐳1👀1

26 Aug 2026, 16:50 UTC≈1,770 views77 reactionsread 28 August 2026
Photo

Народ, спасибо, что пришли! 🩵 Эта встреча в Казани получилась именно такой, как я люблю - уютной, честной и очень душевной. Мы говорили обо всем: о рыбалке , снастях , турнирах , и даже немного о личном. Разыграли кучу крутых подарков, а кто-то, даже уехал с Narval Euphoria в руках, а значит, возможностью участвовать в розыгрыше миллиона🙌 Очень приятно было увидеть на встрече столько детей и даже тех, кто еще не

👍44🔥1912🐳1💅1

25 Aug 2026, 17:59 UTC≈1,960 views49 reactionsread 28 August 2026
Video message

Video message, posted without a caption

33🔥13🥰2💅1

25 Aug 2026, 16:03 UTC≈2,010 views83 reactionsread 28 August 2026
Video message

Video message, posted without a caption

43🔥30🥰5👏3🎉1💅1

24 Aug 2026, 08:29 UTC≈2,500 views102 reactionsread 28 August 2026
Video

Никитос придумал, а страдать мне … Съемки закончили , мчу до Казани , где буду рада лицезреть вас завтра на встрече с подписчиками 🩵

😁5826🔥9👍7💅1🤣1

23 Aug 2026, 15:43 UTC≈2,450 views60 reactionsread 28 August 2026
Video message

Video message, posted without a caption

👍36🔥145💅2🤔2🥴1

22 Aug 2026, 12:02 UTC≈2,670 views89 reactionsread 28 August 2026
Video message

Video message, posted without a caption

😁5120👍15💅3

22 Aug 2026, 09:18 UTC≈2,710 views86 reactionsread 28 August 2026
Video message

Video message, posted without a caption

🔥56👍199💅2

21 Aug 2026, 09:35 UTC≈2,440 views48 reactionsread 28 August 2026
Forwarded from @volgabaitsteamPhoto

Встреча с командой Volga Baits в Казани! 🔥 25 августа, перед стартом 2 тура BetBoom PAL, который пройдёт в Казани на Куйбышевском водохранилище, увидимся с вами лично! Экипаж Дичка-Алекно приедет пообщаться с подписчиками, а вместе с ними — Андрей Ферафонтов и Олег Малацион! Что в программе: — спортсмены поделятся эмоциями после первого этапа BetBoom PAL и расскажут, как это было — Андрей Ферафонтов расскажет про

👍356😁3🥰2💅1🤔1

20 Aug 2026, 10:46 UTC≈5,810 views110 reactionsread 28 August 2026
Video message

Video message, posted without a caption

61👍28👏14🥰3💅2🔥1😨1

18 Aug 2026, 15:37 UTC≈2,710 views45 reactionsread 28 August 2026
Forwarded from @volgabaitsteamVideo

ЗАКУЛИСЬЕ ПОДГОТОВКИ: ЭТО НЕ ВОШЛО В ФИЛЬМ | VGB TEAM LIFE 🔥 Открываем новую серию из жизни команды. Это первая из двух частей, и в ней покажем, что происходило до старта 1 этапа BetBoom PAL. Как экипажи готовились, что чувствовали, о чём переживали и шутили за пару дней до турнира — камера была рядом всё это время. Никитос всё задокументировал, так что сейчас увидите настоящие эмоции без сценария👇🏻 📺 Смотреть на

👍3110🎉1💅1🔥1🥰1

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

Forward network

Republished by

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

VOLGA BAITS | Рыбалка на спиннинг
@volgabaitsteam · 23,824
Telegram ranks this channel #8 of 70 here — alongside 69 others — read 17 September 2026
MAIN TARGET. Рыбалка
@maintarget · 22,525
Telegram ranks this channel #21 of 71 here — alongside 70 others — read 20 September 2026
СИБИРИЯ
@SIBIRIA1 · 22,184
Telegram ranks this channel #27 of 56 here — alongside 55 others — read 21 September 2026
КИЛЬВАТЕР
@kilvaterZhuralife · 30,450
Telegram ranks this channel #31 of 66 here — alongside 65 others — read 20 September 2026
FINNTRAIL | Рыболовное сообщество
@finntrail_fishing · 37,935
Telegram ranks this channel #44 of 64 here — alongside 63 others — read 1 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Вероника Дичка” (@VeronikaDichka), 7,678 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/VeronikaDichka.

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.