Для гостей премии 𝐖𝐇𝐄𝐑𝐄𝟐𝐃𝐑𝐈𝐍𝐊. 𝐑𝐔𝐒𝐒𝐈𝐀𝐍 𝐁𝐀𝐑 𝐀𝐖𝐀𝐑𝐃𝐒 доступны скидки на проживание в отелях Санкт-Петербурга с 17 по 23 августа 2026 г. Остановитесь в городе на время главного барного события года: успейте не только попасть на церемонию, но и увидеть летний Петербург, его бары, рестораны и знаковые места. ▫️Cosmos St. Petersburg Nevsky Hotel 4* Стоимость от 8 000₽. Бронирование по ссылке. Промокод: wtd2026 ▫️«Novote…

Channel
Where Санкт-Петербург
@WhereSaintPetersburg
On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
805subscribers
-12 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 | -1001595852964 |
|---|---|
| Type | Channel |
| Username | @WhereSaintPetersburg |
| Created | 6 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/WhereSaintPetersburg |
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:02 | 805 | -11 |
| 8 Aug 2026, 00:55 | 816 | -1 |
| 7 Aug 2026, 05:17 | 817 | no change |
| 7 Aug 2026, 05:04 | 817 | first reading |
Engagement
7 posts held, back to 3 August 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.59%
- avg views ÷ 805 subscribers
- Avg views / post
- 20.9
- 7 posts measured
- Reaction rate
- 10.5%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 7 (3 August 2026 – 6 August 2026) |
| Views total | 146 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 05:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
4 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 50.0% | |
| 🔥 | 1 | 25.0% | |
| 🥰 | 1 | 25.0% |
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 2 of the 7 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 3 August 2026 to 6 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
Где бренд-шеф ресторанов Closer и Saro (№ 14 в рейтинге WHERETOEAT СЕВЕРО-ЗАПАД 2025) Мария Дементьева завтракает, назначает свидания, пьёт вино и заканчивает вечер? Собрали топ-места на разные случаи. #wte_блиц
👍1🔥1🥰1
В прошлом году 𝐖𝐇𝐄𝐑𝐄𝟐𝐃𝐑𝐈𝐍𝐊. 𝐑𝐔𝐒𝐒𝐈𝐀𝐍 𝐁𝐀𝐑 𝐀𝐖𝐀𝐑𝐃𝐒 2025 собрал барную индустрию в Нижнем Новгороде. Более 1000 гостей, почти 50 городов России, лучшие бары и команды со всей страны — два дня встреч, гостевых смен и главного события года для барного сообщества. А в этом году встречаемся в Санкт-Петербурге. 19 августа город станет столицей Всероссийского бархоппинга WHERE2DRINK — уникального события, не имеющего аналогов…
Мы уже познакомили вас с шорт-листами специальных номинаций, а 20 августа в Санкт-Петербурге объявим победителей IV церемонии 𝐖𝐇𝐄𝐑𝐄𝟐𝐃𝐑𝐈𝐍𝐊. 𝐑𝐔𝐒𝐒𝐈𝐀𝐍 𝐁𝐀𝐑 𝐀𝐖𝐀𝐑𝐃𝐒 и представим ежегодный рейтинг лучших баров России. В этот же день пройдёт открытая образовательная программа для профессионалов индустрии — о развитии барных проектов, управлении командами, консалтинге и маркетинге. ☑️ Елена Машина | 12:00 ➡️ «Спираль развит…
👍1
9 августа во дворе на Рубинштейна состоится очередная встреча гастрономического pop-up-проекта «НАРАЗДАЧЕ» by WHERETOEAT. За кухню в этот день отвечают Виктор Шайдецкий (Manul, Москва) и Андрей Матюха («Угли-Угли», «The Печь», Краснодар). В меню: 🍽 пельмени с осетриной Глобал Трейд и соусом из сметаны и грибов в стиле Строганов; 🍽 брискет «бургуньон», свекольная икра с капустой кимчи, картофель конфи; 🍽 картофель…
19 августа Санкт-Петербург станет столицей Всероссийского бархоппинга WHERE2DRINK! На один вечер лучшие бары города объединятся с гостевыми командами со всей России, чтобы представить авторские коктейли, созданные специально для этого вечера. К бархоппингу присоединятся десятки заведений Петербурга: гостей ждут специальные коктейльные карты, подарочные напитки и возможность за один вечер познакомиться с барной куль…
Кажется, у нас есть ещё одно доказательство того, что лучшие летние воскресенья проходят именно здесь. Питерский двор снова на несколько часов превратился в место встречи тех, кто любит хорошую еду, живое общение и гастрономические открытия. Показываем, как прошел еще один день проекта «НАРАЗДАЧЕ» by WHERETOEAT. До завершения сезона осталось всего четыре встречи. Каждое воскресенье — новое меню, новые гастрономичес…
Showing the 7 most recent of 7 posts we hold for @WhereSaintPetersburg. 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 — 577,948 of 1,480,975entries 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.
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@manulrestaurant · 1,2402 postsWhereToEat
@Where_To_Eat · 10,2552 postsLADOGA life
@ladoga_drinks · 20,0611 postLIGARE Spritz 🍊
@ligarespritz · 2,4911 postParadox Beer
@paradox_beer · 9761 postПетмол
@petmol_club · 1,3571 postPlanto
@planto_club · 3,4611 postСберПро
@sberpromedia · 10,6621 postWE FRY КЛУБ
@wefry_club · 1,0691 postWHERE2DRINK.RUSSIA
@Where_To_Drink · 2,9081 post
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.
“Where Санкт-Петербург” (@WhereSaintPetersburg), 805 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/WhereSaintPetersburg.
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.