Telegram RegisterThe public register of Telegram
Telegram profile photo for VzorKnopki

Channel

VzorKnopki

@vzor_knopki

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

203subscribers

+0 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-1002364378384
TypeChannel
Username@vzor_knopki
Description«Снимаю на многокнопочное» ෴෴෴෴෴෴෴෴ Продублировала старые посты из https://vk.com/vzoruzorknopki ෴෴෴෴෴෴෴෴ Спасибо што оставляете свои следы Связь @pobelokobelok ෴෴෴෴෴෴෴෴
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/vzor_knopki

Previous handles

@vzor_knopki was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@vzor_knopki
held 7 August 20267 August 2026

Growth

2036 Aug 2026, 17:48 — 203 subscribers7 Aug 2026, 04:01 — 203 subscribers6 Aug 2026, 17:487 Aug 2026, 04:01
2 measurements taken within a single day. 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 202–204 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 04:01203no change
6 Aug 2026, 17:48203first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3,800

Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

500 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 24.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 542497615081008604812124.2%
custom 520181677546068889910521.0%
custom 53999968830095553986012.0%
custom 54178336674414787615110.2%
custom 5334693146519420496357.00%
custom 5375512236527724997326.40%
custom 5197707045809175512306.00%
custom 5224704196619556791295.80%
custom 5435984641616016320193.80%
custom 5397812260779345089183.60%

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 are Telegram’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 20 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 500 reactions 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 19 July 2026 to 6 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.

Telegram Stars

Stars received
21
across the posts below
Posts paid on
7
of 20 we hold a reading for · 35%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vzor_knopki. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 19 July 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 11:55 UTC61 views13 reactions3 Starsread 7 August 2026
Photo

Photo, posted without a caption

custom 533469314651942049613

5 Aug 2026, 11:55 UTC83 views18 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 542497615081008604812custom 52247041966195567913custom 54178336674414787613

4 Aug 2026, 11:55 UTC109 views26 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 519770704580917551215custom 53999968830095553986custom 54249761508100860485

3 Aug 2026, 11:55 UTC148 views18 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 520181677546068889918

2 Aug 2026, 14:48 UTC165 views23 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 541783366744147876114custom 54359846416160163209

1 Aug 2026, 14:48 UTC336 views32 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 542497615081008604816custom 53755122365277249979custom 51977070458091755127

31 Jul 2026, 14:48 UTC448 views27 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 539999688300955539815custom 542497615081008604812

30 Jul 2026, 11:55 UTC216 views20 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 542497615081008604814custom 52018167754606888996

29 Jul 2026, 11:55 UTC224 views22 reactions2 Starsread 7 August 2026
Photo

Photo, posted without a caption

custom 537551223652772499715custom 53999968830095553987

28 Jul 2026, 11:55 UTC234 views18 reactions2 Starsread 7 August 2026
Photo

Photo, posted without a caption

custom 520181677546068889918

27 Jul 2026, 11:55 UTC238 views33 reactions2 Starsread 7 August 2026
Photo

Photo, posted without a caption

custom 522470419661955679114custom 51977070458091755126custom 52018167754606888995custom 53346931465194204963custom 54178336674414787613custom 54359846416160163202

26 Jul 2026, 11:55 UTC224 views24 reactions2 Starsread 7 August 2026
Photo

Photo, posted without a caption

custom 520181677546068889919custom 54359846416160163203custom 53755122365277249972

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

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

“VzorKnopki” (@vzor_knopki), 203 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/vzor_knopki.

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.