Telegram RegisterThe public register of Telegram
Telegram profile photo for Р1: Premium. Вакансии 1С для Синьоров

Channel

Р1: Premium. Вакансии 1С для Синьоров

@joboneC

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

20,287subscribers

+459 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001284368373
TypeChannel
Username@joboneC
DescriptionВакансии 1С для синьоров № 7322196714 https://t.me/r1job - для джунов и мидлов https://t.me/r1_Management_job - для менеджеров Правила каналов: https://t.me/joboneC/11865 По всем вопросам: @KaterinaCORS
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/joboneC

Topic

Job listings — 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 10 September 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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@r1job/288721 Jul 2026, 09:32 UTC@joboneC/12024 · this entry22 Jul 2026, 08:46 UTC1.0023 hours
@joboneC/12037 · this entry18 Aug 2026, 06:55 UTC@r1job/290218 Aug 2026, 06:56 UTC1.0072 seconds
@joboneC/12043 · this entry24 Aug 2026, 08:04 UTC@r1job/290724 Aug 2026, 08:05 UTC1.00under a minute
@joboneC/12081 · this entry21 Oct 2026, 09:31 UTC@r1job/292921 Oct 2026, 09:32 UTC1.00under a minute
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
@r1job8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–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. 1 of the 2 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 58 comparable posts for this entry, running 8 July 2026 to 11 November 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 2 channels, the one whose matching posts we hold earliest is @joboneC — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 12 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 2 registered channels linked by matching posts. 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

19,82820,28720,057.56 August 202612 November 2026
61 measurements spanning 98 days, net +459. 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 19,759–20,356 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
12 Nov 2026, 07:2020,287+12
10 Nov 2026, 03:4520,275+12
8 Nov 2026, 21:0920,263-3
7 Nov 2026, 13:4420,266+2
6 Nov 2026, 13:4920,264+20
5 Nov 2026, 12:1620,244+2
4 Nov 2026, 11:5620,242+2
3 Nov 2026, 12:1120,240+2
2 Nov 2026, 15:2820,238+12
1 Nov 2026, 14:0920,226-3
31 Oct 2026, 11:2820,229+2
30 Oct 2026, 13:3520,227-5
29 Oct 2026, 10:0920,232+5
28 Oct 2026, 08:5620,227+11
27 Oct 2026, 05:2020,216+9
26 Oct 2026, 07:3520,207+3
25 Oct 2026, 04:1820,204+7
24 Oct 2026, 04:1620,197+10
23 Oct 2026, 06:3120,187+4
22 Oct 2026, 07:0120,183first reading

Engagement

59 posts held, back to 8 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 78 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 20,287 subscribers
Avg views / post
5,190
24 posts measured
Reaction rate
0.19%
reactions ÷ views · ER floor
Posts in window
24
of 59 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 12 November 2026
Posts held59 (8 July 2026 – 12 November 2026)
Views total124,580
Reactions total237
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 16:31 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
≈7,680
Videos
≈138
Links
≈3,810

Lifetime counters from Telegram’s own channel header, read 12 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
40s
Average length
40s

Measured directly from 1 video 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

582 reactions across 59 posts, in 7 distinct kinds. The most used accounts for 41.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👀24041.2%
❤14825.4%
🔥8915.3%
👍8714.9%
custom 543187885044953345591.55%
✍81.37%
🙏10.172%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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

Measured over the 59 most recent posts we hold, published 8 July 2026 to 12 November 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: 2 of 24 posts held from the last 30 days (8.33%) 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).

12 Nov 2026, 07:12 UTC≈2,330 views21 reactionsread 12 November 2026

💃 Прилетела крутая живая вакансия в команду ERP IT на позицию Руководителя проектного офиса 1С в направление «Пищевое производство», оно развивается давно и успешно, разработан собственный продукт, который пользуется серьёзным спросом на рынке. Поэтому проектов становится всё больше и направлению нужно усиление. ERP-IT ищет Руководителя проектного офиса 1С, очень желательно с экспертизой в пищевом производстве. ✔️E…

❤11👀9🔥1

11 Nov 2026, 11:36 UTC≈2,940 views30 reactionsread 12 November 2026
Photo

#вакансия #1C #developer #офис Категория 200-300 Вилка - 200-230 Net Локация - офис, Москва Контакты: saltanat_adil Требования: Опыт работы в роли разработчика 1С от 4х лет (важен опыт работы с конфигурацией 1С ЗУП); Опыт работы с конфигурациями 1С:УПП, 1С:ERP. Участие в проектах перехода с 1С:УПП на 1С:ERP.

👀29🔥1

11 Nov 2026, 10:28 UTC≈3,020 views2 reactionsread 12 November 2026
Photo

🎉 Наконец-то 11.11! 11-12 ноября объявляем временем инвестиций в знания и будущую карьеру. Покупайте курсы, мини-курсы, тренинги со скидкой. ➡️ Курсы −20% ➡️ Тренинги и мини-курсы −30% Промокод SALE_11.11 уже действует и будет активен до конца 12 ноября. Выбирайте свое обучение: https://clck.ru/3WwF2r Чтобы получить скидку, введите промокод SALE_11.11 при оформлении заказа сегодня или завтра.

custom 54318788504495334552

9 Nov 2026, 09:13 UTC≈3,850 views13 reactionsread 12 November 2026
Photo

Ведущий Консультант 1С (Оперативный учет) Крок Формат: Full time, гибрид с командировками на Дальний Восток (2 недели в офисе, 2 недели удаленно) Вилка: 300-450 (командировки компенсируем) Проект до апреля 2027г., с возможностью продления Система: 1С: ERP УХ Описание проекта: Проект перехода с SAP на 1С:ERP УХ ❗️Требования к специалисту: - Опыт участия в крупных проектах автоматизации и внедрения оперативного учет…

🔥7👍5❤1

6 Nov 2026, 10:17 UTC≈5,050 views9 reactionsread 12 November 2026
Photo

💼 Ведущий консультант 1С:ERP УХ — ТМЦ / РСБУ 🏢 Вератис Категория: 400+ Вилка: 400 000 – 500 000 ₽ на руки 📍 Гибрид: 2–3 дня в неделю в офисе (Москва, м. Шаболовская), неделя в месяц — удалённо из регионов 🕘 Full time, 9:00–18:00 МСК 📋 Оформление: СЗ / ИП / ГПХ ⏳ Проект на 7 месяцев, возможна пролонгация Проект: крупное госпредприятие переводит финансовый контур с 1С:УПП на 1С:ERP УХ. Требования: – ведущий консу…

🔥6❤2✍1

5 Nov 2026, 08:56 UTC≈5,230 views13 reactionsread 12 November 2026
Photo

Разработчик 1С:ЗУП Компания Циан — крупнейший в России сервис для поиска недвижимости. Формат: полная занятость, удалённо/гибрид Категория: 200-300 Задачи, которые нужно решать: — Разрабатывать и дорабатывать 1С:ЗУП 3.0 под бизнес-требования, в основном в области Compensation & Benefits: расчёт ФОТ, премирование, HR-метрики и другие процессы. — Развивать функциональность управленческого и регламентированного учёта в…

👀8❤3👍2

5 Nov 2026, 06:34 UTC≈4,550 views3 reactionsread 12 November 2026
Photo

💼 Функциональный консультант / архитектор 1С:ТОиР КОРП 🏢 Вератис Категория: 300-400 Вилка: 340 000 – 395 000 ₽ на руки 📍 Удалённо + командировки на площадки (Березники, Пермь, Кирово-Чепецк, Воскресенск) по графику проекта 🕘 Full time, 9:00–18:00 МСК 📋 Оформление: СЗ / ИП / ГПХ ⏳ Проект до 30.06.2028 Проект: производство минеральных удобрений, 4 филиала. Методология и нормализация НСИ ТОиР, техническое проектиро…

❤3

3 Nov 2026, 12:18 UTC≈4,980 views1 reactionsread 12 November 2026
Photo

Ищем Аналитика 1С Компания: itvolna.tech Категория: 250–350 Формат: удалённый (работа по МСК) Занятость: полная Локация: любая Оформление: ИП (российское) / ООО ЗП: 260 000–280 000 на руки Требования: Ищем специалистов с опытом работы в следующих направлениях: Опыт работы с основными средствами (ОС) и нематериальными активами (НМА). Глубокое понимание бухгалтерского (БУ) и налогового учёта (НУ). Знание временных…

🔥1

3 Nov 2026, 10:38 UTC≈4,370 views2 reactionsread 12 November 2026
Photo

Вакансия: Консультант/Аналитик 1С Вилка: 250–300 тыс. Локация: удалённая (РФ), гражданство РФ От нас: - Классные, развивающие и масштабные задачи - Широкий спектр задач: от доработки типовых конфигураций до развития сложных, уникальных решений на базе платформы 1С - Задачи без бюрократии, быстрый оффер на отличных условиях; не франчайзи - Договор: ИП Ожидаем от кандидата: Общие требования - Опыт работы в направле…

❤1🔥1

30 Oct 2026, 11:10 UTC≈5,870 views7 reactionsread 12 November 2026
Photo

Вакансия: Функциональный архитектор ERP (регучет) Локация: офис Москва, гибрид Компания: КРОК Зарплатная вилка: От 350 тыс. net (оклад) Оформление: Штат 🔍 Чем предстоит заниматься: 💥 Участие в проектах по внедрению продуктов 1С в роли функционального архитектора; 💥 Проведение обследования; Проектирование! 💥 Сбор и анализ требований к системе; 💥 Формирование и согласование проектной и пользовательской документации;…

❤5👍2

29 Oct 2026, 08:02 UTC≈5,800 views2 reactionsread 12 November 2026
Photo

Рынок 1С меняется, а вместе с ним — требования к специалистам. Опыт, который ещё несколько лет назад обеспечивал стабильную работу, сегодня не всегда гарантирует востребованность. 30 октября в 16:00 МСК на CORS Пятнице №17 поговорим о том, как развиваться в профессии, усиливать свои позиции на рынке труда и выбирать обучение, которое действительно приносит пользу. Вместе с HR-экспертом Людмилой Шароуховой обсудим к…

👀1🔥1

29 Oct 2026, 06:54 UTC≈6,290 views42 reactionsread 12 November 2026
Photo

💼 FullStack-разработчик 1С + React 🏢 Вератис Категория: 200-300 Вилка: 245 000 – 285 000 ₽ на руки 📍 Удалённо, строго РФ, налоговый резидент РФ 🕘 Full time, 10:00–19:00 МСК 📋 Оформление: СЗ / ИП / ГПХ ⏳ Проект на 6 месяцев, возможна пролонгация Проект ВК: система на платформе 1С с кастомным веб-интерфейсом. Задачи: формирование постановок от бизнеса, разработка серверной части на 1С и веб-интерфейса на React/TS, со…

👀39✍1❤1custom 54318788504495334551

Showing the 12 most recent of 59 posts we hold for @joboneC. 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 2 posts on @joboneC 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
5 November 2026
Most recent seen missing
5 November 2026
Median time before seen missing
31 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Р1: Jobs. Вакансии 1С для джунов и мидлов
@r1job · 9,557
#1
Желтый клуб
@yellowclub_official · 11,473
#2
1С Работа (вакансии в штат и аутстаффинг)
@esres_1c · 12,531
#3
Заговори с Охотницей
@talktoann · 3,456
#4
1C Company
@company1c · 6,466
#5
ЕстьРесурс (решаем 1С задачи)
@esres_1Coutstaff · 2,789
#6
Заметки 1Сницы. Анастасия Синякова
@yellow_note · 5,951
#7
Жёлтый чайник 1С (Черненко Виталий)
@JuniorOneS · 5,311
#8
Александр Кунташов — про 1С и не только
@kuntashov_devnotes · 2,575
#9
1C Lite
@lite1C · 11,267
#10
Школа проектного специалиста
@techitpm · 2,968
#11
OpenYellow | Open-source и 1С:Предприятие
@OpenYellowProject · 2,112
#12
Гайды по 1С
@academy_1c · 9,098
#13
Е.БУДНИ программиста 1С | Роман Чумадин
@e_budni_programmer · 6,227
#14
Минцифры России
@mintsifry · 232,323
#15
1C программист
@odin1C_rus · 7,812
#16
Жёлтая ржомба (1С Мемы)
@app1c · 2,273
#17
Заметки Честного HR #ЗЧHR
@HROrekhova · 311
#18
Вакансии 1С и Bitrix-разработчиков
@bitrix_1c_job · 2,863
#19
INFOSTART A&PM EVENT
@analysis_pm_channel · 1,889
#20
НиколAI 1С: от джуна до мидла
@razrab1c · 7,179
#21
Первый Бит
@bit_it_official · 4,515
#22
1С Работа Вакансии
@v1c_rabota · 1,540
#23
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 40,667
#24
1С:Community
@KORUScommunity_1c · 1,177
#25
1С Stars: Вакансии, работа от FastCode 1C
@FastCodeCareer · 852
#26
INFOSTART Support
@infostart_support · 1,483
#27
Вакансии, резюме, менторинг, поиск компетенций 1С 💡
@resume1c · 899
#28
CROC IT 1С
@CROC_1C · 701
#29
Владимир Харин - Просто Pro 1С
@prosto_pro1c · 4,869
#30
1С для торговли
@torg1c_ru · 3,138
#31
Koderline 1С - Платформа
@koderlineplatforma1C · 939
#32
Лаборатория цифровых решений
@eprlab · 708
#33
Старт в 1С: вакансии и резюме без опыта
@job_for_juniors · 1,433
#34
1С:Предприятие 8
@onecv8 · 12,551
#35
1C:ERP
@ERP_1C_official · 6,741
#36
FastCode 1С
@FastCodeIM · 9,950
#37
Подготовка к собеседованиям по 1С и задачи по программированию.
@sobes1c · 3,105
#38
wiki 1С + AI. База знаний, мысли и заметки.
@wiki1c · 4,887
#39
Дмитрий Котов | 1С Заметки
@top_1c · 8,717
#40
WiseAdvice-IT - новости из мира 1С
@WiseAdviceIT · 4,029
#41
Хатка Бобра
@evilbeaverHouse · 1,261
#42
ИНФОСТАРТ Журнал
@infostarttrend · 920
#43
1Cnik
@by_1cnik · 6,267
#44
Никита Арипов | 1С, DevExp
@AriN1C · 2,916
#45
1С PRO: Интеграция + ИИ | NIZAMOV.SCHOOL
@nizamov_studio_1c · 5,446
#46
1С и AI, полезные инструменты и сервисы, стандарты и паттерны
@usefultools1c · 2,284
#47
Практика сложного кода
@quazareline · 3,251
#48
1С СППР Система Проектирования Прикладных Решений
@SPPR1c · 2,084
#49
Зазеркалье 1С
@wonderland_1C · 4,788
#50
Клуб питерских одинэсников
@therapy_1c · 1,574
#51
1С+web+mobile+etc
@web_mobile_1C · 1,616
#52
INFOSTART Enterprise
@infostart_enterprise · 2,061
#53
Мир 1С (Сергей Сыпачев)
@sergsyp · 1,646
#54
Игорь Апресов | Radio Ingvar
@radio_ingvar · 2,326
#55
Канал. Учебный центр №1 фирмы 1С 📣
@uc_1c · 6,827
#56
1С-Рарус Официальный
@rarus_official · 2,836
#57
Простая логика. Канал Пластинина Артема
@simplelogic · 942
#58
DevOps в 1с
@DevOps_onec · 781
#59
Бояршинов из Корады
@corada · 845
#60
Знакомый 1С-ник
@znak1c · 4,449
#61
OneSCast | 1С Предприятие | AI
@OneSCast · 4,649
#62
Фирма 1С Управление проектами (канал)
@Projectmanagement1C · 1,198
#63
В 1С после 40 или как стать Непрограммистом.
@vitposle40 · 1,119
#64
Клуб руководителей проектов на Инфостарте
@pm_infostart · 700
#65
CIO: канал IT руководителей
@cio_channel · 10,892
#66
Programmer & IT Memes
@itmemes · 121,889
#67
Алексей Петухов из Programming Store
@ProSto_CEO · 414
#68
Желтый юмор
@yellow_humor · 1,249
#69
Developers Community Partners
@DevCom_Partners · 1,025
#70
ЧОТКИЙ 1С-НИК (손준형 АКА 1C: Middle East)
@chotkiy_1Cnik · 441
#71
1С ДЛЯ БИЗНЕСА
@giga_1c · 679
#72
BcluB.dev
@bclub_dev · 659
#73
Программирование в 1С для всех
@Programming1CNizamutdinov · 6,488
#74
Шишкина И.С.: об управлении проектами/продуктами/ИТ
@neprostoidea · 1,204
#75
Другой 1С
@another1C · 1,260
#76
1С:Документооборот | 1С:Архив
@doc8_1c · 3,348
#77
1С:Лекторий
@lector_1c · 12,192
#78
БИТ.ФИНАНС | Автоматизация управленческого учета
@bit_finance_channel · 1,104
#79
1CUnlimited
@Chat1CUnlimited · 794
#80
1С Обработки
@free_1c · 6,269
#81
Мемы 1С и около
@memoshnaya1C · 7,611
#82
Никита Федькин - мысли, заметки, анонсы
@nixel2007_thoughts · 2,876
#83
Раньше всех. Ну почти.
@bbbreaking · 1,975,436
#84
Будни питониста
@leontyev_ilya · 3,965
#85
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,662,248
#86
Проект СППР+ [Sk]
@sppr_plus · 312
#87
Инфостарт Лента
@infostartnew · 411
#88
TurboConf 1С
@turboconf · 1,722
#89
Р1: Management. Вакансии для менеджеров 1С
@r1_Management_job · 2,889
#90
Yaplakal.com
@yaplakal · 419,647
#91

Read from Telegram’s recommendation API, most recently 29 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Бухучет, налоги, 1С
@buhru · 35,187
Telegram ranks this channel #19 of 95 here — alongside 94 others — read 2 September 2026
Бухэксперт
@buhexpert8 · 75,272
Telegram ranks this channel #87 of 94 here — alongside 93 others — read 19 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Р1: Premium. Вакансии 1С для Синьоров” (@joboneC), 20,287 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/joboneC.

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.