Telegram RegisterThe public register of Telegram
Telegram profile photo for 96

Channel

96

@vlkulka

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

132subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001896447321
TypeChannel
Username@vlkulka
CreatedBetween 1 November 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/vlkulka

Growth

132133132.57 August 2026 — 132 subscribers9 August 2026 — 132 subscribers15 August 2026 — 133 subscribers22 August 2026 — 132 subscribers7 August 202622 August 2026
4 measurements spanning 15 days. 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 132–133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:03132-1
15 Aug 2026, 07:49133+1
9 Aug 2026, 00:31132no change
7 Aug 2026, 15:03132first reading

Engagement

9 posts held, back to 9 June 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
106.1%
avg views ÷ 132 subscribers
Avg views / post
140
1 post measured
Reaction rate
10.7%
reactions ÷ views · ER floor
Posts in window
1
of 9 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 30 July 2026
Posts held9 (9 June 202630 July 2026)
Views total140
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 00: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.

Reaction mix

68 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 32.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52874150785329617552232.4%
custom 52243042363800636901826.5%
custom 52244879450162171091116.2%
custom 538662790824252064568.82%
custom 545390214566329668368.82%
custom 522664095199215718134.41%
custom 522870956286073494711.47%
custom 542036537027384561011.47%

Custom emoji. Every row above is a 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 9 of the 9 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 9 most recent posts we hold, published 9 June 2026 to 30 July 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

30 Jul 2026, 18:31 UTC140 views15 reactionsread 9 August 2026

Posted without readable text

custom 54539021456632966836custom 52266409519921571813custom 52243042363800636902custom 52244879450162171092custom 52874150785329617552

17 Jul 2026, 20:16 UTC285 views7 reactionsread 9 August 2026
Photo

La distance est nécessaire pour la beauté

custom 53866279082425206453custom 52244879450162171091custom 52287095628607349471custom 52874150785329617551custom 54203653702738456101

5 Jul 2026, 13:55 UTC326 views7 reactionsread 9 August 2026
Photo

sun🐆

custom 52244879450162171094custom 53866279082425206453

12 Jun 2026, 20:33 UTC533 views4 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52244879450162171094

9 Jun 2026, 19:17 UTC337 views6 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52243042363800636906

9 Jun 2026, 18:47 UTC292 views11 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52874150785329617558custom 52243042363800636903

Showing the 9 most recent of 9 posts we hold for @vlkulka. 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.

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

“96” (@vlkulka), 132 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/vlkulka.

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.