Канал Яндекс Такси для водителей. Как стать партнёром Яндекс Про?
Заполните анкету по ссылке: https://clck.ru/3E6VTo
Ссылка на регистрацию в реестре РКН: https://www.gosuslugi.ru/snet/679f91d342df79578a5c4d4d
Created
27 June 2016 — measured — cross-checked against a third-party dataset (TGDataset)
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 66% 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
58 measurements spanning 92 days, net +34. 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 75,663–76,765 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)
Subscribers
Change
6 Nov 2026, 12:06
76,611
+3
5 Nov 2026, 14:30
76,608
-14
4 Nov 2026, 13:35
76,622
+2
3 Nov 2026, 11:45
76,620
-4
2 Nov 2026, 14:59
76,624
-9
1 Nov 2026, 16:05
76,633
-2
31 Oct 2026, 18:41
76,635
-2
30 Oct 2026, 18:40
76,637
-1
29 Oct 2026, 00:08
76,638
+8
26 Oct 2026, 21:02
76,630
-2
25 Oct 2026, 18:47
76,632
+6
24 Oct 2026, 16:35
76,626
+1
23 Oct 2026, 19:11
76,625
-1
21 Oct 2026, 11:56
76,626
+4
20 Oct 2026, 06:21
76,622
+8
19 Oct 2026, 03:16
76,614
+2
18 Oct 2026, 03:31
76,612
+1
17 Oct 2026, 06:18
76,611
+5
15 Oct 2026, 07:25
76,606
+8
14 Oct 2026, 08:50
76,598
first reading
Engagement
39 posts held, back to 6 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 186 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
38.1%
avg views ÷ 76,611 subscribers
Avg views / post
29,200
2 posts measured
Reaction rate
3.61%
reactions ÷ views · ER floor
Posts in window
2
of 39 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 11 October 2026
Posts held
39 (6 July 2026 – 11 October 2026)
Views total
58,400
Reactions total
2,108
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 19:20 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.
What this channel posts
Photos
≈1,160
Videos
≈103
Links
≈488
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
10m 01s
Average length
1m 07s
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
14,125 reactions across 39 posts, in 7 distinct kinds. The most used accounts for 62.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👎
8,890
62.9%
👍
2,617
18.5%
❤
1,455
10.3%
🔥
580
4.11%
😁
457
3.24%
👏
69
0.488%
😎
57
0.404%
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 39 of the 39 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 14,125 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 6 July 2026 to 11 October 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
Telegram’s own ‘edited’ marker: 1 of 2 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Приносим извинения, что сбои наших сервисов сейчас отнимают ваше время и силы.
Мы обязательно разберёмся с каждым заказом и поможем решить возникшие вопросы как можно скорее. Все наши специалисты сейчас круглосуточно восстанавливают работу сервисов. Особое внимание уделяем Яндекс Про, от которого зависят все поездки и заказы.
Спасибо каждому из вас, кто в этой непростой ситуации выходит на линию и помогает пассажир…
Каждый день вы помогаете людям добраться домой и на работу, привозите еду, покупки и посылки. Вы стали частью каждого их дня, а Яндекс Про — частью вашего. Мы знаем, как важно, чтобы сервис не подводил, поэтому хотим рассказать, что происходит.
Яндекс Про зависит от нашего «железного сердца» — дата-центров. За последние дни они пострадали. Но главное, что не пострадали люди, а наши команды уже делают все, чтобы как …
Перекус таксиста чееееек!
Специально ко Дню водителя такси Идрис Ёров составил подборку лучших блюд из Яндекс Лавки для перекуса в авто: там и плов, и борщ, и свежие овощи 😋
Кто, как не он, знает, как вкусно и выгодно подкрепиться между заказами.
Смотрите видео, а если проголодаетесь — заказывайте еду и напитки из подборки со скидкой 20% по промокоду: PEREKUSTAXI
Ваши достижения за рулём
Помните, когда вы в первый раз вышли на линию? Сколько километров суммарно проехали?
Собрали статистику ваших поездок со дня подключения к сервису. Можете посмотреть их в сториз приложения Про.
С праздником! С Днём водителя такси!
Спасибо за ваш труд! Каждый день пассажиры успевают на работу, самолёты и поезда, ездят за покупками и встречаются с близкими.
Спасибо, что вы с нами! В карточках рассказали, какие бонусы подготовили для водителей в честь праздника.
Удачных поездок и отличного праздничного настроения!
👍 — С праздником всех коллег!
👎256👍83❤28🔥8😁4
Showing the 12 most recent of 39 posts we hold for @driveryandex. 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.
Posts edited after publishing
@driveryandex edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
22 August 2026
Most recent edit
22 August 2026
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.
Mentions
Named by 20 registered channels — 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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Яндекс Про | Водители” (@driveryandex), 76,611 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/driveryandex.
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.
