Telegram RegisterThe public register of Telegram
Telegram profile photo for Z U B K O V A•3

Channel

Z U B K O V A•3

@zubkova3

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

371subscribers

+11 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-1002493378271
TypeChannel
Username@zubkova3
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/zubkova3

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

3593713657 August 2026 — 360 subscribers8 August 2026 — 360 subscribers14 August 2026 — 359 subscribers21 August 2026 — 360 subscribers27 August 2026 — 359 subscribers3 September 2026 — 360 subscribers11 September 2026 — 365 subscribers19 September 2026 — 371 subscribers7 August 202619 September 2026
8 measurements spanning 43 days, net +11. 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 357–373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 00:19371+6
11 Sept 2026, 07:38365+5
3 Sept 2026, 06:35360+1
27 Aug 2026, 20:43359-1
21 Aug 2026, 06:46360+1
14 Aug 2026, 16:14359-1
8 Aug 2026, 06:34360no change
7 Aug 2026, 11:03360first reading

Engagement

5 posts held, back to 4 August 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
12s

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

155 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 26.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53258852466321223284126.5%
custom 52828181363813405893120.0%
custom 54746388748336027282415.5%
custom 54629274653850483011912.3%
custom 5456300644379939859159.68%
custom 5262475504820200370138.39%
custom 5409192601263830163117.10%
💯10.645%

Custom emoji. 7 of the rows above are 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 5 of the 5 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 155 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 4 August 2026 to 7 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
1
across the posts below
Posts paid on
1
of 5 we hold a reading for · 20%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @zubkova3. 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 5 most recent posts we hold for this entry, published 4 August 2026 to 7 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

7 Aug 2026, 12:07 UTC120 views32 reactionsread 8 August 2026
Photo

❤️

custom 528281813638134058913custom 547463887483360272810custom 54563006443799398597custom 54091926012638301632

6 Aug 2026, 15:56 UTC146 views34 reactionsread 8 August 2026
Photo

такие вот будни 🙂‍↕️

custom 547463887483360272814custom 54091926012638301639custom 53258852466321223288custom 54629274653850483012custom 54563006443799398591

5 Aug 2026, 18:57 UTC160 views21 reactionsread 8 August 2026
Photo

🏙️/🌃

custom 532588524663212232811custom 52828181363813405896custom 52624755048202003704

4 Aug 2026, 18:12 UTC169 views36 reactions1 Starread 8 August 2026
Photo

мой маленький сладкий пирожок ❤️

custom 532588524663212232815custom 528281813638134058912custom 52624755048202003709

4 Aug 2026, 15:32 UTC173 views32 reactionsread 8 August 2026
Photo

любить или быть любимым? играть и проигрывать или сидеть и побеждать? 😂😂 ладно, шучу, несмотря ни на что, продолжаем работать и стараться, рано или поздно всё будет хорошо 🤞🏼

custom 546292746538504830117custom 53258852466321223287custom 54563006443799398597💯1

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

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Z U B K O V A•3” (@zubkova3), 371 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zubkova3.

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.