Telegram RegisterThe public register of Telegram
Telegram profile photo for Штрафы такси ПДД Москва

Channel

Штрафы такси ПДД Москва

@taxipartner

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

135subscribers

+2 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-1001179463595
TypeChannel
Username@taxipartner
Created20 November 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live12 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/taxipartner

Growth

1331351346 August 2026 — 133 subscribers9 August 2026 — 133 subscribers3 September 2026 — 134 subscribers12 September 2026 — 135 subscribers6 August 202612 September 2026
4 measurements spanning 37 days, net +2. 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 133–135 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 06:15135+1
3 Sept 2026, 11:37134+1
9 Aug 2026, 00:16133no change
6 Aug 2026, 09:09133first reading

Engagement

10 posts held, back to 8 August 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 10 posts for this entry, the most recent from 5 September 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Sept 2023, 17:48 UTC791 viewsread 9 August 2026

https://t.me/miketaxi Господа, заходите в телеграм канал нашего таксопарка 😉

18 Jul 2023, 05:30 UTC918 viewsread 9 August 2026
Photo

Очень частый штраф рядом с Шереметьево Ограничение скорости 60 км/ч

31 May 2023, 17:02 UTC≈1,040 viewsread 9 August 2026
Photo

Это уже глупость, а всего то надо ездить пристегнутым И сам целее и бабки на кармане

8 Apr 2023, 06:50 UTC≈1,140 viewsread 9 August 2026
Photo

Обратите внимание, уже достаточно продолжительное время, приходят штрафы за использование телефонов за рулём, но видимо этого мало. Теперь в некоторых местах стали ставить сразу 2 камеры подряд на небольшом промежутке дороги, на одно и тоже нарушение. В итоге вместо одного штрафа, получается 2

31 Mar 2023, 05:19 UTC≈1,090 viewsread 9 August 2026
Photo

В последнее время всё чаще инспектора ДПС штрафуют водителей, за непристегнутые ремни безопасности у пассажиров. Поэтому обращайте на это внимание и не получайте такие штрафы. Штраф 1000 р

27 Dec 2022, 04:40 UTC≈1,010 viewsread 9 August 2026
Photo

Не забывайте уступать дорогу пешеходам, а то штраф 1500 р

28 Aug 2022, 13:09 UTC≈1,160 viewsread 9 August 2026
Photo

Этот винегрет в виде знака, говорит о том, что останавливаться можно только машинам ТАКСИ на промежутке дороги 50 метров от знака. Останавливаться , но не устраивать стоянку! Ну и впереди тупик )

23 Aug 2022, 12:32 UTC835 viewsread 9 August 2026
Photo

Удивительно, что кто то ещё не понимает что надо пристегиваться Ладно не понимает. Но надо знать, что вся Москва усеена камерами в том числе и на непристегнутый ремень безопасности Итог: 4 штрафа за 3 часа по 500р

20 Aug 2022, 14:10 UTC665 viewsread 9 August 2026
Photo

Невыполнение требования ПДД об остановке перед стоп-линией. ул. Профсоюзная 109в с1 Штраф: 800р

8 Aug 2022, 09:11 UTC759 viewsread 9 August 2026
Photo

Не получилось оспорить штраф за колесо на земле Товарищи теперь в этом плане будьте предельно внимательны, а то 5000р на дороге не валяются Ниже фотка очередного подобного штрафа

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

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Штрафы такси ПДД Москва” (@taxipartner), 135 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/taxipartner.

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.