Telegram RegisterThe public register of Telegram
Telegram profile photo for Пермское Чтиво

Channel

Пермское Чтиво

@permskoechtivo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

39,889subscribers

+7,312 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002065319195
TypeChannel
Username@permskoechtivo
DescriptionНовости Перми и Пермского края на доступном языке. По вопросам рекламы: @permpch Реклама через биржу: telega.in/c/permskoechtivo Прислать свою новость: @chtivonews Мессенджер Макс: max.ru/permskoechtivo
Created5 January 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live8 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/permskoechtivo

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

32,57739,91436,245.539,8896 August 20268 November 2026
62 measurements spanning 95 days, net +7,312. 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 31,476–41,015 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
8 Nov 2026, 16:3539,889-24
7 Nov 2026, 08:4539,913-1
6 Nov 2026, 07:5939,914+2
5 Nov 2026, 08:4939,912+9
4 Nov 2026, 07:3839,903+9
3 Nov 2026, 10:4939,894-8
2 Nov 2026, 10:2539,902+13
1 Nov 2026, 07:5939,889+1
31 Oct 2026, 11:2639,888+1
30 Oct 2026, 09:2839,887+43
29 Oct 2026, 07:5939,844+201
28 Oct 2026, 04:5039,643-7
27 Oct 2026, 01:4139,650+31
25 Oct 2026, 23:1739,619+58
24 Oct 2026, 22:5939,561+49
23 Oct 2026, 22:2539,512+363
22 Oct 2026, 21:0939,149+13
21 Oct 2026, 17:3639,136+12
20 Oct 2026, 11:0839,124+14
19 Oct 2026, 10:1539,110first reading

Engagement

1,875 posts held, back to 5 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 181 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.0%
avg views ÷ 39,889 subscribers
Avg views / post
9,590
639 posts measured
Reaction rate
1.44%
reactions ÷ views · ER floor
Posts in window
639
of 1,875 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held1,875 (5 August 2026 – 8 November 2026)
Views total6,127,868
Reactions total88,060
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 21:10 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
≈12,600
Videos
≈4,680
Links
≈15,500

Lifetime counters from Telegram’s own channel header, read 8 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 03m
Average length
31s

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

137,400 reactions across 1,000 posts, in 36 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤46,20933.6%
👎21,19115.4%
custom 603299116025381163110,2577.47%
💔8,6066.26%
🤣7,2395.27%
🤬6,3124.59%
👍6,2744.57%
🔥4,2173.07%
😭3,9512.88%
😱3,1962.33%
😢2,6731.95%
🎉2,3421.70%
🤯2,1151.54%
🕊2,0781.51%
😁1,3680.996%
🙏1,3030.948%
🤡9960.725%
🥰8170.595%
😐8100.59%
☃6910.503%
16 further kinds4,7553.46%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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 1,000 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 137,400 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 25 September 2026 to 8 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
106
across the posts below
Posts paid on
65
of 1,000 we hold a reading for · 7%
Most on one post
12
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @permskoechtivo. 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 25 September 2026 to 8 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.

Advertising

Ad load
0.6%
6 of 1,000 posts carry an ad marker
Regulatory tokens
5
posts carrying an erid · 5 distinct tokens
Median views · ads
9,020
over 6 measured posts
Median views · rest
9,450
over 994 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFH1fA8y124 October 202624 October 2026
2W5zFHxb44h114 October 202614 October 2026
2W5zFJ97Lrm125 September 202625 September 2026
2W5zFJAKtkR17 October 20267 October 2026
2W5zFJgFSKj112 October 202612 October 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 25 September 2026 to 8 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

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

8 Nov 2026, 17:00 UTC≈7,200 views124 reactionsread 8 November 2026
Photo

⚡️Начались запуски ВСУшных БПЛА от Харьковской области. Подпишись @permskoechtivo

❤75👎30🙏17🔥1😁1

8 Nov 2026, 16:56 UTC≈7,180 views67 reactionsread 8 November 2026
Photo

⚡️Пермь накрыли заморозки — сейчас температура воздуха опустилась до -4 градусов. По данным сервиса Яндекс. Погода, текущая температура ощущается как -10 градусов. На дорогах уже образовалась гололедица. Завтра утром и днём ожидается новая волна снегопада, которая добавит к текущему снежному покрову 2-3 см снега. Подпишись @permskoechtivo

❤41☃10😭7🎉3👎3🤬2🎄1

8 Nov 2026, 15:57 UTC≈7,630 views119 reactionsread 8 November 2026
Photo

⚡️В Краснокамске мужчина упал с пятого этажа, когда спускался вниз по простыням. Всё произошло днём 7 ноября на улице Энтузиастов. Прибывшие спасатели передали пострадавшего медикам. Мужчина был в сознании и жаловался на боль в спине. Подпишись @permskoechtivo

😐91😨17🤣9❤2

8 Nov 2026, 11:56 UTC≈9,810 views417 reactionsread 8 November 2026
Photo

⚡️Магазины КБ научились ставить людей на ноги. Подпишись @permskoechtivo

❤283custom 603299116025381163192🤣36🙏4👎2

8 Nov 2026, 11:32 UTC≈9,930 views128 reactionsread 8 November 2026

⚡️Солнце повторило рекорд XXI века: за сутки произошло 29 вспышек. На Земле началась магнитная буря уровня G5+. Подпишись @permskoechtivo

😱98❤14🥰8🤬4👍2👎1🙏1

8 Nov 2026, 11:05 UTC≈9,750 views158 reactionsread 8 November 2026
Photo

⚡️В Перми более тысячи «умных домофонов» планируют подключить к системе оповещения. Через них жители смогут получать голосовые сообщения о беспилотной и ракетной опасности, а также инструкции о дальнейших действиях. Подпишись @permskoechtivo

❤106👎30custom 603299116025381163116😁6

8 Nov 2026, 09:08 UTC≈9,790 views226 reactionsread 8 November 2026
Photo

⚡️Россияне будут отдыхать 11 дней подряд в новогодние праздники — с 31 декабря по 10 января. Подпишись @permskoechtivo

❤164💔44🔥16👎2

8 Nov 2026, 06:57 UTC≈10,000 views292 reactionsread 8 November 2026

⚡️Рост зарплаты приводит к алкоголизму, — наркологи. Премии и карьерный рост повышают риск спиться, потому что появляются деньги и различные поводы выпить, предупреждают врачи. Подпишись @permskoechtivo

👎162🤣108💊14custom 60329911602538116316❤2

8 Nov 2026, 05:43 UTC≈9,730 views33 reactionsread 8 November 2026

⚡️В Пермском крае возбудили уголовное дело после ДТП с пострадавшими. Авария произошла вечером 7 ноября на 143 километре трассы Усолье — Кудымкар в березниковском округе. Водитель микроавтобуса съехал в кювет, после чего машина перевернулась. Следственный комитет возбудил уголовное дело по статье об оказании услуг, не отвечающих требованиям безопасности. Подпишись @permskoechtivo

👎28❤5

7 Nov 2026, 17:58 UTC≈9,330 views43 reactionsread 8 November 2026

⚡️В ДТП на трассе Усолье – Кудымкар пострадали пять человек, в том числе ребёнок. По информации краевого Минздрава, всех пострадавших госпитализируют и осмотрят в березниковской больнице. Прокуратура начала проверку. Подпишись @permskoechtivo

😢38❤5

7 Nov 2026, 17:50 UTC≈9,410 views69 reactionsread 8 November 2026

⚡️В Пермском крае микроавтобус с людьми опрокинулся в кювет, — СМИ. На 143 километре автодороги Усолье — Кудымкар, у поворота на деревню Городище, произошло ДТП с микроавтобусом «Газель». По предварительной информации, водитель не справился с управлением, в результате чего автобус опрокинулся на бок и съехал в кювет. Погибших нет, количество пострадавших устанавливается. Сейчас на месте работают сотрудники полиции…

😨55❤7😱7

Showing the 12 most recent of 1,875 posts we hold for @permskoechtivo. 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

@permskoechtivo edited 5 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
18 August 2026
Most recent edit
27 October 2026

Posts recorded as deleted after publishing

We recorded 14 posts on @permskoechtivo 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
8 August 2026
Most recent seen missing
5 November 2026
Median time before seen missing
17 hours
Seen missing in the last 30 days
8

Forward network

Republished by

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

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 6 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.

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.

ЧП Пермь
@chp_59_perm · 263,172
#1
Подслушано Пермь
@overheardperm1 · 3,489
#2
.
@redgayva · 17
#3
Пермь с огоньком
@permjtop · 49,157
#4
Жесть Пермь
@zhest_perm_59 · 22,175
#5
Новости Перми и Края
@perm_smi · 91,310
#6
ПЛОХИЕ НОВОСТИ ПЕРМЬ
@zhest_perm · 16,658
#7
ЧП Пермь
@chp_159_59 · 174,451
#8
МОЙ ГОРОД - ПЕРМЬ!
@vikiperm · 29,134
#9
Кстати, Пермь
@permkstati · 2,114
#10
Пермь ЧП и ДТП, новости
@chp_prm · 27,992
#11
Пермь №1
@perm01 · 22,889
#12
Большая Пермь | URA.RU
@Bolshaya_P · 27,238
#13
Пермь и ЧЁ⁉️
@permyche · 2,687
#14
SARVAN FIGHT TEAM 👊🏼
@konchen12 · 477
#15
Свобода Концерт Холл Пермь
@svobodaconcertperm · 3,991
#16
Солнышко • Детский лагерь • Пермь
@suncamp59 · 1,548
#17
самер я
@sameronesnus · 578
#18
cloudr
@fuckcloudr · 4,090
#19
danilova lashes / ресницы пермь
@danilovalash · 1,267
#20
Подолей Алексей
@levapodoley · 659
#21
МС КИСУЛЯ
@mkisa_yourube · 2,525
#22

Read from Telegram’s recommendation API, most recently 4 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.

Пермь с огоньком
@permjtop · 49,157
Telegram ranks this channel #2 of 62 here — alongside 61 others — read 25 August 2026
ЧП Пермь
@chp_159_59 · 174,451
Telegram ranks this channel #2 of 40 here — alongside 39 others — read 17 August 2026
ЧП Пермь
@chp_59_perm · 263,172
Telegram ranks this channel #2 of 38 here — alongside 37 others — read 17 August 2026
Жесть Пермь
@zhest_perm_59 · 22,175
Telegram ranks this channel #3 of 37 here — alongside 36 others — read 20 September 2026
Новости Перми и Края
@perm_smi · 91,310
Telegram ranks this channel #3 of 57 here — alongside 56 others — read 17 August 2026
Наша Пермь
@permour159 · 45,193
Telegram ranks this channel #4 of 33 here — alongside 32 others — read 27 August 2026
ЧП ДТП Пермь
@chpdtpperm · 24,469
Telegram ranks this channel #7 of 76 here — alongside 75 others — read 16 September 2026
МОЙ ГОРОД - ПЕРМЬ!
@vikiperm · 29,134
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 8 September 2026
Пермь ЧП и ДТП, новости
@chp_prm · 27,992
Telegram ranks this channel #9 of 77 here — alongside 76 others — read 10 September 2026
Пермь №1
@perm01 · 22,889
Telegram ranks this channel #13 of 85 here — alongside 84 others — read 19 September 2026
Пермь Активная
@Perm_Active · 26,278
Telegram ranks this channel #23 of 89 here — alongside 88 others — read 12 September 2026
ПЕРМЬ СЕГОДНЯ
@perm1 · 135,843
Telegram ranks this channel #24 of 70 here — alongside 69 others — read 2 September 2026
59.RU | Новости Перми
@news59ru · 49,399
Telegram ranks this channel #25 of 97 here — alongside 96 others — read 25 August 2026
Большая Пермь | URA.RU
@Bolshaya_P · 27,238
Telegram ranks this channel #26 of 94 here — alongside 93 others — read 10 September 2026
Вакансии в Перми
@rabota_permd · 77,187
Telegram ranks this channel #46 of 70 here — alongside 69 others — read 26 August 2026
Работа в Перми
@vakansii_perm · 42,798
Telegram ranks this channel #62 of 76 here — alongside 75 others — read 29 August 2026

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

“Пермское Чтиво” (@permskoechtivo), 39,889 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/permskoechtivo.

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.