18 Sept 2026, 04:36 UTC38 viewsread 8 October 2026
Forwarded from @SPgovoritPhoto
Обновленное расписание 36 и 37 в одной картинке Присоединяйтесь: Северный парк говорит | VK | MAX Написать нам
Channel
Попутчики СП (Расписание автобусов СП)
@poputchiki_sp
On this record: Growth · Engagement · Posts · Citations · Cite this entry
105subscribers
+2 since we began measuring on 8 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002466861902 |
|---|---|
| Type | Channel |
| Username | @poputchiki_sp |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/poputchiki_sp |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Oct 2026, 05:57 | 105 | +1 |
| 11 Oct 2026, 19:37 | 104 | +1 |
| 8 Oct 2026, 03:22 | 103 | no change |
| 8 Oct 2026, 02:47 | 103 | first reading |
Engagement
11 posts held, back to 4 July 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 18 September 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
17 Sept 2026, 04:17 UTC54 viewsread 8 October 2026
Forwarded from @tomskadm70Photo
❗️С пятницы меняется расписание движения маршрутов №№36, 37 По просьбе областного депутата, директора ТЭМЗа Ивана Пушкарева, которую он озвучил в ходе визита мэра Томска Дмитрия Махини на предприятие, скорректировано расписание движения маршрутов №№36, 37. ℹ️Изменения коснулись движения маршрутных автобусов в будние дни, когда жители добираются на работу, учебу и в социальные учреждения. Новое расписание можно посм…
14 Aug 2026, 07:19 UTC145 viewsread 8 October 2026
Photo
Расписание действует с 15 августа 2026 г.
20 Jan 2026, 07:51 UTC398 viewsread 8 October 2026
Forwarded from @SPgovoritPhoto
Актуальное расписание 112С. Цветная картинка будет позже. Присоединяйтесь: 🥹 Северный парк говорит 😅 Наш Северный парк ✏️ Написать нам 😇 MAX: Чат | Попутчики | Купи-продай
22 Dec 2025, 05:05 UTC421 viewsread 8 October 2026
Forwarded from @SPgovorit
#нампишут Соседи добрый день сообщаю сразу 2 автобуса 112 маршрута сейчас прямо сейчас стоят в авариях на проспекте Ленина, оба автобуса двигались из северного парка в город 1 на перекрёстке Ленина Савиных. Второй на перекрёстке Ленина Кирова. У кого есть возможность, сообщите в общий чат-северного парка, эта ситуация сильно отразится на выезде из посёлка. Присоединяйтесь: 🥹 Северный парк говорит 😅 Наш Северный пар…
2 Dec 2025, 06:02 UTC426 viewsread 8 October 2026
Попутчики СП теперь есть в MAX 😇 https://max.ru/join/GjHEWtEtPFsYoi2Hn9Aikmq-dnIkRyaP0LfI7tFz5ws
8 Oct 2025, 05:12 UTC558 viewsread 8 October 2026
Photo
Новое расписание 36 маршрута
3 Oct 2025, 10:34 UTC527 viewsread 8 October 2026
Forwarded from @SPgovoritPhoto
Немного обновили картинку. При использовании материалов поста, ссылка на источник обязательна. Присоединяйтесь: 💬 Северный парк говорит 💬 Наш Северный парк ✏️ Написать нам
16 Aug 2025, 04:34 UTC599 viewsread 8 October 2026
Photo
Телефон диспетчера 112С, Б, Д: +73822990099 Источник упрощенного расписания Северный парк говорит Полное расписание на сайте: https://пассажир.online/documents
15 Aug 2025, 02:28 UTC469 viewsread 8 October 2026
Photo
Новый перевозчик на на 112 Б, Д, С и 134 ООО "ЕТВ". График прежний. Телефон диспетчера +73822990099
4 Jul 2025, 05:56 UTC591 viewsread 8 October 2026
Photo
Расписание 36/37 маршрута
Showing the 11 most recent of 11 posts we hold for @poputchiki_sp. 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.
Forward network
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.
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 19 October 2026 — this entry's latest reading, not the date you are reading this.
“Попутчики СП (Расписание автобусов СП)” (@poputchiki_sp), 105 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/poputchiki_sp.
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.