Telegram RegisterThe public register of Telegram

Channel

Balkonsky Feedback | Отзывы

@balkonskotz

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

13subscribers

+1 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-1002056507637
TypeChannel
Username@balkonskotz
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/balkonskotz

Growth

121312.57 August 2026 — 12 subscribers12 August 2026 — 12 subscribers15 August 2026 — 13 subscribers7 August 202615 August 2026
3 measurements spanning 9 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 12–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 19:0413+1
12 Aug 2026, 04:3012no change
7 Aug 2026, 03:1512first reading

Engagement

19 posts held, back to 27 September 2025the 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.

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

What this channel posts

Video runtime
1m 11s
Average length
36s

Measured directly from 2 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.

Recent posts

25 Feb 2026, 11:30 UTC241 viewsread 12 August 2026

Ну самого дешёвого набрали мы, следовало ожидать что несколько залуп будет

25 Feb 2026, 11:30 UTC242 viewsread 12 August 2026

Бля несколько шмоток пиздец просто ебаная синтетика растянутая без бирок вообще такая залупа ахахаха

23 Feb 2026, 12:11 UTC233 viewsread 12 August 2026
Photo

Все три айтема куплены у балконского в шопе, легит жб! Помогли подобрать как размеры так и сами айтемы, все четко село, рекомендую!

23 Jan 2026, 12:44 UTC257 viewsread 12 August 2026
Photo

Нил, привет. Все огонь, спасибо большое. Худас получил, все довольны ;-)

22 Dec 2025, 12:34 UTC298 viewsread 12 August 2026

забрал все супер ахуеено,самое главное цена супер @balkonskstore 🥰

9 Nov 2025, 09:47 UTC329 viewsread 12 August 2026
Photo

Андрей как всегда радует, забрал сегодня 3 шмотки. Одел маструм на друга, мы оба в ахуе

25 Oct 2025, 16:07 UTC323 viewsread 12 August 2026
Photo

Привет! Забрала бокс, футболка супер, спасибо большое, буду заказывать еще 🫶🏻

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

Citation-graph rank

Citation-graph rank — 118,545 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“Balkonsky Feedback | Отзывы” (@balkonskotz), 13 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/balkonskotz.

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.