Telegram RegisterThe public register of Telegram
Telegram profile photo for Пилот Валико и его Boeing 737 (channel)

Channel

Пилот Валико и его Boeing 737 (channel)

@pillot_valiko

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

152subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001553229657
TypeChannel
Username@pillot_valiko
DescriptionНемного про авиацию
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/pillot_valiko

Growth

1526 August 2026 — 152 subscribers8 August 2026 — 152 subscribers6 August 20268 August 2026
2 measurements spanning 2 days. 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 151–153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:31152no change
6 Aug 2026, 13:50152first reading

Engagement

7 posts held, back to 7 March 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 28 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
53
Videos
9
Links
16

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

89 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 40.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3640.4%
2629.2%
🔥2123.6%
👏33.37%
🤣22.25%
❤‍🔥11.12%

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

Measured over the 7 most recent posts we hold, published 7 March 2023 to 28 February 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

28 Feb 2026, 18:18 UTC182 views10 reactionsread 8 August 2026
Photo

Значится в коем то веке Валико достал мокасины, очки и погрузил все в рабочий чемодан, так как ему достался рейс со стоянкой в Дубай, план «Бобер» ввели и в песках. 😁😁😁 Ну чтож, нечего к хорошему привыкать… Где там у нас Норильск на карте?

👍72❤‍🔥1

31 Jan 2026, 13:23 UTC249 views12 reactionsread 8 August 2026

Держите после новогоднюю историю… возможно, даже выдумка. Задержки и решения Готовимся к вылету. 1987 год, Валлико - сейчас молодой счастливый капитан, сразу после ввода, да еще и после отпуска. Штурманская-рум аэропорта Внуково. — Отлично, господа, быстрый разворотный вечерний Ленинград из Внуково, одна нога тут вторая там и спать как люди будем… Летим всего 1:05, в Ленинграде небольшой снежок, болтанки в полё

9🔥3

17 Jan 2026, 10:37 UTC231 views30 reactionsread 8 August 2026
Photo

Есть кто живой? Я тут про бложик вспомнил. Предполагается много командировок скоро, можно будет и пописать сюда… Правда без инстаграмных лухари пайлот лайф, со стаканчиком кофе и гостиницей 5звезд. Суровые пилотобулни. Ночные, усталость, мороз, обливы.

🔥167👍4👏3

7 Mar 2023, 09:36 UTC≈1,500 views16 reactionsread 8 August 2026
Photo

Photo, posted without a caption

👍122🔥2

7 Mar 2023, 09:36 UTC≈1,430 views9 reactionsread 8 August 2026
Photo

Photo, posted without a caption

👍81

7 Mar 2023, 09:36 UTC≈1,100 views8 reactionsread 8 August 2026
Photo

Photo, posted without a caption

👍53

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

Citation-graph rank

Citation-graph rank — 1,139,311 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Пилот Валико и его Boeing 737 (channel)” (@pillot_valiko), 152 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pillot_valiko.

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.