Channel
Игорь Лифанов
@igorlifanovofficial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cross-platform identity · Cite this entry
1,501subscribers
-10 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001784445474 |
|---|---|
| Type | Channel |
| Username | @igorlifanovofficial |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 2 times, most recently 19 October 2026 |
| On Telegram | t.me/igorlifanovofficial |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Oct 2026, 03:45 | 1,501 | -2 |
| 13 Oct 2026, 00:55 | 1,503 | -3 |
| 6 Oct 2026, 17:42 | 1,506 | +2 |
| 29 Sept 2026, 16:17 | 1,504 | +1 |
| 28 Sept 2026, 02:18 | 1,503 | no change |
| 19 Sept 2026, 12:37 | 1,503 | -1 |
| 14 Sept 2026, 21:39 | 1,504 | -2 |
| 11 Sept 2026, 18:21 | 1,506 | -1 |
| 27 Aug 2026, 20:33 | 1,507 | -1 |
| 24 Aug 2026, 14:56 | 1,508 | +1 |
| 20 Aug 2026, 20:25 | 1,507 | -2 |
| 17 Aug 2026, 16:58 | 1,509 | -1 |
| 14 Aug 2026, 11:45 | 1,510 | -1 |
| 8 Aug 2026, 03:15 | 1,511 | first 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.
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.
@omsxx · 83,883
Telegram ranks this channel #52 of 58 here — alongside 57 others — read 1 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Igor Lifanov |
|---|---|
| Description | Russian actor |
| Official site | http://www.igorlifanov.ru/ |
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 16 October 2026 — this entry's latest reading, not the date you are reading this.
“Игорь Лифанов” (@igorlifanovofficial), 1,501 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/igorlifanovofficial.
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.