Опять цены на топливо поменялись🤦♂️ @dpsvolgograd_public #бензин #топливо #цены #авто #Волгоград дата 04.07.26 цены на топливо: 92 - июнь 2026 год 63,15 🇷🇺 июль 2026 год 63,35 95 - июнь 2026 год 70,45 🇷🇺 июль 2026 год 70,65 100 - июнь 2026 год 92,40 🇷🇺 июль 2026 год 94,40 ДТ - июнь 2026 год 76,25 🇷🇺 июль 2026 год 76,45 цены фиксируются на заправочной станции газпром г. Волгоград @dpsvolgograd_public

Channel
Волгоград🇷🇺тут
@dpsvolgograd_public
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
246subscribers
-8 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 | -1001803052535 |
|---|---|
| Type | Channel |
| Username | @dpsvolgograd_public |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/dpsvolgograd_public |
Topic
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 15:00 | 246 | -1 |
| 30 Sept 2026, 04:38 | 247 | -1 |
| 9 Sept 2026, 01:16 | 248 | -1 |
| 15 Aug 2026, 07:39 | 249 | -3 |
| 8 Aug 2026, 09:20 | 252 | no change |
| 8 Aug 2026, 02:53 | 252 | -2 |
| 7 Aug 2026, 14:09 | 254 | first reading |
Engagement
18 posts held, back to 19 August 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 18 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 4m 01s
- Average length
- 17s
Measured directly from 14 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
73 reactions across 12 posts, in 15 distinct kinds. The most used accounts for 13.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 10 | 13.7% | |
| 👍 | 9 | 12.3% | |
| 😁 | 9 | 12.3% | |
| 🎉 | 8 | 11.0% | |
| 👎 | 8 | 11.0% | |
| 😱 | 8 | 11.0% | |
| 🔥 | 7 | 9.59% | |
| ❤ | 3 | 4.11% | |
| 😢 | 3 | 4.11% | |
| 👏 | 2 | 2.74% | |
| 🫡 | 2 | 2.74% | |
| 🐳 | 1 | 1.37% | |
| 😡 | 1 | 1.37% | |
| 🙈 | 1 | 1.37% | |
| 🤬 | 1 | 1.37% |
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 12 of the 18 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 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 19 August 2025 to 5 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.
Recent posts
Наш величественный Собор Александра Невского. В 2026 году центр Волгограда продолжает радовать потрясающими видами — идеальное место, чтобы выдохнуть, полюбоваться архитектурой и насладиться теплым вечером с семьей. @dpsvolgograd_public 👇 #волгоград #СоборАлександраНевского #2026 #1июня #деньзащитыдетей первыйденьлета
👏2👎1
🚦 Главные дорожные изменения в центре Волгограда с 15 мая: dpsvolgograd_public dpsvolgograd_chat Онлайн чат в MAX 🫷🏻 1. Новые участки с односторонним движением: 🚧 Городская администрация ввела эти правила, чтобы увеличить пропускную способность улиц. Теперь потоки распределяются так: • Улица Пархоменко: движение идет от ул. Кубанской в сторону ул. Невской. 🚦 • Улица Новороссийская: движение организовано в обратном н…
🔥2
Обновлённые БЕЛЫЕ СПИСКИ для РФ @dpsvolgograd_public Взято отсюда
🌤️ Прогноз на 2 дня для жителей города Волгоград: 📅 09.04: ☀️ Солнечно, +3..+12°C, осадки 0мм. Отлично для велопрогулок по набережной! 📅 10.04: ☁️ Облачно, +5..+12°C, без осадков. #погода #Волгоград @dpsvolgograd_public @dpsvolgograd_chat
С 1 апреля, Волгоград! 🌧️ dpsvolgograd_public Природа решила пошутить с размахом. Город официально поплыл, на дорогах намертво встали 10 баллов. Кто уже успел открыть весенний купальный сезон по пути по делам? Делитесь, как добираетесь, и главное — берегите нервы! 🚣♂️👇
🔥2
Новый 2026 год встречает нас новыми ценами на топливо 🥳 всех с наступившим новым годом и праздниками 🎄 @dpsvolgograd_public Опять БЕНЗИН подорожал г. Волгоград 04.01.2026 🤷♂ #бензин #бензинволгоград #волгоград #2026год #2026 дата 04.01.26 цены на топливо: 92 - 2025 год 60,00 / 🔥 2026 год 60,40 95 - 2025 год 67,00 / 🔥 2026 год 67,40 100 - 2026 год 86,80 /🔥 ДТ - 2025 год 72,30 / 🔥 2026 год 73,00 цены фиксируются …
❤2
С новым 2026 годом 🎄
👍9🎉8🔥2🫡2
Кто прав? Кто виноват? 🤷 @dpsvolgograg_public
🤣9
Дзержинский район, ул. Космонавтов перекрыли @dpsvolgograd_public
Вы уж извините, очень хочется оставить цены на топливо в памяти 2025 года. А у Вас как с ценами на бензин? @dpsvolgograd_public @dpsvolgograd_chat Опять БЕНЗИН подорожал г. Волгоград 11.12.2025 🤷♂ #бензин #бензинволгоград #бензиндорожает #волгоград сегодня 11.12.25 года, цены на топливо: 92 - 60,00 / 🔥 95 - 67,00 /🔥 98 - НЕТ /🔥 ДТ - 72,30 /🔥 цены фиксируются на заправочной станции газпром г. Волгоград @dpsvol…
👎3😱3🔥1😡1
Опять БЕНЗИН подорожал г. Волгоград 01.10.25 @dpsvolgograd_public Примерно каждые две недели, цена меняется к сожалению не в меньшую сторону 😟 как обстановка вообще? 🤷♂ 01.10.25 года, цены на топливо: 92 - 59,40 / 95 - 66,40 / 98 - 85,40 / ДТ - НЕТ / цены фиксируются на заправочной станции газпром Волгоград @dpsvolgograd_public
😢3
Showing the 12 most recent of 18 posts we hold for @dpsvolgograd_public. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@dpsvolgograd_public 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Волгоград🇷🇺тут” (@dpsvolgograd_public), 246 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/dpsvolgograd_public.
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.