Telegram RegisterThe public register of Telegram

Channel

ГОТОВ РАБОТАТЬ. Работа Москва!

@Readywork2

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

5,277subscribers

+26 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001600244593
TypeChannel
Username@Readywork2
CreatedBetween 1 October 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/Readywork2

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
@Readywork/186021 Jul 2026, 09:58 UTC@Readywork2/2055 · this entry21 Jul 2026, 09:58 UTC1.00under a minute
@Readywork/186222 Jul 2026, 08:26 UTC@Readywork2/2056 · this entry22 Jul 2026, 08:26 UTC1.00under a minute
@Readywork/186323 Jul 2026, 05:05 UTC@Readywork2/2057 · this entry23 Jul 2026, 05:05 UTC1.00under a minute
@Readywork/186831 Jul 2026, 04:11 UTC@Readywork2/2062 · this entry31 Jul 2026, 04:11 UTC1.00under a minute
@Readywork/18715 Aug 2026, 05:42 UTC@Readywork2/2065 · this entry5 Aug 2026, 05:42 UTC1.00under a minute
@Readywork/18725 Aug 2026, 08:16 UTC@Readywork2/2066 · this entry5 Aug 2026, 08:16 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Readywork16 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (151)

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 1 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 15 July 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 2, the earliest publisher we hold is @Readywork2 — 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 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 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

5,2515,2775,2647 August 2026 — 5,251 subscribers8 August 2026 — 5,253 subscribers10 August 2026 — 5,277 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net +26. 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 5,247–5,281 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 23:555,277+24
8 Aug 2026, 06:085,253+2
7 Aug 2026, 17:035,251first reading

Engagement

25 posts held, back to 15 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 7 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.0%
avg views ÷ 5,277 subscribers
Avg views / post
739
25 posts measured
Reaction rate
0.098%
reactions ÷ views · ER floor
Posts in window
25
of 25 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. It is computed over the 12 of 25 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held25 (15 July 20269 August 2026)
Views total18,465
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04: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
9
Links
809

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

9 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
666.7%
🐳111.1%
💋111.1%
🤝111.1%

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

Measured over the 25 most recent posts we hold, published 15 July 2026 to 9 August 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

9 Aug 2026, 21:14 UTC375 viewsread 12 August 2026

⚡ ЗАЯВКА СРОЧНО на сейчас м.Авиамоторная⚡ 10.08 1:00-5:00+/-час Перовский пр.3с16 м.Авиамоторная 💰Оплата 2500₽-3000₽ (500₽/ч) 🛠 разгрузка оборудования на базе 👷 Нужно еще 3 чел (хелпера/грузчика) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Перовский пр.3с16 м.Авиамоторная 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать до адреса Перовский пр.3, с16 https://yandex.ru/maps/org/vsg/

8 Aug 2026, 10:51 UTC527 views0 reactionsread 12 August 2026

Работа на сегодня 8 августа Время : 23:59 Метро Лужники Требуются 2 человека Помощь монтажникам с сбор проводов Укладка кабель каналов Загрузка/ выгрузка машины И прочие задачи от старшего на месте Оплата : 500₽ в час , минималка 8 часов Ответственные, работящие. РФ 🇷🇺 Для записи пишите в ЛС: 1. ФИО 2. Дата рождения 3. Телефон с вотсапом Связь @burwolf12

8 Aug 2026, 09:02 UTC449 views2 reactionsread 12 August 2026

⚡ ЗАЯВКА на 18:00 Воробьевы горы⚡ 8.08 18:00-22:00+/-час воробьевы горы смотровая площадка ул.Косыгина 💰Оплата 2000₽-2500₽ (500₽/ч) 🛠 помочь на Демонтаже/перемонтаже и погрузка/разгрузка оборудования 👷 Нужно 4 чел (хелпера/грузчика) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Воробьевы горы 1. ФИО 2. Номер тел. 3. Дата рождения 4. Где живете Место встреси ул. Косыгина смотровая площадка В

1🤝1

8 Aug 2026, 08:12 UTC387 views2 reactionsread 12 August 2026

⚡ ЗАЯВКА на 18:00 "Под облаками" м.Пятницкое шоссе⚡ 8.08 18:00-20:00+/-час Под Облаками м.Пятницкое шоссе 💰Оплата 2000₽-2500₽ (500₽/ч) 🛠 помочь на Демонтаже и погрузка оборудования 👷 Нужно 4 чел (хелпера/грузчика) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Под облаками 1. ФИО 2. Номер тел. 3. Дата рождения 4. Где живете Под облаками Московская область, городской округ Красногорск, террит

1💋1

8 Aug 2026, 01:58 UTC379 viewsread 12 August 2026

⚡ ЗАЯВКА СРОЧНО на сейчас. "Под облаками" м.Пятницкое шоссе⚡ 8.08 6:00-10:00+/-час под облаками м.Пятницкое шоссе 💰Оплата 2500₽+/-500₽ + такси до площадки 🛠 разгрузка и помочь на монтаже 👷 Нужно еще 2 чел (хелпера/грузчика) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Под облаками 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать до адреса Под облаками Московская область, городской ок

7 Aug 2026, 05:38 UTC396 viewsread 12 August 2026

⚡ ЗАЯВКА СРОЧНО на сейчас. Воробьёвы Горы ⚡ 7.08 9:30-15:00+/-час Воробьёвы горы смотровая площадка (ул.Косыгина) 💰Оплата 2500-3000₽+/-500₽ (от 2000₽ 500₽/ч) 🛠Основные задачи разгрузка разнос и помощь в монтаже оборудования 👷 Нужен еще 1 чел (хелпер/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Воробьевы горы 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать до адреса Место вс

7 Aug 2026, 04:33 UTC396 viewsread 12 August 2026

⚡ ЗАЯВКА СРОЧНО на 9:00+/-30мин. Воробьёвы Горы ⚡ 7.08 9:00-15:00+/-час Воробьёвы горы смотровая площадка (ул.Косыгина) 💰Оплата 2500-3000₽+/-500₽ (от 2000₽ 500₽/ч) 🛠Основные задачи разгрузка разнос и помощь в монтаже оборудования 👷 Нужно 3 чел (хелпера/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Воробьевы горы 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать до адреса Место

6 Aug 2026, 11:38 UTC468 viewsread 12 August 2026

⚡ Открыт набор на ДКФ(Детский форум)⚡ Локация: Воробьевы горы День/ночь в две смены работа 10-12 часов смена Дата: 19.08-23.08 💰Оплата 4500-6500₽ (от 2000₽ 500₽/ч) 👷 Нужно еще 25 чел (хелпера/грузчик) 🛠Основные задачи - Таскать , грузить , ставить , помогать(выполнять задачи старших на площадке) Кого интересует, заполняйте анкету для пропуска ‼️СЕГОДНЯ‼️ По вопросам писать: @Vassia_21 с темой: ДКФ Ссылка на форму 🔽

5 Aug 2026, 08:16 UTC530 viewsread 12 August 2026

⚡ ЗАЯВКА НА 12:00⚡ Адрес: железнодорожная 2 деревня Подрезково 12:00-15:00+- 💰Оплата 2500₽ (от 2000₽ 500₽/ч) 🛠Основные задачи - Вынос вещей , грузить (вас будет 4) 👷 Нужно еще 1 чел (хелпера/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Подрезково 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать

5 Aug 2026, 05:42 UTC504 views1 reactionsread 12 August 2026

⚡ ЗАЯВКА НА 9:00⚡ Автозаводская 28 , железнодорожный 9:00-10:00+- 💰Оплата 2000₽ (от 2000₽ 500₽/ч) 🛠Основные задачи - Задача вынести стойку(вас будет 4) 👷 Нужно еще 1 чел (хелпера/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Железнодорожный 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать

1

2 Aug 2026, 20:44 UTC750 views0 reactionsread 12 August 2026

⚡ ЗАЯВКА 3.08 4:00-8:00+/- парк Коломенский ⚡ 💰Оплата 2500₽+/-500 (от 2000₽+ такси до площадки 500₽/ч) 🛠Основные задачи - разгрузка и разнос частей стенда помочь на монтаже 👷 Нужно 5 чел (хелпера/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: парк Коломенский 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько стоит такси 5. От куда едите адрес Место проведения Зингаро Москва, музей-за

1 Aug 2026, 12:43 UTC765 views0 reactionsread 12 August 2026

⚡ ЗАЯВКА НА 17:00⚡ Ленинградский проспект, 47 м.Аэропорт 17:00-19:00+- 💰Оплата 2000₽ (от 2000₽ 500₽/ч) 🛠Основные задачи - грузить, тоскать, помогать! 👷 Нужно еще 2 чел (хелпера/грузчик) Кого интересует, пишите мне в личку Tg @vassia_21 Василий. Тема работы: Аэропорт 1. ФИО 2. Номер тел. 3. Дата рождения 4. Сколько ехать

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

“ГОТОВ РАБОТАТЬ. Работа Москва!” (@Readywork2), 5,277 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Readywork2.

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.