Telegram RegisterThe public register of Telegram
Telegram profile photo for Львівводоканал

Bot

Львівводоканал

@vodokanal_lviv_bot

On this record: Topic · Growth · Engagement · Cite this entry

44,561monthly users

+166 since we began measuring on 8 August 2026

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

Register entry

Telegram ID994370544
TypeBot
Username@vodokanal_lviv_bot
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/vodokanal_lviv_bot

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

43,86246,12244,9928 August 2026 — 44,395 monthly users9 August 2026 — 44,492 monthly users11 August 2026 — 44,716 monthly users11 August 2026 — 44,790 monthly users12 August 2026 — 44,790 monthly users14 August 2026 — 45,278 monthly users17 August 2026 — 44,405 monthly users20 August 2026 — 44,406 monthly users24 August 2026 — 44,067 monthly users25 August 2026 — 44,073 monthly users27 August 2026 — 44,011 monthly users29 August 2026 — 43,964 monthly users30 August 2026 — 45,093 monthly users1 September 2026 — 46,122 monthly users4 September 2026 — 44,468 monthly users8 September 2026 — 44,441 monthly users11 September 2026 — 43,862 monthly users13 September 2026 — 43,988 monthly users14 September 2026 — 44,204 monthly users16 September 2026 — 44,395 monthly users18 September 2026 — 44,561 monthly users44,5618 August 202618 September 2026
21 measurements spanning 42 days, net +166. 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 43,523–46,461 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 21
Measured (UTC)Monthly usersChange
18 Sept 2026, 12:2044,561+166
16 Sept 2026, 08:3644,395+191
14 Sept 2026, 16:3644,204+216
13 Sept 2026, 03:2043,988+126
11 Sept 2026, 04:3743,862-579
8 Sept 2026, 04:1844,441-27
4 Sept 2026, 22:0044,468-1,654
1 Sept 2026, 07:1446,122+1,029
30 Aug 2026, 02:5645,093+1,129
29 Aug 2026, 00:1443,964-47
27 Aug 2026, 22:4944,011-62
25 Aug 2026, 21:0444,073+6
24 Aug 2026, 22:4744,067-339
20 Aug 2026, 16:0544,406+1
17 Aug 2026, 14:2444,405-873
14 Aug 2026, 13:5545,278+488
12 Aug 2026, 19:0344,790no change
11 Aug 2026, 23:0344,790+74
11 Aug 2026, 02:0344,716+224
9 Aug 2026, 00:5144,492first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Львівводоканал” (@vodokanal_lviv_bot), 44,561 monthly users as measured 18 September 2026. Telegram Register, tgregister.com/channel/vodokanal_lviv_bot.

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.