Telegram RegisterThe public register of Telegram
Telegram profile photo for Удаленная работа

Channel

Удаленная работа

@vakansii181

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Advertising · Posts · Posts recorded as deleted · Citations · Domains linked from posts · Cite this entry

39,482subscribers

-57 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001391474942
TypeChannel
Username@vakansii181
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held46
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/vakansii181

Topic

Job listings — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 word for word on 4 other registered channels. They sit inside a group of 9 channels that share the same post bodies 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@rabota_onlaynr/81403 Aug 2026, 09:00 UTC@vakansii181/9025 · this entry3 Aug 2026, 09:00 UTC1.00under a minute
@rabota_onlaynr/81433 Aug 2026, 12:01 UTC@vakansii181/9028 · this entry3 Aug 2026, 12:01 UTC1.00under a minute
@rabota_onlaynr/81443 Aug 2026, 15:05 UTC@vakansii181/9031 · this entry3 Aug 2026, 15:05 UTC1.00under a minute
@rabota_onlaynr/81454 Aug 2026, 09:00 UTC@vakansii181/9032 · this entry4 Aug 2026, 09:00 UTC1.00under a minute
@rabota_onlaynr/81474 Aug 2026, 12:01 UTC@vakansii181/9034 · this entry4 Aug 2026, 12:01 UTC1.00under a minute
@rabota_onlaynr/81484 Aug 2026, 15:01 UTC@vakansii181/9035 · this entry4 Aug 2026, 15:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@rabota_onlaynr8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–2)
@rabota_na_domue6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (5–1)
@rabota_onlaynq5 (5/5 hand-verifiable sample passed)1.00under a minute@rabota_onlaynq (5–0)
@rabota_onlayny5 (5/5 hand-verifiable sample passed)1.00under a minute@rabota_onlayny (3–2)

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. 4 of the 11 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 24 comparable posts for this entry, running 3 August 2026 to 7 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).

Across the whole group of 9, the earliest publisher we hold is @vakansii181 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

6.4 average views per post against 39,482 subscribers — an engagement rate of 0.016%. Across the 8,315 registered channels in the same cohort — 31,623–99,997 subscribers, posting mainly in Russian — the middle half sit between 5.08% and 20.8%, with a median of 10.5%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured96 of 96 published in the window (96 exact, 0 rounded by Telegram)
Views totalled615
Mature posts only0.016% over 94 posts read at least 24h after publication
Subscribers39,482 measured 5 November 2026
Cohortb31623:rus · 8,315 channels · p10 2.60% · p25 5.08% · p50 10.5% · p75 20.8% · p90 35.5%
Position in cohort0.072th percentile · 1/500 the cohort median
Uncertainty±0.073% of the figure, from Telegram’s rounding
Post languageRussian · 97.9% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_copy · clone_mutual · clone_source · err_low, last confirmed 5 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 8 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

39,48139,53939,5107 August 2026 — 39,539 subscribers7 August 2026 — 39,539 subscribers8 August 2026 — 39,538 subscribers9 August 2026 — 39,537 subscribers10 August 2026 — 39,536 subscribers12 August 2026 — 39,534 subscribers12 August 2026 — 39,533 subscribers14 August 2026 — 39,529 subscribers17 August 2026 — 39,531 subscribers18 August 2026 — 39,529 subscribers21 August 2026 — 39,528 subscribers22 August 2026 — 39,527 subscribers24 August 2026 — 39,521 subscribers28 August 2026 — 39,520 subscribers29 August 2026 — 39,518 subscribers30 August 2026 — 39,517 subscribers31 August 2026 — 39,516 subscribers1 September 2026 — 39,515 subscribers2 September 2026 — 39,514 subscribers3 September 2026 — 39,513 subscribers5 September 2026 — 39,512 subscribers8 September 2026 — 39,508 subscribers11 September 2026 — 39,505 subscribers13 September 2026 — 39,508 subscribers14 September 2026 — 39,507 subscribers16 September 2026 — 39,504 subscribers18 September 2026 — 39,501 subscribers2 October 2026 — 39,497 subscribers6 October 2026 — 39,498 subscribers11 October 2026 — 39,496 subscribers14 October 2026 — 39,497 subscribers15 October 2026 — 39,496 subscribers16 October 2026 — 39,494 subscribers18 October 2026 — 39,492 subscribers21 October 2026 — 39,494 subscribers22 October 2026 — 39,493 subscribers25 October 2026 — 39,491 subscribers27 October 2026 — 39,490 subscribers28 October 2026 — 39,487 subscribers29 October 2026 — 39,485 subscribers31 October 2026 — 39,484 subscribers1 November 2026 — 39,483 subscribers4 November 2026 — 39,481 subscribers5 November 2026 — 39,482 subscribers7 November 2026 — 39,483 subscribers8 November 2026 — 39,482 subscribers39,4827 August 20268 November 2026
46 measurements spanning 93 days, net -57. 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 39,472–39,548 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
8 Nov 2026, 11:5639,482-1
7 Nov 2026, 08:0039,483+1
5 Nov 2026, 06:2939,482+1
4 Nov 2026, 04:5539,481-2
1 Nov 2026, 08:4039,483-1
31 Oct 2026, 08:3139,484-1
29 Oct 2026, 10:4939,485-2
28 Oct 2026, 10:2039,487-3
27 Oct 2026, 11:4739,490-1
25 Oct 2026, 11:4639,491-2
22 Oct 2026, 15:1639,493-1
21 Oct 2026, 11:0639,494+2
18 Oct 2026, 03:3739,492-2
16 Oct 2026, 05:1839,494-2
15 Oct 2026, 05:2039,496-1
14 Oct 2026, 00:5539,497+1
11 Oct 2026, 02:3739,496-2
6 Oct 2026, 22:5939,498+1
2 Oct 2026, 01:1939,497-4
18 Sept 2026, 11:0139,501first reading

Engagement

426 posts held, back to 3 August 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 182 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.017%
avg views ÷ 39,482 subscribers
Avg views / post
6.5
92 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
92
of 426 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
WindowRolling 30 days · latest post in window 8 November 2026
Posts held426 (3 August 2026 – 8 November 2026)
Views total601
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 10:16 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

Video runtime
1m 09s
Average length
5s

Measured directly from 13 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.

Advertising

Ad load
9.15%
39 of 426 posts carry an ad marker
Regulatory tokens
39
posts carrying an erid · 5 distinct tokens
Median views · ads
7.0
over 39 measured posts
Median views · rest
5,000
over 363 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7G1224 September 20265 November 2026
2SDnjdDRjvV84 October 20267 November 2026
5jtCeReNwxHpfQTDve31wmc87 August 20264 November 2026
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd786 August 202622 September 2026
2W5zFHRnKXf311 October 202625 October 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 426 most recent posts we hold, published 3 August 2026 to 8 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 92 posts held from the last 30 days (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).

8 Nov 2026, 09:00 UTC3 viewsread 8 November 2026

Категорийный менеджер на маркетплейсы 150000 – 250000 RUR Обязанности: • Заказать образцы и партию. • Развивать ассортимент в новой категории. • Работа с поставщиками. Требования: • Опыт категорийным менеджером / закупщиком / product manager от 2 лет. • Подтверждённый опыт работы с конкретной категорией. • Действующая база проверенных поставщиков по... Контакты: +79676731676 Заработная плата по договоренности

7 Nov 2026, 17:02 UTC4 viewsread 8 November 2026
Advertisementerid 2SDnjdDRjvVPhoto

🏆🏆🏆🎁 Увеличил приветственный бонус до 10 000 ₽ Новым игрокам — 10 фрибетов по 1 000 ₽. Начисление автоматическое: пополнил счёт — фрибет уже у тебя. Каждый день, 10 дней подряд. 🚩 Регистрируйся и получай бонус

7 Nov 2026, 15:00 UTC3 viewsread 8 November 2026

Маркетолог ДПО Заработная плата по договоренности Обязанности: • Разработать и реализовать маркетинговую стратегию, связанную с целями бизнеса и планом продаж. • Сформировать позиционирование бренда и образовательных продуктов, контролировать единообразие... Требования: • Имеет не менее 5 лет опыта в маркетинге, в том числе опыт руководства маркетингом или ключевыми направлениями. • Работал с B... Контакты: +79344…

7 Nov 2026, 12:00 UTC4 viewsread 8 November 2026

Team Lead / РОП контакт-центра (с функцией менеджера по продажам) Заработная плата по договоренности Обязанности: • Управление командой: Координация работы двух менеджеров колл-центра, составление графиков, распределение нагрузки. Контроль качества и KPI: Прослушивание звонков, контроль соблюдения... Требования: • Опыт руководства: Опыт работы на позиции Team Lead / Супервайзера / РОПа в контакт-центре или отделе п…

7 Nov 2026, 09:05 UTC4 viewsread 8 November 2026

Менеджер колл-центра в сеть клиник Заработная плата по договоренности Обязанности: • Обработка входящих лидов: Оперативная обработка обращений из всех каналов (звонки, заявки с сайта, мессенджеры, соцсети) без потери заявок. Требования: • Опыт работы в контакт-центре или отделе продаж (желательно в сфере медицины, красоты или косметологии). • Понимание специфики направления: Опыт продаж... Контакты: +79636487325

6 Nov 2026, 15:06 UTC4 viewsread 8 November 2026

Программист 1С Заработная плата по договоренности Обязанности: • Мы ищем Программиста 1С с экспертизой в маркировке и проектировании высоконагруженных систем. Вам предстоит сопровождать полный жизненный цикл кода... Требования: • Практический опыт реализации проекта маркировки от начала до конца, будет вашим преимуществом. Знание жизненного цикла кода маркировки: эмиссия → ввод в... Контакты: +79059302889

6 Nov 2026, 12:01 UTC6 viewsread 8 November 2026

Руководитель группы (ОВиК) Заработная плата по договоренности Обязанности: • Обеспечивать высокий технический уровень решений и корректное оформление документации в соответствии с нормативами и ТЗ. • Контролировать сроки так, чтобы из... Требования: • Техническое образование (не обязательно узкопрофильное). • Опыт работы инженером‑проектировщиком от 5 лет, в том числе не менее 2 лет в... Контакты: +79645178077

6 Nov 2026, 09:01 UTC6 viewsread 8 November 2026

Менеджер по продажам и работе с клиентами в интернет магазин (без холодных звонков) 82 832 – 186 800 ₽ Обязанности: • Работать с теплой клиентской базой (входящий поток звонков). • Вести переговоры по существующей базе. • Развивать базу за счет... Требования: • У тебя есть опыт работы в активных продажах от 1 года. • Есть навыки ведения телефонных переговоров. Контакты: +79061250701

5 Nov 2026, 19:19 UTC5 viewsread 8 November 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7GVideo

💛 Подработка курьером в вашем городе — доставка заказов Яндекс Еды и Яндекс Лавки Набор ведёт официальный партнёр сервиса. Условия: 📍 доход до 8 500 ₽ в день, выплаты каждый день (оформление как самозанятый) 📍 график выбираете сами — слоты свободные, заказы поступают 24/7 📍 все чаевые — ваши 📍 из документов — требуется только удостоверение личности + смартфон Бонусы для курьеров сейчас: 😍 велосипед Яндекс Байк — з…

5 Nov 2026, 15:04 UTC4 viewsread 8 November 2026

Требуется Промоутер, Без опыта, Удаленная работа, График: Гибкий график, Обучение Заработная плата по договоренности Обязанности: • Средний заработок — 80 000–110 000 сом в месяц • Гибкий график — доход зависит от количества отработанных часов • Обучение и помощь на старте • Дружная команда и поддержка • Возможность развиваться и увеличивать свой заработок Требования: • Девушек от 18 лет • С приятной внешностью и х…

5 Nov 2026, 12:03 UTC7 viewsread 8 November 2026

Требуется Промоутер, Без опыта, Удаленная работа, График: Гибкий график, Обучение Заработная плата по договоренности Обязанности: • Средний заработок — 80 000–110 000 сом в месяц • Гибкий график — доход зависит от количества отработанных часов • Обучение и помощь на старте • Дружная команда и поддержка • Возможность развиваться и увеличивать свой заработок Требования: • Девушек от 18 лет • С приятной внешностью и х…

5 Nov 2026, 09:05 UTC6 viewsread 8 November 2026

Требуется Промоутер, Без опыта, Удаленная работа, График: Гибкий график, Обучение Заработная плата по договоренности Обязанности: • Средний заработок — 80 000–110 000 сом в месяц • Гибкий график — доход зависит от количества отработанных часов • Обучение и помощь на старте • Дружная команда и поддержка • Возможность развиваться и увеличивать свой заработок Требования: • Девушек от 18 лет • С приятной внешностью и х…

Showing the 12 most recent of 426 posts we hold for @vakansii181. 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 recorded as deleted after publishing

We recorded 5 posts on @vakansii181 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
21 October 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
2

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 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.

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.

Domains linked from posts

3 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

pxl.leads.suregistrable domain: leads.su10 posts · 5 August 2026 – 5 August 2026 · example post
clck.ru5 posts · 3 August 2026 – 7 August 2026 · example post
trk.ppdu.ruregistrable domain: ppdu.ru1 post · 6 August 2026 – 6 August 2026 · example post

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

“Удаленная работа” (@vakansii181), 39,482 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/vakansii181.

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.