Telegram RegisterThe public register of Telegram
Telegram profile photo for База от Забаза

Channel

База от Забаза

@NikitaZabaznov84

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

2,051subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001652994961
TypeChannel
Username@NikitaZabaznov84
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 held12
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/NikitaZabaznov84

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

2,0502,0562,0537 August 2026 — 2,055 subscribers8 August 2026 — 2,054 subscribers14 August 2026 — 2,055 subscribers17 August 2026 — 2,053 subscribers21 August 2026 — 2,052 subscribers25 August 2026 — 2,056 subscribers28 August 2026 — 2,053 subscribers30 August 2026 — 2,052 subscribers2 September 2026 — 2,053 subscribers6 September 2026 — 2,051 subscribers11 September 2026 — 2,050 subscribers19 September 2026 — 2,051 subscribers2,0517 August 202619 September 2026
12 measurements spanning 43 days, net -4. 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 2,049–2,057 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 09:562,051+1
11 Sept 2026, 20:202,050-1
6 Sept 2026, 22:402,051-2
2 Sept 2026, 11:292,053+1
30 Aug 2026, 20:472,052-1
28 Aug 2026, 04:042,053-3
25 Aug 2026, 00:092,056+4
21 Aug 2026, 04:082,052-1
17 Aug 2026, 18:382,053-2
14 Aug 2026, 06:172,055+1
8 Aug 2026, 01:112,054-1
7 Aug 2026, 10:312,055first reading

Engagement

20 posts held, back to 21 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 17 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 58s
Average length
2m 58s

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

593 reactions across 20 posts, in 33 distinct kinds. The most used accounts for 30.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱18230.7%
👍10818.2%
😢6110.3%
👏305.06%
💯284.72%
❤213.54%
😨213.54%
🔥162.70%
🤔162.70%
🤓132.19%
✍111.85%
🤷‍♂111.85%
🤗101.69%
😎81.35%
👀71.18%
🫡71.18%
😐61.01%
🍓40.675%
🙏40.675%
⚡30.506%
13 further kinds264.38%

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 593 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 21 April 2026 to 17 May 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

17 May 2026, 14:06 UTC≈4,240 views132 reactionsread 7 August 2026
Photo

Зато лавочки там больше нет. По крайней мере пока 🤣😂🤣

👍52😢27😱16👏14😨6💯4👀3🤗3

17 May 2026, 13:06 UTC≈4,450 views135 reactionsread 7 August 2026
Video message

Video message, posted without a caption

😱44😢31👍22😨10🤗7🫡6🔥5👀4

13 May 2026, 14:44 UTC≈3,690 views23 reactionsread 7 August 2026

Это ЛОХ даже посолил вместо него 😂🤣😂

👍10💯5😱4😐2❤1🤷‍♂1

13 May 2026, 14:34 UTC≈3,530 views22 reactionsread 7 August 2026
Video message

Video message, posted without a caption

💯10😱5🤷‍♂2😐2😢2❤1

12 May 2026, 16:26 UTC≈3,440 views15 reactionsread 7 August 2026
Video

Вот это поворот 😳. Данный гр-н. 👆 уверяет, что у козюли в штанах член 24 см. 😂 Конечно, я думаю, он выражается фигурально и имеет ввиду её маскулинность - мужскую черту характера, но..... 🤔

😱8🤷‍♂3👏2❤1🎉1

11 May 2026, 21:57 UTC≈2,480 views5 reactionsread 7 August 2026

https://www.youtube.com/live/1BGSCIvyalY?si=X5gB9F28BlWZWHC0

😱3👍2

10 May 2026, 09:28 UTC≈2,420 views29 reactionsread 7 August 2026
Photo

Ответил на комментарий под прямым эфиром с патриков.

😱14🤓5❤3😐2🍓1🔥1🤔1🤩1

5 May 2026, 23:39 UTC≈2,240 views12 reactionsread 7 August 2026
Video message

Video message, posted without a caption

😱7❤3👍2

5 May 2026, 21:52 UTC≈2,090 views7 reactionsread 7 August 2026

Финансовый отчёт ☝️

😱5✍1❤1

5 May 2026, 21:52 UTC≈2,050 views5 reactionsread 7 August 2026

https://youtube.com/live/v_OzgX6-Hiw?feature=share

😱4❤1

5 May 2026, 03:02 UTC≈1,740 views12 reactionsread 7 August 2026

Обзор на продукты в Москве 👆

😱7❤2👏2🔥1

5 May 2026, 03:02 UTC≈1,770 views12 reactionsread 7 August 2026

https://www.youtube.com/live/f27WVThcFbM?si=rBaLu5sP0OvOIKGd

😱6👍2✍1❤1👏1🔥1

Showing the 12 most recent of 20 posts we hold for @NikitaZabaznov84. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“База от Забаза” (@NikitaZabaznov84), 2,051 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/NikitaZabaznov84.

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.