Telegram RegisterThe public register of Telegram
Telegram profile photo for Світло ОДЕСА | Вода, Газ

Channel

Світло ОДЕСА | Вода, Газ

@odesa_svet1

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

20,609subscribers

-1,686 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001638134543
TypeChannel
Username@odesa_svet1
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/odesa_svet1

Topic

National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@odesa_svet1/9228 · this entry6 Nov 2026, 14:55 UTC@odesa_svitlo_svet1/101116 Nov 2026, 14:55 UTC1.00under a minute
@odesa_svitlo_svet1/97897 Aug 2026, 18:26 UTC@odesa_svet1/8920 · this entry7 Aug 2026, 18:26 UTC0.99under a minute
@odesa_svitlo_svet1/978230 Jul 2026, 18:03 UTC@odesa_svet1/8913 · this entry30 Jul 2026, 18:03 UTC0.97under a minute
@odesa_svitlo_svet1/97918 Aug 2026, 07:07 UTC@odesa_svet1/8922 · this entry8 Aug 2026, 07:07 UTC0.97under a minute
@odesa_svitlo_svet1/100753 Nov 2026, 05:02 UTC@odesa_svet1/9195 · this entry3 Nov 2026, 08:10 UTC0.953.1 hours
@odesa_svitlo_svet1/101035 Nov 2026, 17:47 UTC@odesa_svet1/9220 · this entry5 Nov 2026, 17:47 UTC0.94under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@odesa_svitlo_svet115 (8/8 hand-verifiable sample passed)0.96under a minute@odesa_svitlo_svet1 (12–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 10 of the 12 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 103 comparable posts for this entry, running 22 July 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 14 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

20,60922,29521,4527 August 202614 November 2026
65 measurements spanning 99 days, net -1,686. 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 20,356–22,548 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 14:2020,609-11
11 Nov 2026, 15:5520,620-12
9 Nov 2026, 20:4620,632-15
8 Nov 2026, 14:5920,647-3
7 Nov 2026, 12:2220,650+3
6 Nov 2026, 10:5820,647-9
5 Nov 2026, 08:1520,656+12
4 Nov 2026, 07:1020,644+20
3 Nov 2026, 10:1720,624-27
2 Nov 2026, 11:4120,651-49
1 Nov 2026, 11:4620,700-41
31 Oct 2026, 10:4620,741-39
30 Oct 2026, 13:5620,780-124
29 Oct 2026, 13:2120,904-162
28 Oct 2026, 09:3121,066-10
27 Oct 2026, 06:4621,076-13
26 Oct 2026, 03:1521,089-18
25 Oct 2026, 02:0921,107-32
23 Oct 2026, 23:1921,139-10
22 Oct 2026, 21:1721,149first reading

Engagement

183 posts held, back to 22 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 97 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.5%
avg views ÷ 20,609 subscribers
Avg views / post
5,050
98 posts measured
Reaction rate
0.361%
reactions ÷ views · ER floor
Posts in window
98
of 183 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 96 of 98 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 14 November 2026
Posts held183 (22 July 2026 – 14 November 2026)
Views total495,325
Reactions total1,758
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 09:01 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

Video runtime
19m 08s
Average length
38s

Measured directly from 30 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

5,463 reactions across 175 posts, in 11 distinct kinds. The most used accounts for 42.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬2,32942.6%
❤1,05319.3%
🙏77914.3%
😢74213.6%
👍2173.97%
😭1412.58%
🔥651.19%
👎520.952%
😱410.751%
🤯340.622%
🤔100.183%

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 179 of the 183 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 5,463 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 183 most recent posts we hold, published 22 July 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 7 of 98 posts held from the last 30 days (7.14%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 08:12 UTC925 views3 reactionsread 14 November 2026

💡 ДТЕК: Зафіксовано відключення електроенергії в частині Подільського району. Фахівці вже працюють над тим, щоб якнайшвидше відновити електропостачання в усіх будинках. Світло ОДЕСА | Вода, Газ

👍3

13 Nov 2026, 19:55 UTC≈3,080 views13 reactionsread 14 November 2026

Графік відключень на завтра 1.1 — 06:00–09:00, 15:30–19:30 1.2 — 06:00–09:00, 15:30–19:30 2.1 — 06:00–09:00, 17:30–19:30 2.2 — 15:30–19:30 3.1 — 19:00–23:00 3.2 — 08:30–12:30, 19:00–23:00 4.1 — 08:30–12:30, 19:00–22:30 4.2 — 08:30–12:30, 19:00–23:00 5.1 — 12:00–16:00, 22:30–24:00 5.2 — 12:00–16:00 6.1 — 14:00–18:00, 22:30–24:00 6.2 — 12:00–16:00, 22:30–24:00 Світло ОДЕСА | Вода, Газ

❤6🙏5👍1😢1

13 Nov 2026, 17:10 UTC≈3,610 views21 reactionsread 14 November 2026
Photo

Ще оновлення, на сьогодні відключень більше не планується Світло ОДЕСА | Вода, Газ

👍18❤3

13 Nov 2026, 15:59 UTC≈3,650 views14 reactionsread 14 November 2026
Photo

Ще оновлення Світло ОДЕСА | Вода, Газ

👎8👍3🤔2❤1

13 Nov 2026, 15:51 UTC≈3,560 views6 reactionsread 14 November 2026
Photo

Знову оновлення в графіку відключення електрики на сьогодні Світло ОДЕСА | Вода, Газ

👍3👎2🔥1

13 Nov 2026, 14:30 UTC≈3,670 views6 reactionsread 14 November 2026
Photo

Зміни у графіку Світло ОДЕСА | Вода, Газ

❤5👎1

13 Nov 2026, 13:00 UTC≈3,810 views12 reactionsread 14 November 2026
Photo

Оновлення графіку Світло ОДЕСА | Вода, Газ

👍7🤬4❤1

13 Nov 2026, 10:22 UTC≈4,190 views22 reactionsread 14 November 2026
Photo

❗️Якщо через руйнування інфраструктури послуги фактично не надаватимуться, розглядається можливість припинення нарахування комунальних платежів, – прем’єр Корнецький Світло ОДЕСА | Вода, Газ

❤18👍4

13 Nov 2026, 08:03 UTC≈4,470 views14 reactionsread 14 November 2026
Photo

Оновлений графік по світлу на ранок. До 15:30 відключення не заплановані Світло ОДЕСА | Вода, Газ

🙏10❤4

12 Nov 2026, 19:42 UTC≈4,750 views10 reactionsread 14 November 2026

Оновили графіки відключень на завтра в Одесі та області, – ДТЕК. ▪️ 1.1: 08:00–12:00, 18:30–22:30; ▪️ 1.2: 08:00–12:00, 18:30–22:30; ▪️ 2.1: 18:30–22:30; ▪️ 2.2: 08:00–12:00, 18:30–22:30; ▪️ 3.1: 11:30–15:30; ▪️ 3.2: 11:30–15:30, 22:00–24:00; ▪️ 4.1: 12:00–15:30, 22:00–24:00; ▪️ 4.2: 11:30–15:30, 22:00–24:00; ▪️ 5.1: 06:00–08:30, 15:00–19:00; ▪️ 5.2: 06:00–08:30, 15:00–19:00; ▪️ 6.1: 15:00–19:00; ▪️ 6.2: 06:00–08:30…

🙏6❤4

12 Nov 2026, 19:12 UTC≈4,560 views10 reactionsread 14 November 2026
Photo

💡 Графік на завтра Світло ОДЕСА | Вода, Газ

🙏7❤3

12 Nov 2026, 19:07 UTC≈4,550 views2 reactionsread 14 November 2026
Photo

❌ Оновили графік відключення електрики на сьогодні Світло ОДЕСА | Вода, Газ

👍2

Showing the 12 most recent of 183 posts we hold for @odesa_svet1. 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 recorded as deleted after publishing

We recorded 7 posts on @odesa_svet1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
31 August 2026
Most recent seen missing
12 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
5

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Хуевая Одесса
@xydessa · 944,347
#1
Одесса как она есть
@odessapublic · 306,169
#2
Думская. Одесса. Война в Украине
@OdessaDumskayaNet · 102,528
#3
Труха⚡️Одеса | Новини
@odesatruexa · 263,504
#4
Одесса как она есть | Паблик Одесса
@odessa_kak_ona_est · 38,776
#5
Сповіщення | Новини. Одеса
@odesa_daily · 53,002
#6
Одеський MAXXL
@maxxlod_ua · 9,058
#7
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 242,758
#8
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 990,973
#9
Новости Одесса | Одеса
@our_odessa · 437,561
#10
Типичная Одесса
@odessa_typical · 251,626
#11
Повітряна тривога️ | Бережіть себе!
@raketna_neb · 215,789
#12
Лачен пише
@lachentyt · 1,578,193
#13
Труха⚡️Україна
@truexanewsua · 3,165,061
#14
Курс Одесса
@kurs_odessa · 122,279
#15
Південь ™
@mediapivden · 193,193
#16
🚨КАЛІБР🚨
@temporis_odesa · 93,144
#17
Одеса. Офіційно
@odesacityofficial · 81,540
#18
INSIDER UA | Україна | Новини
@insiderukr · 2,146,024
#19
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,428
#20
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,408
#21
ДТЕК - офіційний канал
@dtek_ua · 447,558
#22
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#23
Одеса | Графіки | Світло
@odesa_svitlo_svet1 · 36,206
#24
⚔️БРАТЧУК
@Bratchuk_Sergey · 154,718
#25
Vitalii KIM | Official
@VitaliiKimOfficial · 251,885
#26
💡Нет света Одесса | Тутешні
@svitlo_off · 12,227
#27
Сила Громади
@Sila_GO · 315,622
#28
Реальна Війна | Україна | Новини
@voynareal · 1,543,423
#29
Україна 24/7 - новини
@ukraina_novosti · 1,403,375 (as read 22 September 2026)
#30
Суспільне Одеса
@suspilneodesa · 46,713
#31
Повестки Одесса
@povestky · 54,666
#32
“Kaiteki” Cosplay Anime party
@kaiteki_party · 1,141
#33
Черный список Одесса
@black_list_odessa · 23,153
#34
𝐎𝐃 𝐏𝐎𝐒𝐊𝐎𝐓 🍁🍃
@od_poskot · 27,341
#35
І ШО КУДА ОДЕСА
@i_sho_kuda_odesa · 8,614
#36
<Crystals> Одеська косплей паті 🕸
@Crystals_Odessa · 557
#37
Тривога України | Радар
@kiev_nebo · 540,698
#38
Chornomorsk | Черноморск
@checity · 61,724
#39
Gura Anton
@guraanton · 273,268
#40
Не Молчи, Одесса ⚓️
@NMOdessa · 8,372
#41
Новости Николаева🇺🇦 | Миколаїв
@novostiniko · 253,833
#42
🇺🇦Олег Кіпер/Одеська ОДА (ОВА)
@odeskaODA · 38,009
#43
Крым | Причерноморье
@krymmax · 10,139
#44
Ukraine NOW
@UkraineNow · 404,377
#45
MoGucci Ейчаруччі
@AdvicefromHR · 5,592
#46
Інформація, новини, оголошення ОДАБА
@info_ODABA · 2,408 (as read 22 September 2026)
#47
ПОСКОТ ОДЕССА НОВОСТИ
@poskot_odessa_TG · 11,877
#48
Nyako-kon|News📢
@NyakoKon · 909 (as read 22 September 2026)
#49
Лена Адамова. Мир кайфолова 🇺🇦♥️
@ElenaAdamova · 6,889
#50
Ani_land
@anillland · 1,028
#51
monitor
@war_monitor · 958,023
#52
Скринька Пандори
@pandoras_box_ua · 157,815
#53
Чому тривога | Радар
@raketa_trevoga · 472,563
#54
Тотальна Зрада
@totallzrada · 266,456
#55
Мечников_інфо
@Mechnikov_info · 4,606
#56
Natsu Nami Party
@NatsuNamiparty · 797
#57
Одеса КИТ Group
@obmenka_odessa · 19,016
#58
Підслухано в Одесі
@overheardinodesa · 746
#59
Новинач
@novinach · 142,284
#60
Где повестки Одесса?
@agendaOdessa · 129,916
#61
Hebi Hebi Agency
@hebihebi_agency · 12,094
#62
Отключения света - Черноморск
@chornomorsk_svitlo · 38,484
#63
Повестки Одесса
@pov_od · 19,800
#64
More Music Club
@mrmscl · 2,098
#65
Зелений театр
@greentheatreod · 2,889
#66
7:40 Одеса
@sem_sorok · 14,998
#67
ДУІТЗ / Державний університет інтелектуальних технологій і зв'язку
@suitt_official · 776 (as read 22 September 2026)
#68

Read from Telegram’s recommendation API, most recently 22 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Одесса как она есть
@odessapublic · 306,169
Telegram ranks this channel #20 of 77 here — alongside 76 others — read 10 August 2026
Сповіщення | Новини. Одеса
@odesa_daily · 53,002
Telegram ranks this channel #28 of 79 here — alongside 78 others — read 27 August 2026
Одесса как она есть | Паблик Одесса
@odessa_kak_ona_est · 38,776
Telegram ranks this channel #39 of 74 here — alongside 73 others — read 29 August 2026
Одеса | Графіки | Світло
@odesa_svitlo_svet1 · 36,206
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 3 September 2026
Оренда квартир в Одесі | ДОВГОСТРОКОВО - ПОДОБОВО
@arendavodesse_odessa · 21,981
Telegram ranks this channel #49 of 55 here — alongside 54 others — read 25 September 2026
ОДЕССА ИНФО LIVE - радар Одеса
@odessa_inform · 375,614
Telegram ranks this channel #55 of 75 here — alongside 74 others — read 10 August 2026
Повестки Одесса
@pov_od · 19,800
Telegram ranks this channel #57 of 59 here — alongside 58 others — read 2 October 2026
Сила Громади
@Sila_GO · 315,622
Telegram ranks this channel #60 of 65 here — alongside 64 others — read 11 August 2026
Повітряна тривога️ | Бережіть себе!
@raketna_neb · 215,789
Telegram ranks this channel #65 of 76 here — alongside 75 others — read 11 August 2026
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 990,973
Telegram ranks this channel #65 of 79 here — alongside 78 others — read 8 August 2026
Где повестки Одесса?
@agendaOdessa · 129,916
Telegram ranks this channel #70 of 73 here — alongside 72 others — read 16 August 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Світло ОДЕСА | Вода, Газ” (@odesa_svet1), 20,609 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/odesa_svet1.

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.