Telegram RegisterThe public register of Telegram
Telegram profile photo for Свидетели пивовоза

Channel

Свидетели пивовоза

@pivoZOV8

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

37subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003516681795
TypeChannel
Username@pivoZOV8
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 10 September 2026
On Telegramt.me/pivoZOV8

Growth

363736.510 August 2026 — 36 subscribers10 August 2026 — 36 subscribers2 September 2026 — 37 subscribers10 August 20262 September 2026
3 measurements spanning 23 days, net +1. 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 36–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 10:5737+1
10 Aug 2026, 23:0136no change
10 Aug 2026, 07:0136first reading

Engagement

20 posts held, back to 6 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
12s

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

211 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 55.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 530108127792179688611755.5%
custom 53010346131021232499444.5%

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 211 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 6 July 2026 to 9 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

9 Aug 2026, 16:12 UTC22 views11 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 53010346131021232496custom 53010812779217968865

Signed Kappa Kappa

8 Aug 2026, 18:58 UTC26 views9 reactionsread 10 August 2026
Video message

Video message, posted without a caption

custom 53010346131021232496custom 53010812779217968863

Signed Kappa Kappa

8 Aug 2026, 17:21 UTC39 views14 reactionsread 10 August 2026
Video message

Video message, posted without a caption

custom 53010812779217968868custom 53010346131021232496

Signed Kappa Kappa

8 Aug 2026, 17:18 UTC40 views12 reactionsread 10 August 2026
Video message

Video message, posted without a caption

custom 53010812779217968868custom 53010346131021232494

Signed Kappa Kappa

8 Aug 2026, 09:53 UTC39 views16 reactionsread 10 August 2026
Video message

Video message, posted without a caption

custom 530108127792179688610custom 53010346131021232496

Signed Kappa Kappa

7 Aug 2026, 12:19 UTC42 views10 reactionsread 10 August 2026
Video message

Video message, posted without a caption

custom 53010812779217968866custom 53010346131021232494

Signed Kappa Kappa

7 Aug 2026, 10:45 UTC28 views5 reactionsread 10 August 2026
Forwarded from @truefrozenzederVideo

Video, posted without a caption

custom 53010812779217968863custom 53010346131021232492

Signed Kappa Kappa

4 Aug 2026, 21:13 UTC42 views7 reactionsread 10 August 2026
Video

Video, posted without a caption

custom 53010346131021232494custom 53010812779217968863

Signed Kappa Kappa

2 Aug 2026, 06:21 UTC48 views8 reactionsread 10 August 2026
Photo

Хуле орешь

custom 53010346131021232495custom 53010812779217968863

Signed Kappa Kappa

2 Aug 2026, 04:12 UTC43 views14 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 53010812779217968868custom 53010346131021232496

Signed Kappa Kappa

30 Jul 2026, 08:52 UTC55 views8 reactionsread 10 August 2026
Photo

Пиздец

custom 53010812779217968865custom 53010346131021232493

Signed Kappa Kappa

29 Jul 2026, 18:19 UTC46 views10 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 53010346131021232495custom 53010812779217968865

Signed Kappa Kappa

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

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

“Свидетели пивовоза” (@pivoZOV8), 37 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/pivoZOV8.

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.