Telegram RegisterThe public register of Telegram

Channel

Работа бухгалтером | Сочи

@vakansii_sochi2

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry

1,106subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

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

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 11 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 why it has no browse page of its own yet.

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 3 other registered channels. 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
@vakansii_sochi2/329 · this entry22 Jul 2026, 07:08 UTC@vakansii_gelendzhike/33722 Jul 2026, 09:33 UTC1.002.4 hours
@vakansii_sochi2/336 · this entry23 Jul 2026, 11:58 UTC@vakansii_gelendzhike/34423 Jul 2026, 13:02 UTC1.0065 minutes
@vakansii_gelendzhike/34223 Jul 2026, 09:31 UTC@vakansii_sochi2/337 · this entry23 Jul 2026, 13:02 UTC1.003.5 hours
@vakansii_sochi2/338 · this entry23 Jul 2026, 15:04 UTC@vakansii_gelendzhike/34523 Jul 2026, 15:04 UTC1.00under a minute
@vakansii_sochi2/340 · this entry24 Jul 2026, 09:26 UTC@vakansii_gelendzhike/34924 Jul 2026, 14:30 UTC1.005.1 hours
@vakansii_gelendzhike/34824 Jul 2026, 12:02 UTC@vakansii_sochi2/342 · this entry24 Jul 2026, 14:30 UTC1.002.5 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@vakansii_gelendzhike12 (8/8 hand-verifiable sample passed)1.002.4 hourseven
@vakansii_alagirec9 (8/8 hand-verifiable sample passed)1.004.9 hours@vakansii_alagirec (54)
@vakansii_krasnodare19 (8/8 hand-verifiable sample passed)1.002.5 hoursthis entry (54)

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 15 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 20 comparable posts for this entry, running 22 July 2026 to 25 July 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 4, the earliest publisher we hold is @vakansii_alagirec. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

1.0 average views per post against 1,106 subscribers — an engagement rate of 0.09%. Across the 54,164 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.5% and 35.6%, with a median of 20.1%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured20 of 20 published in the window (20 exact, 0 rounded by Telegram)
Views totalled20
Mature posts only0.09% over 20 posts read at least 24h after publication
Subscribers1,106 measured 10 August 2026
Cohortb1000:rus · 54,164 channels · p10 5.33% · p25 10.5% · p50 20.1% · p75 35.6% · p90 57.1%
Position in cohort0.299th percentile · 1/250 the cohort median
Uncertainty±0.261% of the figure, from Telegram’s rounding
Post languageRussian · 100.0%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_mutual · err_low, last confirmed 12 August 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 3 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

1,1061,1081,1077 August 2026 — 1,108 subscribers8 August 2026 — 1,108 subscribers10 August 2026 — 1,106 subscribers7 August 202610 August 2026
3 measurements spanning 3 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 1,106–1,108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:211,106-2
8 Aug 2026, 00:031,108no change
7 Aug 2026, 18:151,108first reading

Engagement

20 posts held, back to 22 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.09%
avg views ÷ 1,106 subscribers
Avg views / post
1.0
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 25 July 2026
Posts held20 (22 July 202625 July 2026)
Views total20
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:03 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.

Recent posts

25 Jul 2026, 16:55 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Бухгалтер-кассир Зарплата по договоренности. Обязанности: • Ведение кассового учёта (приход, расход, перемещение денежных средств) • Работа с банковскими выписками и отражение операций в 1С Требования: • Опыт работы бухгалтером приветствуется • Опыт работы в 1С - обязателен • Уверенное владение ПК и Microsoft Excel • Ответственность, внимательность и организованность Контакты: +9965

25 Jul 2026, 14:30 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Главный бухгалтер Зарплата по договоренности. Обязанности: • Ведение бухгалтерского, налогового и статистического учета • Своевременное составление и предоставление отчетности • Контроль документооборота • ОСН • Ввод приходных накладных • Учёт сырья • Контроль Требования: • Внимательность • Ответственность • Опыт работы Контакты: +375291374120

25 Jul 2026, 12:00 UTC1 viewsread 8 August 2026

Вакансия из города Ставрополь Заместитель главного бухгалтера 115000 ₽ Обязанности: • Ведение бухгалтерского учёта основные средства по группе компаний (4 юридических лица) • Подготовка и сдача всей необходимой отчётности (статистическая, налоговая, таможенная) Требования: • Высшее экономическое (бухгалтерский учет, анализ и аудит, финансы и кредит, налоги и налогообложение) образование • Релевантный опыт работы н

25 Jul 2026, 09:32 UTC1 viewsread 8 August 2026

Вакансия из города Краснодар Бухгалтер по заработной плате Зарплата по договоренности. Обязанности: • Расчёт отпускных, листов нетрудоспособности, компенсации отпуска при увольнении и т.д. • Оформление вычетов по НДФЛ для сотрудников. • Прием и контроль... Требования: • Стаж работы не менее 1 года в 1С.ЗУП. • Знание всех систем оплат труда. • Опыт подготовки и сдачи отчетности в СФР... Контакты: hh@rospromtorg.co

25 Jul 2026, 07:02 UTC1 viewsread 8 August 2026

Вакансия из города Краснодар Бухгалтер-кассир 61500 ₽ Обязанности: • Работа с кассовым аппаратом, приём наличных д/с • Ведение кассовой книги • Заполнение журнала кассира - операциониста • Ведение первичной документации Требования: • Образование не ниже среднего профессионального • Опыт работы на аналогичной позиции (от 1 года) • Уверенный пользователь ПК (пакет программ Microsoft Office... Контакты: +880

24 Jul 2026, 16:59 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Главный бухгалтер 31000 KGS Обязанности: • Ведение бухгалтерского учета и отчетности согласно законодательству • Контроль правильности оформления первичных документов • Подготовка и сдача налоговой отчетности • Взаимодействие с налоговыми... Требования: • Высшее экономическое образование • Знание кыргызского и русского языков • Пунктуальность, дисциплинированность и ответственность •

24 Jul 2026, 14:30 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Бухгалтер Зарплата по договоренности. Обязанности: • Ведение бухгалтерского и налогового учёта ИП и ОсОО • Расчёт налогов: единый налог (4% безнал / 6% наличка), НДС 12% для плательщиков... Требования: • Знание Налогового кодекса КР и порядка сдачи отчётности • Опыт ведения ИП/ОсОО на разных налоговых режимах • Уверенная работа с ЭСФ Контакты: +996551121544

24 Jul 2026, 12:02 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Бухгалтер по расчету заработной платы Зарплата по договоренности. Обязанности: • Расчет и начисление заработной платы сотрудникам компании • Статистическая отчетность по заработной плате • Проверка и проведение авансовых отчётов • Поставки из стран... Требования: • Опыт работы бухгалтером по заработной плате или на соответствующих участках • Знание бухгалтерского учёта • Опыт работы

24 Jul 2026, 09:26 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Бухгалтер - калькулятор Зарплата по договоренности. Обязанности: • Ведение, расчёт калькуляций и контроль себестоимости • Ведение первичной документации • Взаимодействие с Шеф-поваром и Старшим барменом • Работа с программой Iiko... Требования: • Высшее/среднее-специальное экономическое или бухгалтерское образование • Опыт работы бухгалтером-калькулятором в общепите от 2 лет • Уверен

24 Jul 2026, 07:01 UTC1 viewsread 8 August 2026

Вакансия из города Краснодар Главный бухгалтер 150000 ₽ Обязанности: • Ведение бухгалтерского учета, налогового учета • Расчет НДС, Прибыль • Оформление прием/увольнение персонала • Сдача отчетности • Подготовка отчетов руководителю • Сдача отчетности во... Требования: • Знание НК, ПБУ • Умение работать с 1С Предприятием, 1С УТ, Excel • Опыт прохождения проверок обязателен Контакты: ruslan@yakubov.pro

23 Jul 2026, 15:04 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Заместитель главного бухгалтера (по инвестиционной и финансовой работе) Зарплата по договоренности. Обязанности: • Контроль отражения в бухгалтерском учете основных средств, нематериальных активов, строительства объектов • Организация и контроль проведения инвентаризаций • Контроль документов по проведению... Требования: • Опыт работы не менее 3-х лет с аналогичными обязанностями • Р

23 Jul 2026, 13:02 UTC1 viewsread 8 August 2026

Вакансия из города Брюховецкая Бухгалтер (Главный бухгалтер) 2000 BYR Обязанности: • Подготовка, формирование и подача отчетной документации: ПУ-2, ПУ-3, статистическая отчетность, баланс • Формирование и отправка в банк платежных поручений Требования: • Наличие высшего профильного образования • Опыт работы в ОСН и УСН от 3-х лет • Опыт работы и знание 1С Контакты: +375291048787

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

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

“Работа бухгалтером | Сочи” (@vakansii_sochi2), 1,106 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/vakansii_sochi2.

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.