Telegram RegisterThe public register of Telegram
Telegram profile photo for KİTAP YURDU

Channel

KİTAP YURDU

@kitapyurdu2

On this record: Topic · Growth · Engagement · Cite this entry

3,647subscribers

+568 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-1003334879616
TypeChannel
Username@kitapyurdu2
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live3 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/kitapyurdu2

Topic

Literature — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

3,0793,6473,3637 August 2026 — 3,079 subscribers8 August 2026 — 3,083 subscribers11 August 2026 — 3,133 subscribers15 August 2026 — 3,172 subscribers18 August 2026 — 3,194 subscribers21 August 2026 — 3,225 subscribers24 August 2026 — 3,237 subscribers28 August 2026 — 3,256 subscribers31 August 2026 — 3,280 subscribers4 September 2026 — 3,301 subscribers9 September 2026 — 3,328 subscribers9 September 2026 — 3,328 subscribers17 September 2026 — 3,365 subscribers25 September 2026 — 3,434 subscribers4 October 2026 — 3,498 subscribers11 October 2026 — 3,544 subscribers14 October 2026 — 3,562 subscribers18 October 2026 — 3,579 subscribers21 October 2026 — 3,586 subscribers24 October 2026 — 3,607 subscribers28 October 2026 — 3,627 subscribers31 October 2026 — 3,639 subscribers3 November 2026 — 3,647 subscribers7 August 20263 November 2026
23 measurements spanning 87 days, net +568. 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,994–3,732 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
3 Nov 2026, 01:293,647+8
31 Oct 2026, 10:103,639+12
28 Oct 2026, 01:003,627+20
24 Oct 2026, 22:113,607+21
21 Oct 2026, 13:283,586+7
18 Oct 2026, 01:573,579+17
14 Oct 2026, 15:503,562+18
11 Oct 2026, 05:413,544+46
4 Oct 2026, 17:573,498+64
25 Sept 2026, 06:373,434+69
17 Sept 2026, 07:013,365+37
9 Sept 2026, 13:093,328no change
9 Sept 2026, 03:403,328+27
4 Sept 2026, 04:013,301+21
31 Aug 2026, 08:573,280+24
28 Aug 2026, 01:233,256+19
24 Aug 2026, 20:443,237+12
21 Aug 2026, 04:183,225+31
18 Aug 2026, 08:223,194+22
15 Aug 2026, 05:153,172first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“KİTAP YURDU” (@kitapyurdu2), 3,647 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/kitapyurdu2.

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.