Telegram RegisterThe public register of Telegram
Telegram profile photo for Исповедник

Channel

Исповедник

@Ispovednik_K

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

8,816subscribers

-463 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-1002229515563
TypeChannel
Username@Ispovednik_K
DescriptionЖизненные истории, мысли и наблюдения 📖 Любовь, поступки и случайности, которые меняют многое, а пермь незаметно появляется среди этих сюжетов ✨
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/Ispovednik_K

Topic

Other / unclassifiable — 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 51% 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
@anon_sydbi/128009 Aug 2026, 09:00 UTC@Ispovednik_K/12701 · this entry9 Aug 2026, 09:00 UTC1.00under a minute
@anon_sydbi/1291015 Aug 2026, 05:00 UTC@Ispovednik_K/12821 · this entry15 Aug 2026, 05:00 UTC1.00under a minute
@Ispovednik_K/12929 · this entry21 Aug 2026, 05:00 UTC@anon_sydbi/1303221 Aug 2026, 05:00 UTC1.00under a minute
@Ispovednik_K/12970 · this entry23 Aug 2026, 07:00 UTC@anon_sydbi/1306723 Aug 2026, 07:00 UTC1.00under a minute
@Ispovednik_K/13027 · this entry26 Aug 2026, 05:00 UTC@anon_sydbi/1311326 Aug 2026, 05:00 UTC1.00under a minute
@Ispovednik_K/13046 · this entry27 Aug 2026, 05:00 UTC@anon_sydbi/1314027 Aug 2026, 05:00 UTC1.00under 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
@anon_sydbi18 (8/8 hand-verifiable sample passed)1.00under a minute@anon_sydbi (12–6)
@zhenskie_istoriy15 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–7)
@Sp_letnica14 (8/8 hand-verifiable sample passed)1.00under a minute@Sp_letnica (8–6)
@Otkrovenii_ya9 (8/8 hand-verifiable sample passed)1.00under a minute@Otkrovenii_ya (6–3)
@DamskiuGolos8 (8/8 hand-verifiable sample passed)1.00under a minute@DamskiuGolos (5–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. 38 of the 38 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 300 comparable posts for this entry, running 6 August 2026 to 14 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,8169,2799,047.57 August 2026 — 9,279 subscribers7 August 2026 — 9,279 subscribers7 August 2026 — 9,278 subscribers10 August 2026 — 9,277 subscribers14 August 2026 — 9,276 subscribers17 August 2026 — 9,223 subscribers20 August 2026 — 9,203 subscribers24 August 2026 — 9,214 subscribers27 August 2026 — 9,208 subscribers30 August 2026 — 9,216 subscribers1 September 2026 — 9,198 subscribers6 September 2026 — 9,179 subscribers10 September 2026 — 9,157 subscribers14 September 2026 — 9,161 subscribers18 September 2026 — 9,156 subscribers27 September 2026 — 9,120 subscribers5 October 2026 — 9,068 subscribers12 October 2026 — 9,030 subscribers15 October 2026 — 8,994 subscribers18 October 2026 — 8,975 subscribers21 October 2026 — 8,954 subscribers23 October 2026 — 8,948 subscribers27 October 2026 — 8,936 subscribers30 October 2026 — 8,912 subscribers2 November 2026 — 8,890 subscribers5 November 2026 — 8,865 subscribers9 November 2026 — 8,849 subscribers13 November 2026 — 8,816 subscribers7 August 202613 November 2026
28 measurements spanning 98 days, net -463. 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,747–9,348 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
13 Nov 2026, 14:478,816-33
9 Nov 2026, 03:168,849-16
5 Nov 2026, 17:048,865-25
2 Nov 2026, 10:378,890-22
30 Oct 2026, 00:358,912-24
27 Oct 2026, 05:168,936-12
23 Oct 2026, 20:558,948-6
21 Oct 2026, 04:578,954-21
18 Oct 2026, 03:188,975-19
15 Oct 2026, 07:268,994-36
12 Oct 2026, 04:569,030-38
5 Oct 2026, 10:169,068-52
27 Sept 2026, 15:209,120-36
18 Sept 2026, 16:399,156-5
14 Sept 2026, 10:219,161+4
10 Sept 2026, 23:219,157-22
6 Sept 2026, 06:219,179-19
1 Sept 2026, 23:589,198-18
30 Aug 2026, 00:539,216+8
27 Aug 2026, 00:049,208first reading

Engagement

430 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.35%
avg views ÷ 8,816 subscribers
Avg views / post
295
144 posts measured
Reaction rate
0.415%
reactions ÷ views · ER floor
Posts in window
144
of 430 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 35 of 144 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 15 November 2026
Posts held430 (6 August 2026 – 15 November 2026)
Views total42,546
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 01:24 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
≈114
Videos
≈5
Links
≈6,050

Lifetime counters from Telegram’s own channel header, read 15 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.

Reaction mix

139 reactions across 102 posts, in 6 distinct kinds. The most used accounts for 90.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤12690.6%
🔥64.32%
👍21.44%
😭21.44%
🤯21.44%
😁10.719%

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 112 of the 430 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 139 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 430 most recent posts we hold, published 6 August 2026 to 15 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: 0 of 144 posts held from the last 30 days (0%) 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).

15 Nov 2026, 00:00 UTC15 views1 reactionsread 15 November 2026

Если я в юности хотела сделать какую-то глупость, мама никогда меня не отговаривала и не ругала, поскольку я была упряма. Так вот, она заставляла меня писать что-то вроде: "Я абсолютно осознанно решила сделать татуировку/отрезать волосы/бросить танцы/ встречаться с идиотом….и т.д. Полностью беру на себя ответственность за этот поступок и обещаю никого не винить." Теперь-то я понимаю, что много дров наломала, и от это…

❤1

14 Nov 2026, 16:00 UTC101 views1 reactionsread 15 November 2026

Был у меня друг по переписке - парень, чуть старше меня. Нашли общий язык, много переписывались, но так как живем в разных городах, возможности встретиться не было. И так получилось, что без памяти влюбилась в него, привыкла к общению. Оказалось, взаимно! Вот только продлилось это три года, а в жизни так и не встретились. Итог: ссоры, депрессия, слёзы. Оказалось, что всё это время переписывалась с девушкой чуть младш…

❤1

14 Nov 2026, 12:00 UTC143 views2 reactionsread 15 November 2026

Год назад договорились с подругой, что если одна из нас выиграет в лотерею, то разделим приз пополам. За это время она купила всего четыре билета, а вот я впала в манию. Могла с зарплаты и аванса профукать по несколько тысяч. Уже переживала за свою игровую зависимость, решила бросить, и тут наконец выиграла! Не джекпот, но суммы хватит, чтобы добавить к сбережениям и купить маленькую однушку в нашем городе (не Москва…

❤2

14 Nov 2026, 10:00 UTC159 views1 reactionsread 15 November 2026

В свое время моя мама на Новый год устроила своего рода гадание: вытягиваешь "конфету" из подарочной бумаги, и там будет что-то, предсказывающее, как пройдет наступающий год. Папе достались аскорбинки, символизирующее здоровье. А второго числа у деда был день рождения, приехали его дети со своими детьми. Когда мы играли, нам понадобилось что-то достать со шкафа, я залезла на стул, заглянула туда и увидела витаминки. …

❤1

14 Nov 2026, 08:00 UTC176 views1 reactionsread 15 November 2026

Работала в LEGO. Были в продаже мини-фигурки, они выходили в коллекции по 16 штук. Но в коробке приходили по 50, и узнать, какая внутри, нельзя. Они были дешёвые (99 рублей), а магазин был в обычном районе. Дети после школы заходили и брали по 1-2 штуки, всем хотелось без повторов, поэтому дети щупали пакеты и по явным деталям определяли, что внутри. Сама компания нам запрещала щупать, но я часто, видя мучения детей,…

❤1

14 Nov 2026, 06:00 UTC195 views1 reactionsread 15 November 2026

Однажды в поезде познакомилась с семейной парой. Рассказали историю своей женитьбы. Встретились в кафе во Львове случайно. Обменялись телефонами. Она решила не мешкать и через две недели приехала к нему в Энергодар. Легенда - вроде на свадьбу к подруге. Очень боялась спалиться, но там жить плавно и осталась. Бабушка передала платье поездом, расписались через 2 недели. Потом уже сказала своим родителям, была свадьба, …

❤1

14 Nov 2026, 05:00 UTC202 viewsread 15 November 2026

Муж моей подруги ум@р от рака. Его дети долго писали ему СМС-сообщения о том, как они поживают. Номер передали другому абоненту, и он начал отвечать. Отвечал на каждое сообщение, так как понял, что к чему . Подбадривал их, писал в ответ очень хорошие слова. Когда их мама узнала, то решила позвонить. Говорили они по телефону до утра. Встретились. Спустя почти пять лет она выходит замуж, дети его называют папа-два, он…

14 Nov 2026, 00:00 UTC244 views1 reactionsread 15 November 2026

На моей бывшей работе был сотрудник. Если кто-то косячил, то он сразу шел и говорил об этом РГ, а не сотруднику, чтобы все спокойно исправить. Со временем он и меня убедил в том, что так нужно: "Пусть РГ с ним и разбирается". Я часто смотрю на "обвиненных" на которых пожаловались, и мне их так жалко. Решил, что хватит, и стал говорить с ними без доносов. Отношения стали лучше, и работа в коллективе тоже. Мне похуй на…

❤1

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

@Ispovednik_K 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
8 August 2026
Most recent edit
27 August 2026

Mentions

Named by 3 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.

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

“Исповедник” (@Ispovednik_K), 8,816 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/Ispovednik_K.

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.