Telegram RegisterThe public register of Telegram
Telegram profile photo for МУПП "Саратовводоканал"

Channel

МУПП "Саратовводоканал"

@vodokanal_64

On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

19,050subscribers

+3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002264684090
TypeChannel
Username@vodokanal_64
DescriptionОфициальный канал МУПП "Саратовводоканал" 📞 Центр по работе с абонентами: +7 (8452) 32-00-00 +7 (8452) 30-40-00 VK: https://vk.ru/vodokanal_64 Email: [email protected]
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/vodokanal_64

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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

19,03819,05219,0456 August 2026 — 19,047 subscribers7 August 2026 — 19,041 subscribers8 August 2026 — 19,040 subscribers9 August 2026 — 19,045 subscribers9 August 2026 — 19,038 subscribers11 August 2026 — 19,039 subscribers11 August 2026 — 19,048 subscribers13 August 2026 — 19,051 subscribers14 August 2026 — 19,052 subscribers15 August 2026 — 19,050 subscribers19,0506 August 202615 August 2026
10 measurements spanning 9 days, net +3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19,036–19,054 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:5519,050-2
14 Aug 2026, 05:2719,052+1
13 Aug 2026, 01:0319,051+3
11 Aug 2026, 22:2319,048+9
11 Aug 2026, 00:0319,039+1
9 Aug 2026, 21:5219,038-7
9 Aug 2026, 00:5519,045+5
8 Aug 2026, 03:5519,040-1
7 Aug 2026, 00:5519,041-6
6 Aug 2026, 09:5319,047first reading

Engagement

140 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
11.7%
avg views ÷ 19,050 subscribers
Avg views / post
2,240
140 posts measured
Reaction rate
0.161%
reactions ÷ views · ER floor
Posts in window
140
of 140 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 50 of 140 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held140 (3 August 202616 August 2026)
Views total312,999
Reactions total188
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 20:45 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.

What this channel posts

Photos
3,810
Videos
86
Links
1,060

Lifetime counters from Telegram’s own channel header, read 16 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
29s
Average length
29s

Measured directly from 1 video 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

188 reactions across 37 posts, in 12 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5227.7%
👍4322.9%
😢179.04%
🔥168.51%
👏157.98%
😱115.85%
👌105.32%
🆒84.26%
🤔73.72%
🙏52.66%
💯21.06%
🕊21.06%

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 50 of the 140 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 188reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 140 most recent posts we hold, published 3 August 2026 to 16 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

16 Aug 2026, 19:17 UTC691 viewsread 16 August 2026
Photo

Когда 16 августа до 08:00 17 августа Где 1-й пр. Энергетиков,14/16 Зона отключения 🔵1-й пр. Энергетиков. МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

16 Aug 2026, 18:19 UTC≈1,300 views1 reactionsread 16 August 2026
Photo

Когда 16 августа до 08:00 17 августа Где Ул. Центральная,6 Зона отключения 🔵пр.Строителей 2,2а,4,4а,6,6а,8,8а; 🔵Шехурдина 34,36,36а,38; 🔵Куприянова; 🔵Центральная; 🔵Приовражная. МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

1

16 Aug 2026, 16:32 UTC≈1,210 viewsread 16 August 2026

Водоснабжение восстановлено 📍ул. Карьерная, 6/12 МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

16 Aug 2026, 14:43 UTC≈1,080 views7 reactionsread 16 August 2026
Forwarded from @busargin_rVideo

МАСШТАБНАЯ МОДЕРНИЗАЦИЯ СЕТЕЙ ВОДОКАНАЛА В САРАТОВЕ ⬇️⬇️⬇️ Реализация региональной программы: Замена коммуникаций завершена на улицах Уфимцева, Благодарова, Буровой и Саперной. Подрядные организации продолжают благоустройство участков после вскрышных работ. Качественное восстановление территории - обязательное условие реализации региональной программы. Работы продолжаются: 🔘 На улице Кутякова (от Пугачева до Астр

3👍2💯1🔥1

16 Aug 2026, 14:24 UTC≈1,070 viewsread 16 August 2026

Водоснабжение восстановлено 📍ул. Чехова, 8/2 МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

16 Aug 2026, 13:25 UTC≈2,420 viewsread 16 August 2026
Photo

Когда 16 августа до 24:00 Где ул. Карьерная,6/12 Зона отключения 🔵ул. Огородная, 29а, 31а, 31б, 31, 31/33, 33в; 🔵Карьерная, 3, 6/12, 2г, 2б, 2д, 2в, 5; 🔵Лопатина гора, 14, корп.2 и корп.1, 12а, 12, 10а, 🔵частный сектор по 2-му Карьерному пр МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

16 Aug 2026, 08:38 UTC≈2,150 viewsread 16 August 2026
Photo

📍ул. Днепропетровская,16 Машина находится на месте, пока есть желающие пополнить запасы воды.

16 Aug 2026, 08:21 UTC≈2,380 viewsread 16 August 2026
Photo

Когда 16 августа до 20:00 Где ул. Чехова, 8/2 Зона отключения 🔵ул. Чехова от Антонова до Мамонтовой. МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

16 Aug 2026, 05:34 UTC≈1,490 viewsread 16 August 2026
Photo

📍2я Садовая, 103/107 Машина находится на месте, пока есть желающие пополнить запасы воды.

15 Aug 2026, 14:11 UTC≈1,530 viewsread 16 August 2026

Водоснабжение восстановлено 📍ул. Бакинская, 19 МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

15 Aug 2026, 14:06 UTC≈1,460 viewsread 16 August 2026

Водоснабжение восстановлено 📍ул. Навашина,40 МУПП «Саратовводоканал» напоминает абонентам, что в течение 24 часов необходимо использовать питьевую воду в кипяченом виде.

15 Aug 2026, 13:37 UTC≈2,400 viewsread 16 August 2026
Photo

📍Уфимцева, 12а 📍Огородная, 29 Машины находятся на месте, пока есть желающие пополнить запасы воды.

Showing the 12 most recent of 140 posts we hold for @vodokanal_64. 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.

Posts edited after publishing

@vodokanal_64 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Citation-graph rank

Citation-graph rank — 58,746 of 1,481,243entries 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

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

Named by 4 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.

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.

“МУПП "Саратовводоканал"” (@vodokanal_64), 19,050 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/vodokanal_64.

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.