Telegram RegisterThe public register of Telegram
Telegram profile photo for Леонардо Дай Винчик ✅

Channel

Леонардо Дай Винчик ✅

@dayvinchik_leonardo

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

1,569subscribers

-43 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001335337654
TypeChannel
Username@dayvinchik_leonardo
Description⚠️ Warning: Many users report that this account impersonates a famous person or organisation.
Created29 January 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded27 September 2026
Last confirmed live27 September 2026
Measurements held15
On Telegramt.me/dayvinchik_leonardo

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.

Growth

1,5691,6121,590.56 August 2026 — 1,612 subscribers10 August 2026 — 1,610 subscribers13 August 2026 — 1,608 subscribers16 August 2026 — 1,606 subscribers19 August 2026 — 1,603 subscribers23 August 2026 — 1,599 subscribers25 August 2026 — 1,596 subscribers28 August 2026 — 1,593 subscribers31 August 2026 — 1,588 subscribers4 September 2026 — 1,584 subscribers9 September 2026 — 1,580 subscribers13 September 2026 — 1,579 subscribers17 September 2026 — 1,574 subscribers25 September 2026 — 1,569 subscribers27 September 2026 — 1,569 subscribers6 August 202627 September 2026
15 measurements spanning 51 days, net -43. 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 1,563–1,618 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 00:071,569no change
25 Sept 2026, 19:581,569-5
17 Sept 2026, 08:211,574-5
13 Sept 2026, 11:021,579-1
9 Sept 2026, 05:371,580-4
4 Sept 2026, 04:591,584-4
31 Aug 2026, 12:461,588-5
28 Aug 2026, 09:071,593-3
25 Aug 2026, 19:541,596-3
23 Aug 2026, 00:351,599-4
19 Aug 2026, 21:221,603-3
16 Aug 2026, 18:161,606-2
13 Aug 2026, 05:471,608-2
10 Aug 2026, 14:461,610-2
6 Aug 2026, 21:171,612first 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.

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.

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

“Леонардо Дай Винчик ✅” (@dayvinchik_leonardo), 1,569 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/dayvinchik_leonardo.

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.