Я-Саша, отец пятерых 👱🏻♀️👶🏼👦🏼🧑🏻🦱👧🏼
✅ актуальная афиша 🌳 🚴♀️ 🛼 🚣🏿♀️
✅ интересные новости
✅ если вы - родитель
❗️еще один канал https://t.me/Papa_PFO
👉 [email protected]
👉 @kznpapasha
Created
25 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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
28 measurements spanning 98 days, net -184. 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 6,714–6,957 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
12 Nov 2026, 14:15
6,745
-16
8 Nov 2026, 10:56
6,761
+19
5 Nov 2026, 13:31
6,742
-3
2 Nov 2026, 06:01
6,745
-9
30 Oct 2026, 06:49
6,754
-4
27 Oct 2026, 10:16
6,758
-13
24 Oct 2026, 06:45
6,771
+2
21 Oct 2026, 06:26
6,769
-1
17 Oct 2026, 23:47
6,770
-9
14 Oct 2026, 14:38
6,779
-7
11 Oct 2026, 06:01
6,786
-1
5 Oct 2026, 02:16
6,787
-29
26 Sept 2026, 10:59
6,816
-11
17 Sept 2026, 19:16
6,827
-3
14 Sept 2026, 01:37
6,830
-15
10 Sept 2026, 01:56
6,845
-17
4 Sept 2026, 10:20
6,862
-21
1 Sept 2026, 02:17
6,883
-6
29 Aug 2026, 05:14
6,889
+1
26 Aug 2026, 02:32
6,888
first reading
Engagement
122 posts held, back to 4 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 34 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.61%
avg views ÷ 6,745 subscribers
Avg views / post
648
77 posts measured
Reaction rate
1.11%
reactions ÷ views · ER floor
Posts in window
78
of 122 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 66 of 77 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 16 November 2026
Posts held
122 (4 August 2026 – 16 November 2026)
Views total
49,925
Reactions total
479
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Nov 2026, 15:38 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
≈10,200
Videos
≈1,480
Links
≈6,950
Lifetime counters from Telegram’s own channel header, read 16 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
7m 00s
Average length
32s
Measured directly from 13 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
848 reactions across 102 posts, in 18 distinct kinds. The most used accounts for 22.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
194
22.9%
❤
184
21.7%
😁
133
15.7%
😢
120
14.2%
🔥
108
12.7%
🙈
34
4.01%
💯
19
2.24%
👎
13
1.53%
custom 5220113606724557083
10
1.18%
👏
8
0.943%
🐳
5
0.59%
😨
5
0.59%
🤔
4
0.472%
😍
3
0.354%
🤬
3
0.354%
🤯
3
0.354%
👌
1
0.118%
👻
1
0.118%
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 104 of the 122 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 848 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 122 most recent posts we hold, published 4 August 2026 to 16 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
2
across the posts below
Posts paid on
1
of 121 we hold a reading for · 0.8%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kznpapa. 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 122 most recent posts we hold for this entry, published 4 August 2026 to 16 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: 14 of 78 posts held from the last 30 days (17.9%) 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).
Вместо детской площадки в парке Горького теперь парковка.
Саму детскую площадку перенесли глубже в лес, ближе к ресторану «Лето».
Вроде бы все , как раньше. Качели есть, горочки есть, песочница тоже имеется.
В лесу, летом 100% приятнее будет гулять под деревьями.
1 млн рублей составит маткапитал на второго ребёнка в феврале 2027 года.
Выплаты проиндексируют на 6,8%, после рождения первенца можно будет получить 778 488 рублей 59 копеек, на второго ребёнка — 1 028 743 рубля 71 копейку, если вы не забирали деньги в первый раз.
Что сегодня:
🌓 11.00 лаборатория увлекательной науки в школе «СОлНЦЕ» ДЛЯ детей ОТ 4-14 лет.
🐋Ребят ждут занятия на выбор: кубик Рубика, макетирование, лекции по искусству и русскому языку, научные эксперименты, творчество и многое другое.
➡️Между занятиями — активные переменки и чаепитие.
🌙Для родителей — беседа-знакомство с директором школы Павлом Анатольевичем Шмаковым и игра «Что? Где? Когда?»
🤩 Чаепитие
Прин…
Когда я спрашивал, чем заняться в дождь - я имел в виду не это!
На квартале выключили свет и колесо обозрения остановилось. Людей снимали с высоты 65 м
Что еще сегодня:
🧣11.00 вязаный маркет в Адонисе на Профсоюзной. Вход свободный
🐉 17.00 вечер татарских сказок и мифов в павильоне на набережной озера Кабан (у театра Тинчурина, со стороны ул. Марджани)
❤2
Showing the 12 most recent of 122 posts we hold for @kznpapa. 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
@kznpapa edited 1 post 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
16 November 2026
Most recent edit
16 November 2026
Posts recorded as deleted after publishing
We recorded 13 posts on @kznpapa 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
7 August 2026
Most recent seen missing
14 November 2026
Median time before seen missing
2 days
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 2 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.
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.
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.
Дети в Казани. Казань куда пойти @Kidsafisha · 19,056 Telegram ranks this channel #1 of 91 here — alongside 90 others — read 4 October 2026
КАЗАНЬ СЕГОДНЯ @kazany · 55,697 Telegram ranks this channel #1 of 89 here — alongside 88 others — read 27 August 2026
Рождественская @MarinaRozhdestvenskaia · 31,305 Telegram ranks this channel #4 of 73 here — alongside 72 others — read 6 September 2026
Парки и скверы Казани🌳 @parkikazani · 20,301 Telegram ranks this channel #5 of 92 here — alongside 91 others — read 28 September 2026
Подслушано | Казань и Республика Татарстан @kzn_xz · 22,453 Telegram ranks this channel #13 of 93 here — alongside 92 others — read 20 September 2026
Мэрия Казани @kzn_official · 26,041 Telegram ranks this channel #13 of 94 here — alongside 93 others — read 12 September 2026
Вокруг Казани | Куда пойти @kazanlenta · 38,027 Telegram ranks this channel #16 of 92 here — alongside 91 others — read 31 August 2026
ВТП | В Татарстане Поймут @vkazani · 48,712 Telegram ranks this channel #19 of 98 here — alongside 97 others — read 30 August 2026
Enter @enter_media · 70,541 Telegram ranks this channel #21 of 83 here — alongside 82 others — read 22 August 2026
Куда Пойти в Казани | Типичная Казань @kazankay · 84,692 Telegram ranks this channel #21 of 88 here — alongside 87 others — read 18 August 2026
КазаньДА | Новости Казани @kazan · 285,859 Telegram ranks this channel #21 of 75 here — alongside 74 others — read 12 August 2026
ТАТМЕДИА | Новости Казани и Татарстана @tatmediaofficial · 45,805 Telegram ranks this channel #22 of 95 here — alongside 94 others — read 26 August 2026
ТатарстанДа! @tatarstan_da · 34,736 Telegram ranks this channel #27 of 96 here — alongside 95 others — read 12 September 2026
Куда Казань Татарстан/ Куда пойти в Казани @kuda_kazan · 36,883 Telegram ranks this channel #29 of 73 here — alongside 72 others — read 31 August 2026
Моя Казань @my_kazan · 50,514 Telegram ranks this channel #32 of 89 here — alongside 88 others — read 24 August 2026
Go Kazan•Новости Казани @gokzn · 115,494 Telegram ranks this channel #32 of 79 here — alongside 78 others — read 14 August 2026
Жесть Казани @SHOCKkzn · 80,987 Telegram ranks this channel #34 of 87 here — alongside 86 others — read 19 August 2026
В Казани Поймут @kazanvkp · 94,692 Telegram ranks this channel #37 of 74 here — alongside 73 others — read 16 August 2026
ПОДСЛУШАНО КАЗАНЬ🧿 @podslukzn · 44,960 Telegram ranks this channel #39 of 97 here — alongside 96 others — read 8 September 2026
Инфо-Татар | Казань | Татарстан @info_tatar · 37,677 Telegram ranks this channel #39 of 95 here — alongside 94 others — read 31 August 2026
Tatarstan Republic | Казань @tatarstan_republic · 55,110 Telegram ranks this channel #39 of 91 here — alongside 90 others — read 23 August 2026
Инде @indekazancity · 22,797 Telegram ranks this channel #41 of 82 here — alongside 81 others — read 19 September 2026
Еду в Татарстан @eduvtatarstan · 37,453 Telegram ranks this channel #42 of 91 here — alongside 90 others — read 30 August 2026
Казань с огоньком @kazantop1 · 52,885 Telegram ranks this channel #42 of 83 here — alongside 82 others — read 24 August 2026
This channel appears in 40 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 12 November 2026 — this
entry's latest reading, not the date you are reading this.
“КАЗАНСКИЙ ПАПА” (@kznpapa), 6,745 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/kznpapa.
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.