Telegram RegisterThe public register of Telegram
Telegram profile photo for Типові Чернівці | Новини

Channel

Типові Чернівці | Новини

@typical_cv

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,829subscribers

+335 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001175322949
TypeChannel
Username@typical_cv
Description🏙️ Новини Чернівців та Буковини ⚡️ Все важливе — тут
Created4 February 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/typical_cv

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 5 other registered channels. 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
@molbuk/5875425 Aug 2026, 12:40 UTC@typical_cv/37431 · this entry25 Aug 2026, 14:08 UTC0.9888 minutes
@molbuk/614715 Nov 2026, 16:40 UTC@typical_cv/39507 · this entry5 Nov 2026, 17:36 UTC0.9755 minutes
@molbuk/615146 Nov 2026, 19:00 UTC@typical_cv/39527 · this entry6 Nov 2026, 19:47 UTC0.9646 minutes
@molbuk/581806 Aug 2026, 18:40 UTC@typical_cv/36966 · this entry6 Aug 2026, 19:08 UTC0.9628 minutes
@molbuk/582519 Aug 2026, 14:20 UTC@typical_cv/37030 · this entry9 Aug 2026, 15:32 UTC0.9572 minutes
@molbuk/614314 Nov 2026, 14:01 UTC@typical_cv/39476 · this entry4 Nov 2026, 14:37 UTC0.9435 minutes
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
@molbuk37 (8/8 hand-verifiable sample passed)0.9648 minutes@molbuk (37–0)
@pereval_media20 (8/8 hand-verifiable sample passed)0.9426 minutes@pereval_media (19–1)
@promincv16 (8/8 hand-verifiable sample passed)1.0012 minutes@promincv (15–1)
@ChernivtsiCityCouncil12 (8/8 hand-verifiable sample passed)1.0047 minutes@ChernivtsiCityCouncil (12–0)
@vazhlyvo_cv7 (7/7 hand-verifiable sample passed)0.998 minutesthis entry (4–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. 86 of the 86 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 316 comparable posts for this entry, running 6 August 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 keys clone_copy · clone_mutual, 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

8,4818,8318,6567 August 2026 — 8,494 subscribers8 August 2026 — 8,496 subscribers10 August 2026 — 8,497 subscribers13 August 2026 — 8,485 subscribers17 August 2026 — 8,481 subscribers20 August 2026 — 8,484 subscribers24 August 2026 — 8,481 subscribers27 August 2026 — 8,502 subscribers30 August 2026 — 8,503 subscribers2 September 2026 — 8,519 subscribers7 September 2026 — 8,521 subscribers11 September 2026 — 8,522 subscribers15 September 2026 — 8,518 subscribers26 September 2026 — 8,619 subscribers5 October 2026 — 8,629 subscribers11 October 2026 — 8,639 subscribers14 October 2026 — 8,649 subscribers18 October 2026 — 8,673 subscribers21 October 2026 — 8,681 subscribers23 October 2026 — 8,669 subscribers27 October 2026 — 8,755 subscribers29 October 2026 — 8,736 subscribers1 November 2026 — 8,742 subscribers4 November 2026 — 8,827 subscribers7 November 2026 — 8,831 subscribers10 November 2026 — 8,829 subscribers8,8297 August 202610 November 2026
26 measurements spanning 95 days, net +335. 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 8,429–8,884 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
10 Nov 2026, 19:108,829-2
7 Nov 2026, 07:478,831+4
4 Nov 2026, 00:378,827+85
1 Nov 2026, 08:288,742+6
29 Oct 2026, 17:108,736-19
27 Oct 2026, 02:468,755+86
23 Oct 2026, 23:298,669-12
21 Oct 2026, 08:368,681+8
18 Oct 2026, 02:508,673+24
14 Oct 2026, 19:558,649+10
11 Oct 2026, 14:588,639+10
5 Oct 2026, 01:008,629+10
26 Sept 2026, 09:218,619+101
15 Sept 2026, 13:178,518-4
11 Sept 2026, 20:188,522+1
7 Sept 2026, 04:568,521+2
2 Sept 2026, 20:598,519+16
30 Aug 2026, 15:058,503+1
27 Aug 2026, 17:078,502+21
24 Aug 2026, 17:488,481first reading

Engagement

414 posts held, back to 6 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 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.8%
avg views ÷ 8,829 subscribers
Avg views / post
1,660
214 posts measured
Reaction rate
0.638%
reactions ÷ views · ER floor
Posts in window
214
of 414 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 211 of 214 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 held414 (6 August 2026 – 14 November 2026)
Views total355,929
Reactions total2,241
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 13:21 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
≈29,000
Videos
≈5,450
Links
≈11,100

Lifetime counters from Telegram’s own channel header, read 14 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
40m 04s
Average length
49s

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

3,677 reactions across 385 posts, in 41 distinct kinds. The most used accounts for 26.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤97526.5%
🤣36910.0%
😢3549.63%
🤬2747.45%
👍2687.29%
🙏2446.64%
🤮2155.85%
🕊1484.03%
😭1443.92%
👎1133.07%
🤡962.61%
🔥802.18%
🖕541.47%
😁541.47%
👏441.20%
🤯421.14%
❤‍🔥320.87%
💩290.789%
😱260.707%
🥰210.571%
21 further kinds952.58%

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 390 of the 414 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 3,677 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 414 most recent posts we hold, published 6 August 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: 12 of 214 posts held from the last 30 days (5.61%) 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, 12:14 UTC433 viewsread 14 November 2026
Photo

🐶 У Чернівцях загубилася собака на кличку Зоська. Район вул. Рівненської та прилеглих вулиць. Перелякана, не агресивна, до рук не підходить. Прикмети: біла грудка, руді боки, шов після стерилізації збоку. Якщо бачили Зоську або знаєте, де вона може бути, телефонуйте: +380 95 888 0 190 🙏

14 Nov 2026, 10:13 UTC772 views10 reactionsread 14 November 2026
Video

Пожежа у торговому павільйоні на ринку «Добробут». Рятувальники показали, як гасили вогонь

❤5🤡2😱2🤣1

14 Nov 2026, 07:24 UTC≈1,020 views12 reactionsread 14 November 2026

💡Скасували графіки відключень світла на Буковині.

👍10❤1🤣1

14 Nov 2026, 06:02 UTC≈1,160 views16 reactionsread 14 November 2026
Photo

🕯️Сьогодні, 14 листопада, відбудеться прощання з військовослужбовцями, які стали на захист України від російських окупантів. Головному сержантові Юрію Решетнику, воїну Збройних сил України, віддадуть останню шану о 13:00 у Кострижівці – буде встановлено кенотаф у пам'ять героя. Із солдатом Михайлом Гуштюком, воїном військової частини А4718, попрощаються о 09:00 у Турятці. 🇺🇦Вічна пам'ять та слава Героям. Глибокі с…

😢11🕊4🤣1

13 Nov 2026, 19:55 UTC≈1,410 views32 reactionsread 14 November 2026
Photo

На фронті загинув захисник з Шипинців Андрій Мітран 🇺🇦 Підтвердилася загибель жителя села Шипинці Андрія Васильовича Мітрана, 1984 р. н., який загинув 5 серпня 2026 року під час бойового завдання поблизу села Горівка Пологівського району Запорізької області.

🙏14😢8😭6🕊2❤1🤮1

13 Nov 2026, 19:11 UTC≈1,420 views3 reactionsread 14 November 2026
Photo

💡 Орієнтовний графік відключень світла на завтра, 14 листопада.

👍1🤣1😭1

13 Nov 2026, 17:18 UTC≈1,530 views8 reactionsread 14 November 2026
Photo

До кінця доби 13 листопада на Буковині світло не вимикатимуть Всі групи будуть з електрикою

👍5❤2🤣1

13 Nov 2026, 16:57 UTC≈1,560 views25 reactionsread 14 November 2026
Photo

На Донеччині загинув захисник із Сокирян Віктор Микитюк 🇺🇦 Захищаючи Україну, внаслідок артобстрілу 12 листопада 2025 року на Донеччині загинув 36-річний молодший сержант, командир відділення снайперів із Сокирян Віктор Миколайович Микитюк. Рік він вважався зниклим безвісти. Добровольцем став до війська 26 лютого 2022 року. Нагороджений, зокрема, відзнакою Президента "За оборону України", "Золотим хрестом" Головнок…

🕊11😭9😢4🤣1

13 Nov 2026, 16:20 UTC≈1,470 views12 reactionsread 14 November 2026

❗️росія завдасть масового удару по Україні у найближчі 48 годин: є попередження, — розвідспільнота США

🤬7😁2🙏2👍1

13 Nov 2026, 15:37 UTC≈1,490 views17 reactionsread 14 November 2026
Photo

На Буковину приїхали 130 дітей із прифронтової Чернігівщини 🌄 130 дітей військовослужбовців, полонених і загиблих Захисників та Захисниць України, а також дітей-сиріт у межах проєкту "Карпатська зміна" три тижні відпочиватимуть на Буковині, знайомитимуться з її традиціями, відвідуватимуть екскурсії та активності.

❤15👏1🤣1

13 Nov 2026, 15:05 UTC≈1,530 views4 reactionsread 14 November 2026
Photo

🚨 У Чернівцях біля 43-го дитсадка дерево впало на автомобіль Інцидент стався на проспекті Незалежності, 86. За словами очевидців, через це утворився затор в обох напрямках. Водіїв просять врахувати ситуацію та за можливості обрати інший маршрут.

👍2❤1🤣1

13 Nov 2026, 14:52 UTC≈1,450 views3 reactionsread 14 November 2026
Photo

💡Оновлений графік на сьогодні.

👎1🤣1🤬1

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

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.

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.

Чернівецька міська рада
@ChernivtsiCityCouncil · 27,977
Telegram ranks this channel #10 of 79 here — alongside 78 others — read 10 September 2026
CHERNIVTSIGRAM БУКОВИНА ЧЕРНІВЦІ ЧЕРНІВЦІГРАМ
@chernivtsigram · 29,739
Telegram ranks this channel #13 of 82 here — alongside 81 others — read 9 September 2026
Руслан Осипенко / Чернівецька ОВА
@chernivetskaODA · 32,103
Telegram ranks this channel #14 of 89 here — alongside 88 others — read 8 September 2026
РОБОТА ЧЕРНІВЦІ ВАКАНСІЇ
@pidrobitok_chernovci · 36,312
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 2 September 2026
PEREVAL Чернівці / Буковина
@pereval_media · 45,431
Telegram ranks this channel #17 of 84 here — alongside 83 others — read 27 August 2026
ХОРОШІ ЧЕРНІВЦІ CHERNIVTSI БУКОВИНА ХЧ
@goodchernivtsi · 116,383
Telegram ranks this channel #18 of 84 here — alongside 83 others — read 14 August 2026
21 Ужгород
@uzhgorod_21 · 20,805
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 1 October 2026
Чернівці⚡️Труха
@chernivcitruexa · 109,812
Telegram ranks this channel #20 of 83 here — alongside 82 others — read 16 August 2026
Закарпатич | Новини
@zakarpatych · 27,467
Telegram ranks this channel #55 of 87 here — alongside 86 others — read 11 September 2026

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

“Типові Чернівці | Новини” (@typical_cv), 8,829 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/typical_cv.

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.