Telegram RegisterThe public register of Telegram
Telegram profile photo for На Пермь! Попутчики, поездки Екатеринбург, Челябинск, Казань

Channel

На Пермь! Попутчики, поездки Екатеринбург, Челябинск, Казань

@permeka

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

307subscribers

-9 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001738626700
TypeChannel
Username@permeka
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/permeka

Topic

Local community — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@permeka/4229 · this entry31 Jul 2026, 07:10 UTC@vpragu/232831 Jul 2026, 07:13 UTC1.004 minutes
@permeka/4231 · this entry1 Aug 2026, 07:24 UTC@vpragu/23291 Aug 2026, 07:30 UTC1.006 minutes
@permeka/4232 · this entry2 Aug 2026, 07:24 UTC@vpragu/23302 Aug 2026, 07:28 UTC1.004 minutes
@permeka/4239 · this entry4 Aug 2026, 07:13 UTC@vpragu/23354 Aug 2026, 07:17 UTC1.005 minutes
@permeka/4248 · this entry8 Aug 2026, 07:16 UTC@vpragu/23418 Aug 2026, 07:19 UTC1.004 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@vpragu5 (5/5 hand-verifiable sample passed)1.005 minutesthis entry (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 13 comparable posts for this entry, running 31 July 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 5 channels, the one whose matching posts we hold earliest is @izik5. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

307328317.57 August 2026 — 316 subscribers8 August 2026 — 317 subscribers8 August 2026 — 317 subscribers16 August 2026 — 316 subscribers23 August 2026 — 321 subscribers31 August 2026 — 327 subscribers9 September 2026 — 328 subscribers18 September 2026 — 327 subscribers3 October 2026 — 326 subscribers13 October 2026 — 321 subscribers20 October 2026 — 314 subscribers2 November 2026 — 309 subscribers10 November 2026 — 307 subscribers7 August 202610 November 2026
13 measurements spanning 95 days, net -9. 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 304–331 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 14:37307-2
2 Nov 2026, 17:46309-5
20 Oct 2026, 03:51314-7
13 Oct 2026, 21:45321-5
3 Oct 2026, 18:55326-1
18 Sept 2026, 22:40327-1
9 Sept 2026, 14:38328+1
31 Aug 2026, 12:46327+6
23 Aug 2026, 20:45321+5
16 Aug 2026, 04:27316-1
8 Aug 2026, 07:33317no change
8 Aug 2026, 02:20317+1
7 Aug 2026, 18:00316first reading

Engagement

20 posts held, back to 31 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 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 07:16 UTC1 viewsread 8 August 2026

Бесплатные места от Клуба перевозчиков 14.08 15:00 Нарва- Таллин 16.08 ~7:00 Таллин- Нарва @artemvputi Купим места у водителей Наш канал https://t.me/fair_drivers

8 Aug 2026, 06:53 UTC1 viewsread 8 August 2026

8.08 22:20 Пермь- Екатеринбург (Аэропорт). Есть места. Беру посылки @nightdriverivan

8 Aug 2026, 05:45 UTC3 viewsread 8 August 2026

9.08 11:00 Гознак Пермь- Казань места по 4000р, есть 2 места. Возьму посылки, животных. Минивэн (5 мест) +79026398717 Ольга

7 Aug 2026, 07:49 UTC6 viewsread 8 August 2026

🌞Наши проекты без поездок Гиды и экскурсии 🚶 @vbalt Аренда недвижимости 🏠 @gdekv Пассажиры для водителей 👨‍👩‍👦‍👦 @nevodi Учись и учи! 👩‍🏫 @izik5 О собаках 🐺@nasobaku Живи долго! 🩺 @vamdoktor Сводки с границ 👁 @namgranica Есть предложения? Пиши - @bokser213

7 Aug 2026, 07:34 UTC8 viewsread 8 August 2026

9.08 13:30 Устик- Тавра- Екатеринбург есть места до Южного и жд 19:00 Екатеринбург- Тавра-Устик Заеду в соседние деревни. Посылки +79093450472 ват, макс. телег +79674586471

6 Aug 2026, 07:13 UTC12 viewsread 8 August 2026

Поездки на канале размещаются бесплатно 1 раз в четыре дня! При соблюдении 5 условий: 1. Дата 2. Время 3. Маршрут 4. Цена 5. Способ связи Небольшой комментарий приветствуется! Достоверная информация помечена 🚩 Платные объявления и дубли 500 руб/сутки и помечены 🔴. Все поездки, истории, новости и пожелания присылайте @bokser213

5 Aug 2026, 12:56 UTC16 viewsread 8 August 2026

24.08 Екатеринбург - Пермь - Ижевск - Глазов 31.08 Глазов - Пермь - Екатеринбург Беру посылки @nkt_ks

5 Aug 2026, 07:04 UTC19 viewsread 8 August 2026

🔴 Клуб перевозчиков купит у водителей места @artemvputi Наш канал @fair_drivers Возить с нами - выгодно! Не возите воздух.

4 Aug 2026, 07:53 UTC20 viewsread 8 August 2026

06.08 ~14:30 Пермь- Соликамск. Есть места, возьму посылки 7.08 ~14:00 Пермь- Соликамск есть места возьму посылки +79824787383

4 Aug 2026, 07:13 UTC22 viewsread 8 August 2026

Сеть каналов по поездкам 🚗 Юг России @sssro2 🚗 Приуралье и Пермь @permeka 🚗 По Германии @RFvFRG 🚗 Крым @vamkrm 🚗 Калининград @vklgr - много поездок 👍 🚗 Минск и РБ @kminsku 🚗 Спб и окрестности @vezdespb - много поездок 👍 🚗 Латвия @izrigi - много поездок 👍 🚗 Грузия @vgruzii 🚗 Чехия @vpragu 🚗 Москва @kmoskve - много поездок 👍 🚗 Псков и окрестности @vpskv 🚗 Польша @izpol 🚗 Литва @vvilnus 🚗 Эстония @vtalin 🚖 чат водителей…

3 Aug 2026, 18:25 UTC22 viewsread 8 August 2026

4.08 9:00 Пермь - Екатеринбург 16:00 Екатеринбург - Пермь 1700 р - место. Возьму посылки, животных. Минивэн (6 мест) +79026398717

3 Aug 2026, 18:23 UTC24 viewsread 8 August 2026

Подайте бесплатно объявление и водитель сам позвонит https://t.me/nevodi/8284

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

Mentions

Named by 6 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.

Names

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

Клуб верифицированных перевозчиков Европа - Россия
@fair_drivers · 1,385
3 posts
Сводка с границ
@namgranica · 337
3 posts
Попутчики, посылки, пассажиры для водителей @nevodi
@nevodi · 2,516
3 posts
Краткосрочная аренда жилья
@gdekv · 235
2 posts
Обучающий лингвистический канал МоСаРТ
@izik5 · 201
2 posts
Канал заводчиков собак. МоСаРТ
@nasobaku · 115
2 posts
Живи долго! Канал о новостях и достижениях медицины. И хороших врачах
@vamdoktor · 29
2 posts
Экскурсии - обзорные, авторские, фестивали, мероприятия
@vbalt · 217
2 posts
В Польшу! Поездки и попутчики Варшава, Гданьск и соседние страны
@izpol · 491
1 post
Попутчики, поездки, водители Москва, Спб, Рига, Таллин, Минск, Вильнюс
@izrigi · 5,365
1 post
К Минску! Попутчики и поездки Вильнюс, Рига, Москва, Варшава и обратно
@kminsku · 1,933
1 post
К Москве Поездки трансферы водители попутчики. По России и Европе
@kmoskve · 1,136
1 post
Чат водителей, попутчиков. Посылки, пассажиры для водителей
@otvezut · 3,517
1 post
Поездки по Германии, Польше, России. Берлин Бонн Гданьск Калининград
@RFvFRG · 81
1 post
В Краснодар! Попутчики, водители и поездки. Юг России
@sssro2 · 372
1 post
Вам Крым! Поездки, водители и попутчики
@vamkrm · 439
1 post
Питер везде! Поездки, трансферы и попутчики - Петербург Таллин Хельсинки Рига Москва
@vezdespb · 1,316
1 post
Поездки, попутчики, трансферы и водители по Грузии, Армении, Тбилиси Батуми Ереван Кутаиси
@vgruzii · 455
1 post
В Калининград! Попутчики, трансферы и поездки в Польшу Литву Германию Латвию Россию
@vklgr · 1,633
1 post
Поездки и попутчики Прага, Чехия, Германия, Австрия
@vpragu · 304
1 post
На Псков! Авторский канал о поездках трансферах в СПб Москву Ригу Таллин и Псков. Граница Шумилкино- Luhamaa Koidula
@vpskv · 1,389
1 post
Нарва Ивангород Таллин Тарту - Эстония попутчики, водители, пассажиры, поездки, трансферы
@vtalin · 834
1 post
В Литву. Поездки, трансферы и попутчики по Литве, Латвии, России, Польше
@vvilnus · 885
1 post

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

“На Пермь! Попутчики, поездки Екатеринбург, Челябинск, Казань” (@permeka), 307 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/permeka.

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.