А?
🔥7😁3🍾2custom 52131334473499504922❤1
Signed Zlatek Kovrizhechko

Channel
@saliwa_spb
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
447subscribers
-7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001542773531 |
|---|---|
| Type | Channel |
| Username | @saliwa_spb |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/saliwa_spb |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 11:36 | 447 | -1 |
| 5 Sept 2026, 03:19 | 448 | +2 |
| 28 Aug 2026, 17:43 | 446 | -7 |
| 20 Aug 2026, 23:57 | 453 | -1 |
| 13 Aug 2026, 13:16 | 454 | -1 |
| 7 Aug 2026, 10:44 | 455 | +1 |
| 6 Aug 2026, 19:15 | 454 | no change |
| 6 Aug 2026, 18:33 | 454 | first reading |
17 posts held, back to 1 July 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 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 17 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.
254 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 80 | 31.5% | |
| 🔥 | 58 | 22.8% | |
| custom 5215514289456039627 | 23 | 9.06% | |
| custom 5208647010411896056 | 16 | 6.30% | |
| custom 5213133447349950492 | 15 | 5.91% | |
| 👍 | 11 | 4.33% | |
| 🥰 | 11 | 4.33% | |
| 👏 | 10 | 3.94% | |
| ⚡ | 7 | 2.76% | |
| 🍾 | 6 | 2.36% | |
| custom 5213339700269440276 | 5 | 1.97% | |
| 👻 | 5 | 1.97% | |
| 😁 | 3 | 1.18% | |
| custom 5210934144921519445 | 2 | 0.787% | |
| 🍌 | 1 | 0.394% | |
| 🤔 | 1 | 0.394% |
Custom emoji. 5 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 17 of the 17 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 254 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 1 July 2026 to 10 July 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.
А?
🔥7😁3🍾2custom 52131334473499504922❤1
Signed Zlatek Kovrizhechko
Идёт возня!
👍7custom 52133397002694402763❤2🥰1
Signed Zlatek Kovrizhechko
Photo, posted without a caption
custom 52155142894560396279❤7👏2
Signed Zlatek Kovrizhechko
Хит сезона! Все жоска двигаются на панамах! Мы решили не отставать, вышивка, со шнурком и широкие поля, получилось годно! Детали уточняйте в комментах P. S. Модель Виталити )))
⚡7🔥2❤1
Signed Zlatek Kovrizhechko
в конце 2020-го мы презентовали в баре Luminous наш первый в жизни хейзи айпиэй Ocelot. сегодня в той же локации мы показываем и наливаем сразу целый вагон сортов! премьерный шеринг (всего по 3 банки на сорт): TH3 W6RST – тройной хейзи айпиэй 9,5 ABV с тройным сухим охмелением! ПАНАМА – хейзи айпиэй в коллабе с Oh, My Beer на Mango Mandes и Krush, Krush Lupomax и Motueka. 7 ABV Росомаха – хейзи пейл эль, сброженный …
❤10custom 52155142894560396272custom 52086470104118960561
ребзя, а помните мы делали драйх-хопд джин на наше шестилетие? так вот, инфа для самых внимательных: завтра в качестве велком-дринка в Люминосе мы выкатим коллабу с братвой из Püre Bootleg – экспериментальный бэтч ямайского рома с сухим охмелением Riwaka! кто шарит за дандеры и Ямайку – велкам, кто пока не шарит – расскажем)
🔥9custom 52155142894560396273👍2🍾1👏1
говорят, среда – это маленькая пятница 😊 а в пятницу у нас, северных петербуржцев, распространена традиция – проверить работает ли секретный тапрум на Прокофьева, 10? на Прокофьева – увы, закрыто заведение! но есть и хорошие новости – ребята теперь раздают в баре LUMINOUS! и в эту пятницу 10.07 в 19-30 мы в @luminousbar будем наливать и пояснять за все припасённые пивчанские – 3 сорта на кране, 5 в банках и секретн…
custom 52155142894560396276❤5custom 52131334473499504924👻2🥰2🍌1👏1custom 52086470104118960561
Шурико из Хлеба
custom 52131334473499504925🔥3❤1👏1👻1
Signed Zlatek Kovrizhechko
Video message, posted without a caption
❤6custom 52109341449215194452👍1🔥1custom 52086470104118960561
Signed Zlatek Kovrizhechko
Ожидаем все вместе!
🔥7❤1👻1custom 52131334473499504921custom 52155142894560396271
Signed Zlatek Kovrizhechko
Ду!
🔥4❤3custom 52086470104118960562🍾1👻1
Signed Zlatek Kovrizhechko
А вы где ? Мы тут пивас наливаем
custom 52086470104118960568🥰7🔥2custom 52155142894560396271
Signed Zlatek Kovrizhechko
Showing the 12 most recent of 17 posts we hold for @saliwa_spb. 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.
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.
Named by 3 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.
@saliwa_spb named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“SALIWA” (@saliwa_spb), 447 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/saliwa_spb.
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.