Telegram RegisterThe public register of Telegram
Telegram profile photo for Одеса Головне

Channel

Одеса Головне

@odesa_golovne

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

124,602subscribers

+13,148 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001671916806
TypeChannel
Username@odesa_golovne
DescriptionПершими розповідаємо, що відбувається в Одесі та області ⚡️ Реклама: @golovne_ads Маєш цікавий матеріал? Пиши: https://t.me/OdesaGolovne_Bot
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 live7 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/odesa_golovne

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

Growth

111,441124,602118,021.57 August 2026 — 111,454 subscribers8 August 2026 — 111,441 subscribers8 August 2026 — 111,453 subscribers9 August 2026 — 115,260 subscribers11 August 2026 — 117,248 subscribers12 August 2026 — 118,629 subscribers13 August 2026 — 118,722 subscribers14 August 2026 — 118,490 subscribers16 August 2026 — 118,229 subscribers17 August 2026 — 119,519 subscribers18 August 2026 — 119,552 subscribers19 August 2026 — 119,385 subscribers20 August 2026 — 119,091 subscribers21 August 2026 — 118,846 subscribers23 August 2026 — 120,279 subscribers24 August 2026 — 120,935 subscribers25 August 2026 — 120,704 subscribers26 August 2026 — 120,564 subscribers28 August 2026 — 121,430 subscribers28 August 2026 — 121,099 subscribers30 August 2026 — 120,840 subscribers30 August 2026 — 120,518 subscribers31 August 2026 — 120,421 subscribers1 September 2026 — 120,385 subscribers3 September 2026 — 120,713 subscribers4 September 2026 — 120,602 subscribers7 September 2026 — 120,319 subscribers10 September 2026 — 119,867 subscribers12 September 2026 — 120,619 subscribers14 September 2026 — 120,607 subscribers16 September 2026 — 120,310 subscribers18 September 2026 — 119,986 subscribers1 October 2026 — 118,345 subscribers6 October 2026 — 117,798 subscribers10 October 2026 — 120,224 subscribers13 October 2026 — 119,738 subscribers15 October 2026 — 119,576 subscribers15 October 2026 — 119,675 subscribers16 October 2026 — 119,551 subscribers18 October 2026 — 120,992 subscribers18 October 2026 — 121,349 subscribers19 October 2026 — 121,329 subscribers20 October 2026 — 121,159 subscribers22 October 2026 — 120,968 subscribers23 October 2026 — 120,857 subscribers24 October 2026 — 120,720 subscribers25 October 2026 — 120,593 subscribers26 October 2026 — 120,468 subscribers27 October 2026 — 120,355 subscribers28 October 2026 — 120,236 subscribers29 October 2026 — 120,123 subscribers30 October 2026 — 120,033 subscribers31 October 2026 — 119,940 subscribers1 November 2026 — 119,845 subscribers2 November 2026 — 119,704 subscribers3 November 2026 — 119,615 subscribers4 November 2026 — 123,622 subscribers5 November 2026 — 124,349 subscribers6 November 2026 — 124,270 subscribers7 November 2026 — 124,602 subscribers7 August 20267 November 2026
60 measurements spanning 92 days, net +13,148. 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 109,467–126,576 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
7 Nov 2026, 15:19124,602+332
6 Nov 2026, 12:57124,270-79
5 Nov 2026, 16:08124,349+727
4 Nov 2026, 14:29123,622+4,007
3 Nov 2026, 10:56119,615-89
2 Nov 2026, 13:20119,704-141
1 Nov 2026, 09:46119,845-95
31 Oct 2026, 08:36119,940-93
30 Oct 2026, 09:55120,033-90
29 Oct 2026, 08:11120,123-113
28 Oct 2026, 09:06120,236-119
27 Oct 2026, 07:59120,355-113
26 Oct 2026, 06:09120,468-125
25 Oct 2026, 04:55120,593-127
24 Oct 2026, 03:28120,720-137
23 Oct 2026, 01:21120,857-111
22 Oct 2026, 02:01120,968-191
20 Oct 2026, 18:26121,159-170
19 Oct 2026, 18:47121,329-20
18 Oct 2026, 21:16121,349first reading

Engagement

3,089 posts held, back to 7 August 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 194 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14.0%
avg views ÷ 124,602 subscribers
Avg views / post
17,400
863 posts measured
Reaction rate
1.20%
reactions ÷ views · ER floor
Posts in window
863
of 3,089 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 862 of 863 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 7 November 2026
Posts held3,089 (7 August 2026 – 7 November 2026)
Views total15,053,804
Reactions total181,270
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 23:03 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
≈14,900
Videos
≈6,390
Links
≈25,700

Lifetime counters from Telegram’s own channel header, read 7 November 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
1h 20m
Average length
36s

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

205,395 reactions across 998 posts, in 36 distinct kinds. The most used accounts for 44.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏91,74344.7%
🤬45,77822.3%
❤22,53611.0%
👍9,3374.55%
😢8,1743.98%
😱5,4402.65%
🤣3,8241.86%
😡3,3041.61%
👎2,4681.20%
🔥1,9920.97%
😭1,7400.847%
😴1,7090.832%
🤯1,5290.744%
😁1,2600.613%
🤔1,0110.492%
👏5270.257%
😨4850.236%
🕊3150.153%
❤‍🔥3030.148%
🙉2580.126%
16 further kinds1,6620.809%

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 999 of the 1,000 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 205,395 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 5 October 2026 to 7 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.

Telegram Stars

Stars received
23
across the posts below
Posts paid on
18
of 1,000 we hold a reading for · 2%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @odesa_golovne. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 5 October 2026 to 7 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 101 of 863 posts held from the last 30 days (11.7%) 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).

7 Nov 2026, 20:42 UTC≈7,560 views161 reactionsread 7 November 2026

🫡 Одеса — відбій жовтої тривоги!

🙏130👍23❤5🤣3

7 Nov 2026, 20:41 UTC≈8,960 views197 reactionsread 7 November 2026

❗️Впав

🙏138🤬21👍12❤7👎6😡5🤣4😱3

7 Nov 2026, 20:40 UTC≈9,380 views143 reactionsread 7 November 2026

❗️Усатове до вас далі

🙏109🤬29❤2🤣2😡1

7 Nov 2026, 20:38 UTC≈9,990 views181 reactionsread 7 November 2026

❗️ Поскот увага до вас летить

🙏121🤬49😱5👎4🤣1😡1

7 Nov 2026, 20:36 UTC≈10,900 views207 reactionsread 7 November 2026

❗️Герань на Чорноморськ

🙏149🤬48❤6😱2🤣1😡1

7 Nov 2026, 20:34 UTC≈11,100 views129 reactionsread 7 November 2026

🟡🚨 Одеса — жовта тривога (дронова небезпека)!

🙏97🤬26❤4🤣1😡1

7 Nov 2026, 19:42 UTC≈16,900 views274 reactionsread 7 November 2026
Photo

❗️ В Одесі після атаки дрона виявили додаткові руйнування: пошкоджені житлові будинки та господарські споруди в адмінбудівлі вибухова хвиля вибила вікна й двері 🔴 Одеса Головне Надіслати новину | Наш чат

🤬158😢68🙏25❤21🤣1😡1

7 Nov 2026, 19:32 UTC≈17,200 views132 reactionsread 7 November 2026

💔 Якби маминої любові вистачало на лікування, цього збору не було б. Але їй доводиться відкривати перед незнайомими людьми найстрашніше - свій страх втратити сина. Знову й знову. Бо соромно просити, боляче повторювати, але зупинитися - як? За цими постами мама, якій потрібен її хлопчик. Сьогодні. На наступний день народження. Дорослим. Допоможімо їй боротися за це майбутнє. Будь-якою посильною сумою. 🙏 Рахунок фон…

❤66🙏59🤬4🗿2🤣1

7 Nov 2026, 19:28 UTC≈17,700 views295 reactionsread 7 November 2026

💥 Вибух

🙏195🤬82😢10🤣3❤2❤‍🔥2😡1

7 Nov 2026, 19:25 UTC≈18,900 views345 reactionsread 7 November 2026

❗️ Одеса, центр!

🙏246🤬72😡8🤣6🕊5❤4👎2🔥2

7 Nov 2026, 19:19 UTC≈20,200 views351 reactionsread 7 November 2026

❗️ Реактивний з моря, тримає курс на Одесу

🙏239🤬78😡10❤8🔥4🤣4🕊3❤‍🔥2

7 Nov 2026, 19:18 UTC≈20,200 views174 reactionsread 7 November 2026

🟡🚨 Одеса — жовта тривога (дронова небезпека)!

🙏117🤬43❤7🕊3🤣3😡1

Showing the 12 most recent of 3,089 posts we hold for @odesa_golovne. 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

@odesa_golovne edited 7 posts 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
10 August 2026
Most recent edit
29 October 2026

Posts recorded as deleted after publishing

We recorded 9 posts on @odesa_golovne 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
30 August 2026
Most recent seen missing
7 November 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
6

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Одеса Головне” (@odesa_golovne), 124,602 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/odesa_golovne.

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.