Channel

Авторские курсы и книги Михаила Тарасова Timcore

@books_security_and_programming

On this record: Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

2,145subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	-1001662454428
Type	Channel
Username	@books_security_and_programming
Created	Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	17 August 2026
Measurements held	5
Confirmed unchanged	1 time, most recently 17 August 2026
On Telegram	t.me/books_security_and_programming

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Хакер | Этичный хакинг с Михаилом Тарасовым (Timcore)
@timcore_hacking · Channel1,647 subscribers Школа программирования и этичного хакинга «Timcore»
@school_timcore · Channel490 subscribers

Growth

5 measurements spanning 10 days, net -13. 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 2,143–2,160 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
17 Aug 2026, 20:04	2,145	-7
14 Aug 2026, 23:24	2,152	-4
11 Aug 2026, 12:14	2,156	-2
7 Aug 2026, 20:31	2,158	no change
7 Aug 2026, 17:42	2,158	first reading

Engagement

20 posts held, back to 1 July 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days: 6.89%; avg views ÷ 2,145 subscribers
Avg views / post: 148; 8 posts measured
Reaction rate: —; this channel exposes no reaction counts
Posts in window: 8; of 20 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
Window	Rolling 30 days · latest post in window 7 August 2026
Posts held	20 (1 July 2026 – 7 August 2026)
Views total	1,182
Reactions total	—
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	7 Aug 2026, 20:31 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.