Обновлённая схема Петербургского метрополитена с отмеченными на ней линиями внутригородских и пригородных электричек (как с тактовым движением, так и без оного).
❤7😁1
Signed Alexey Fedorov

Channel
@wikiphotospace
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
50subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002012411405 |
|---|---|
| Type | Channel |
| Username | @wikiphotospace |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 13 October 2026 |
| On Telegram | t.me/wikiphotospace |
Local community — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 3 Oct 2026, 14:38 | 50 | +1 |
| 10 Sept 2026, 06:41 | 49 | +1 |
| 10 Aug 2026, 13:16 | 48 | no change |
| 8 Aug 2026, 00:14 | 48 | first reading |
11 posts held, back to 3 June 2025 — 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 11 posts for this entry, the most recent from 15 April 2026. An engagement rate over an empty window would be a number about nothing.
69 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 36.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 36.2% | |
| 👍 | 16 | 23.2% | |
| 🔥 | 15 | 21.7% | |
| 😢 | 6 | 8.70% | |
| 😁 | 4 | 5.80% | |
| 💔 | 2 | 2.90% | |
| 😭 | 1 | 1.45% |
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 10 of the 11 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 69 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 3 June 2025 to 15 April 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😁1
Signed Alexey Fedorov
Сгорел деревянный Дом горного начальника в Петрозаводске. Это мой снимок из 2017г. Немного страшновато представить, как будет выглядеть новодел здания после обещанного «восстановления»
😢6😭1
Signed Alexander Savin
26 декабря 2025 года в Петербурге открылись две новых станции метрополитена: «Путиловская» (с пересадкой на «Кировский завод») и «Юго-Западная». Которые стали первым участком новой линии — Красносельско-Калининской. Пока что она протяженностью целых 2,6 километров, но у неё всё ещё впереди!
❤6🔥2😁1
Signed Alexey Fedorov
Вдогонку летней схеме Петербургского метро, сделал также ещё и схему трамвайного движения Санкт-Петербурга. Выпуск которой условно приурочен к запуску новой пригородной линии в Славянку, и которая пришла на замену старой моей схеме. Последняя, конечно же, визуально сильно устарела за прошедшие с момента её выгрузки 10 лет, и необходимость её замены назрела.
❤3😁1
Signed Alexey Fedorov
Оказывается, сегодня — Всемирный день туризма, отмечающийся с 1979 года ежегодно 27 сентября. Чего я не знал ровно год назад, когда случайным образом "отметил" именно этот день, вылетемши из Франкфурта на Сейшелы, дабы на свои кровные обогатить Википедию очередной порцией иллюстраций. О том, что спустя год Википедия окончательно сойдёт с ума, как-то тоже не особо подозревал... хотя вполне можно было, учитывая умствен…
💔2❤1
Signed Alexander Savin
Пергола в Верхнем саду Петергофа
❤6
Signed Alexey Fedorov
"Твой человек не тот, кому "с тобой хорошо" — с тобой может быть хорошо сотне людей. Твоему — "без тебя плохо". Эрих Мария Ремарк Популярная Философия | Цитаты
👍4
Signed Alexander Savin
Станция Петербургского метрополитена «Волковская»
👍5🔥3❤1😁1
Signed Alexey Fedorov
Из рубрики «Никогда такого не было и вот опять»
Signed Alexander Savin
Майсен, Саксония Март 2025
🔥8❤1
Signed Alexander Savin
Намедни завершил работы по созданию новой схемы Петербургского метрополитена. Она является улучшенной (надеюсь) и дополненной (сомневаюсь) преемницей прежней схемы, с момента публикации которой в Википедии прошло уже 13 лет
👍7🔥2
Signed Alexey Fedorov
Showing the 11 most recent of 11 posts we hold for @wikiphotospace. 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.
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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“WikiPhoto.Space” (@wikiphotospace), 50 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/wikiphotospace.
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.