Telegram RegisterThe public register of Telegram
Telegram profile photo for Работа в Париже 🇫🇷

Channel

Работа в Париже 🇫🇷

@travailler_a_paris

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

1,525subscribers

+190 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003144435149
TypeChannel
Username@travailler_a_paris
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/travailler_a_paris

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 1 other registered channel. 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
@work_france/94415 Jul 2026, 06:56 UTC@travailler_a_paris/277 · this entry15 Jul 2026, 06:56 UTC1.00under a minute
@work_france/95318 Jul 2026, 09:10 UTC@travailler_a_paris/285 · this entry18 Jul 2026, 09:33 UTC0.9823 minutes
@work_france/94616 Jul 2026, 08:39 UTC@travailler_a_paris/279 · this entry16 Jul 2026, 08:39 UTC0.98under a minute
@work_france/97027 Jul 2026, 19:02 UTC@travailler_a_paris/303 · this entry27 Jul 2026, 19:02 UTC0.96under a minute
@work_france/94816 Jul 2026, 10:55 UTC@travailler_a_paris/281 · this entry16 Jul 2026, 11:04 UTC0.9410 minutes
@work_france/95921 Jul 2026, 07:25 UTC@travailler_a_paris/291 · this entry21 Jul 2026, 07:25 UTC0.91under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@work_france6 (6/6 hand-verifiable sample passed)0.96under a minute@work_france (6–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 6 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 11 July 2026 to 1 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 2, the earliest publisher we hold is @work_france. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 6 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 1 other registered channel, 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,3321,5251,428.56 August 2026 — 1,335 subscribers6 August 2026 — 1,335 subscribers9 August 2026 — 1,336 subscribers12 August 2026 — 1,332 subscribers16 August 2026 — 1,365 subscribers19 August 2026 — 1,378 subscribers22 August 2026 — 1,407 subscribers26 August 2026 — 1,424 subscribers29 August 2026 — 1,423 subscribers1 September 2026 — 1,424 subscribers4 September 2026 — 1,456 subscribers9 September 2026 — 1,465 subscribers13 September 2026 — 1,496 subscribers17 September 2026 — 1,499 subscribers25 September 2026 — 1,525 subscribers6 August 202625 September 2026
15 measurements spanning 50 days, net +190. 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,303–1,554 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 06:571,525+26
17 Sept 2026, 08:001,499+3
13 Sept 2026, 11:361,496+31
9 Sept 2026, 19:141,465+9
4 Sept 2026, 14:001,456+32
1 Sept 2026, 01:351,424+1
29 Aug 2026, 10:281,423-1
26 Aug 2026, 00:531,424+17
22 Aug 2026, 20:161,407+29
19 Aug 2026, 09:551,378+13
16 Aug 2026, 18:341,365+33
12 Aug 2026, 21:591,332-4
9 Aug 2026, 14:121,336+1
6 Aug 2026, 08:031,335no change
6 Aug 2026, 06:221,335first reading

Engagement

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

Recent posts

1 Aug 2026, 06:14 UTC≈343 views0 reactionsread 6 August 2026

Париж Требуется человек на работу на 1–2 недели. Работа: вывоз строительного мусора и глины. Оплата договорная. ☎️ Пишите в личные сообщения или звоните по номеру: +33 758789964

31 Jul 2026, 09:26 UTC≈362 viewsread 6 August 2026

Париж Требуются люди на шпаклевку и покраску. ☎️ Контакты: +33758235256

30 Jul 2026, 09:24 UTC≈412 views0 reactionsread 6 August 2026

Париж Добрый день, на работу нужны 2-3 человека для шпаклевки, малярки, главное обязательство — быть ответственным. ☎️ Звоните: +33758235256

27 Jul 2026, 19:02 UTC≈479 views2 reactionsread 6 August 2026

Париж Приглашаем в команду мастера маникюра. • Высокий доход. • Официальное оформление. • Работа в красивом салоне премиум-класса, удобные рабочие места. • Дружный коллектив и комфортные условия. Требования: ✔️ Опыт от 1 года. ✔️ Аппаратный/комбинированный маникюр и педикюр. ✔️ Качественное покрытие гель-лаком и гелем. ☎️ Присылайте фото своих работ и краткую информацию о себе в WhatsApp: +33646492975 или звоните.

24 Jul 2026, 09:15 UTC≈519 viewsread 6 August 2026

Ищем водителя для грузовых перевозок и вывоза строительного мусора по Парижу. ☎️ Пишите на номер: +33663017337

24 Jul 2026, 00:53 UTC≈533 viewsread 6 August 2026

Париж Требуется подсобный рабочий. Оплата 12 евро в час, стабильные выплаты каждую неделю. Работа выездная. ☎️ По деталям звоните по номеру: 0785472976 или пишите в личные сообщения

22 Jul 2026, 07:21 UTC≈557 viewsread 6 August 2026

📍 час от Ниццы В охотхозяйство требуется егерь. Ищем человека, который знает и любит охоту, умеет обращаться с сельскохозяйственной техникой и ответственно относится к своей работе. Заработная плата — по результатам собеседования, зависит от опыта и профессиональных навыков. Возможно трудоустройство семейной пары. ☎️ Контакт (WhatsApp): +49 160 2204243

21 Jul 2026, 07:25 UTC≈530 viewsread 6 August 2026

Париж Добрый день, нужен парень для работы с гипсокартоном. Желательно, чтобы умел класть и банду. ☎️ Связываться по номеру: 07-49-34-76-06

20 Jul 2026, 13:47 UTC≈537 views1 reactionsread 6 August 2026

Париж Требуется подсобный рабочий. Оплата 12 евро в час, стабильные выплаты каждую неделю. Работа выездная. ☎️ По деталям звоните по номеру: 0785472976

19 Jul 2026, 17:20 UTC≈556 viewsread 6 August 2026

Париж На работу нужен человек на демонтажные работы. ☎️ Контакты: 0751525500

18 Jul 2026, 09:33 UTC≈611 views1 reactionsread 6 August 2026

В нашу детейлинг-студию в Mions требуется администратор. Если вы умный, инициативный человек, который не боится работать, умеет общаться с людьми и хочет расти вместе с компанией — будем рады познакомиться. Мы ищем человека, который: - быстро соображает и умеет принимать решения; - готов много работать и брать на себя ответственность; - обладает отличными коммуникативными навыками; - организован, внимателен к деталям…

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

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

“Работа в Париже 🇫🇷” (@travailler_a_paris), 1,525 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/travailler_a_paris.

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.