Telegram RegisterThe public register of Telegram
Telegram profile photo for Услуги Казань Шабашка

Channel

Услуги Казань Шабашка

@uslugikazan16

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

2,581subscribers

-25 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-1003261609256
TypeChannel
Username@uslugikazan16
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held12
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/uslugikazan16

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 99% 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 2 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
@rabota016/20255 Aug 2026, 07:37 UTC@uslugikazan16/3380 · this entry6 Aug 2026, 10:20 UTC1.0027 hours
@rabota016/20275 Aug 2026, 08:05 UTC@uslugikazan16/3378 · this entry6 Aug 2026, 08:46 UTC1.0025 hours
@rabota016/20305 Aug 2026, 12:28 UTC@uslugikazan16/3388 · this entry7 Aug 2026, 07:37 UTC1.0043 hours
@rabota016/20315 Aug 2026, 14:38 UTC@uslugikazan16/3382 · this entry6 Aug 2026, 15:16 UTC1.0025 hours
@uslugikazan16/3373 · this entry6 Aug 2026, 05:56 UTC@rabota016/20326 Aug 2026, 05:56 UTC1.00under a minute
@rabota016/20336 Aug 2026, 07:03 UTC@uslugikazan16/3375 · this entry6 Aug 2026, 07:03 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@rabota01610 (8/8 hand-verifiable sample passed)1.0012 hours@rabota016 (64)
@kznrabotatut10 (8/8 hand-verifiable sample passed)1.00under a minute@kznrabotatut (91)

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. 15 of the 15 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 11 comparable posts for this entry, running 6 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 3, the earliest publisher we hold is @rabota016. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 7 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 2 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

2,5802,6062,5937 August 2026 — 2,606 subscribers7 August 2026 — 2,606 subscribers11 August 2026 — 2,604 subscribers14 August 2026 — 2,603 subscribers18 August 2026 — 2,599 subscribers21 August 2026 — 2,601 subscribers24 August 2026 — 2,597 subscribers27 August 2026 — 2,594 subscribers30 August 2026 — 2,592 subscribers2 September 2026 — 2,583 subscribers7 September 2026 — 2,580 subscribers11 September 2026 — 2,581 subscribers2,5817 August 202611 September 2026
12 measurements spanning 35 days, net -25. 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 2,576–2,610 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 18:172,581+1
7 Sept 2026, 14:372,580-3
2 Sept 2026, 08:452,583-9
30 Aug 2026, 01:132,592-2
27 Aug 2026, 11:132,594-3
24 Aug 2026, 08:072,597-4
21 Aug 2026, 01:382,601+2
18 Aug 2026, 03:422,599-4
14 Aug 2026, 22:282,603-1
11 Aug 2026, 08:222,604-2
7 Aug 2026, 17:482,606no change
7 Aug 2026, 17:382,606first reading

Engagement

20 posts held, back to 6 August 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 15:26 UTC31 viewsread 7 August 2026

❗️❗️все новые заявки сначала публикуются в нашем канале 👇👇👇 https://max.ru/kznrabota16 🚀 «Шабашка Казань» — № 1 в MAX! 👥 9 000+ участников 📈 Новые заявки каждый день Не пропусти свои возможности! 👇 https://max.ru/kznrabota16

7 Aug 2026, 10:28 UTC43 viewsread 7 August 2026

Заявка Штроба стяжки также кирпича За собой все собирать в мешки Нужны 2 людей с опытом работы Инструмент предоставим Оплата за обьем Также расмотрим на постоянной основе, работы много Звонить по номеру или писать в макс, Закрыто 🔐

7 Aug 2026, 07:37 UTC44 viewsread 7 August 2026
Photo

⚡ Вакансия: Сборщик литиевых аккумуляторов 🔋 Компания «Апгрейд Стафф» приглашает сотрудников на производство в с. Столбище! ❗️Начало работы 13.08.26, сейчас набираем в резерв! (СНГ, РФ ) 💰 Оплата: 5 000 ₽ за смену (выплаты раз в неделю). 📅 График: 5/2, 6/1 или 7/0 (смены с 08:00 до 20:00). 🚌 Трансфер: бесплатная вахта от м. «Проспект Победы» (Казань). 🛠 Что делать: Сборка аккумуляторов по техкартам. Пайка, нарезка и

7 Aug 2026, 06:47 UTC47 viewsread 7 August 2026

Всем доброго времени. Срочно нужен михонизатор на К744 ЗП договорная. Высокогорский район. 89083428004 Линар

6 Aug 2026, 19:00 UTC74 viewsread 7 August 2026

Здравствуйте! В Тюлячи на деревообработку требуется работник. Желателен опыт работы на ленточной пилораме или станках. В день от 5 до 10 тыс рублей. Тел 8 (939) 393-56-59

6 Aug 2026, 17:25 UTC82 viewsread 7 August 2026

Требуется продавец в магазин аккумуляторов.Новониколаевка. Требования: работа с пк с1, маркет приветствуется, знание авто, умение заменить акб. Писать в Макс 89656104010

6 Aug 2026, 15:16 UTC72 viewsread 7 August 2026

❗️❗️все новые заявки сначала публикуются в нашем канале 👇👇👇 https://max.ru/kznrabota16 🚀 «Шабашка Казань» — № 1 в MAX! 👥 9 000+ участников 📈 Новые заявки каждый день Не пропусти свои возможности! 👇 https://max.ru/kznrabota16

Showing the 12 most recent of 20 posts we hold for @uslugikazan16. 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“Услуги Казань Шабашка” (@uslugikazan16), 2,581 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/uslugikazan16.

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.