📍Канал Грибоедова у Пикалова моста. 1973/2023 год. 💡Интересный факт: а вы узнали откуда верхнее фото? Правильно, это кадр из к/ф «Невероятные приключения итальянцев в России». 🎞Санкт-Петербург в объективе времени🎞
❤16👍7

Channel
@spb_in_time
On this record: Topic · Growth · Engagement · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
6,376subscribers
-31 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001887376651 |
|---|---|
| Type | Channel |
| Username | @spb_in_time |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/spb_in_time |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 40% 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 |
|---|---|---|
| 14 Sept 2026, 13:39 | 6,376 | -3 |
| 10 Sept 2026, 17:39 | 6,379 | -5 |
| 5 Sept 2026, 13:56 | 6,384 | -10 |
| 2 Sept 2026, 00:05 | 6,394 | -5 |
| 29 Aug 2026, 18:48 | 6,399 | -8 |
| 24 Aug 2026, 06:51 | 6,407 | +2 |
| 20 Aug 2026, 09:04 | 6,405 | -2 |
| 17 Aug 2026, 12:05 | 6,407 | +13 |
| 14 Aug 2026, 10:38 | 6,394 | -1 |
| 11 Aug 2026, 04:48 | 6,395 | -5 |
| 8 Aug 2026, 06:11 | 6,400 | -7 |
| 7 Aug 2026, 07:17 | 6,407 | first reading |
25 posts held, back to 20 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 10 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 25 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
678 reactions across 24 posts, in 6 distinct kinds. The most used accounts for 58.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 398 | 58.7% | |
| 👍 | 263 | 38.8% | |
| 😢 | 8 | 1.18% | |
| 🔥 | 6 | 0.885% | |
| 😍 | 2 | 0.295% | |
| 👎 | 1 | 0.147% |
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 24 of the 25 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 678 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 20 July 2026 to 11 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFJD6P8m | 1 | 22 July 2026 | 22 July 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 25 most recent posts we hold, published 20 July 2026 to 11 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
📍Канал Грибоедова у Пикалова моста. 1973/2023 год. 💡Интересный факт: а вы узнали откуда верхнее фото? Правильно, это кадр из к/ф «Невероятные приключения итальянцев в России». 🎞Санкт-Петербург в объективе времени🎞
❤16👍7
📍Набережная реки Фонтанки. 1902/2023 год. 💡Интересный факт: невероятно, но та, первая гранитная набережная до сих пор «удерживает» русло Фонтанки. 🎞Санкт-Петербург в объективе времени🎞
❤17🔥6👍5
📍Улица Шкапина. 1977/2023 год. 💡Интересный факт: улица Шкапина — одно из немногих мест, где во дворах сохранилась брусчатка. увы, сегодня оплакивают свое мощёное прошлое улица Репина, Академический и Днепровск... 🎞Санкт-Петербург в объективе времени🎞
👍13❤8😢5
📍Канал Круштейна / Адмиралтейский канал. 1932/2023 год. 💡Интересный факт: после революции канал был переименован в честь большевика Круштейна и стал называться каналом Круштейна. А в 1956 году каналу вернули историческое название Адмиралтейский. 🎞Санкт-Петербург в объективе времени🎞
👍18❤9
📍Набережная канала Грибоедова. 1992/2023 год. 💡Интересный факт: в 1923 году канал был переименован в честь русского драматурга и дипломата А. С. Грибоедова, проживавшего в одном из домов на набережной. 🎞Санкт-Петербург в объективе времени🎞
❤19👍8
📍Церковь святого Исидора Юрьевского на канале Грибоедова. 1912/2023 год. 💡Интересный факт: церковь возвели в 1903-1907 годах с благословления святого Иоанна Кронштадского, который и внес первые пожертвования в строительство будущего храма. Необходимость в своем приходе возникла у четырех тысяч эстонцев, проживавших на тот момент в городе. Эстонский православный приход возник в Коломне, а в Петербурге богослужения с…
👍17❤12
📍Могилёвский мост. 1955/2023 год. 💡Интересный факт: название моста происходит от Могилёвской улицы, которая в свою очередь получила такое название от белорусского города Могилёв. 🎞Санкт-Петербург в объективе времени🎞
❤18👍12
📍Английская набережная. 1911/2023 год. 💡Интересный факт: в 1777 году набережную стали называть Английской линией, а в 1829 году официально — «Английской набережной». 🎞Санкт-Петербург в объективе времени🎞
❤20👍12😢3
📍Улица Дыбенко. 1998/2024 год. 💡Интересный факт: нынешнее название улица получила только в 1964-м году. До этого она была Проектируемым проездом № 4934. 🎞Санкт-Петербург в объективе времени🎞
👍10❤8
📍1-ая Красноармейская улица. 1987/2023 год. 💡 Интересный факт: история 1-й Красноармейской улицы в Петербурге началась ещё в 18-м веке, когда она была известна как 1-я рота. Затем она была 1-й Измайловской, просто Измайловской, пока в 1923 году не получила название в честь Красной Армии. 🎞Санкт-Петербург в объективе времени🎞
👍18❤8😍2
📍Мариинский дворец. 1991/2023 год. 💡Интересный факт: в XVIII веке на месте Мариинского дворца располагался дворец графа Ивана Чернышева и ещё несколько зданий. Новый дворец предназначался в качестве свадебного подарка для дочери императора Николая I — великой княжны Марии Николаевны. После того как она вышла замуж за герцога Лейхтенбергского, дворец стал официальной резиденцией этой фамилии. 🎞Санкт-Петербург в объ…
❤15👍11
📍Ораниенбаум. Большой дворец. 1975/2024 год. 💡Интересный факт: в XX веке Ораниенбаум был переименован в Ломоносов (историческое название сохранилось за дворцово-парковым комплексом), но апельсиновое дерево и в наши дни красуется на городском гербе. 🎞Санкт-Петербург в объективе времени🎞
❤19👍11👎1
Showing the 12 most recent of 25 posts we hold for @spb_in_time. 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.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Санкт-Петербург в объективе времени” (@spb_in_time), 6,376 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/spb_in_time.
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.