Telegram RegisterThe public register of Telegram
Telegram profile photo for Правовой инспектор РОСПРОФЖЕЛ

Channel

Правовой инспектор РОСПРОФЖЕЛ

@pravovoyinspector

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

10,751subscribers

-131 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001712410035
TypeChannel
Username@pravovoyinspector
DescriptionЗащита трудовых прав членов РОСПРОФЖЕЛ
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/pravovoyinspector

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.

Growth

10,75110,88310,8179 August 2026 — 10,882 subscribers10 August 2026 — 10,883 subscribers11 August 2026 — 10,882 subscribers12 August 2026 — 10,881 subscribers14 August 2026 — 10,879 subscribers15 August 2026 — 10,877 subscribers17 August 2026 — 10,876 subscribers18 August 2026 — 10,874 subscribers20 August 2026 — 10,866 subscribers21 August 2026 — 10,863 subscribers24 August 2026 — 10,860 subscribers25 August 2026 — 10,858 subscribers26 August 2026 — 10,855 subscribers27 August 2026 — 10,854 subscribers29 August 2026 — 10,853 subscribers29 August 2026 — 10,848 subscribers31 August 2026 — 10,842 subscribers3 September 2026 — 10,845 subscribers4 September 2026 — 10,843 subscribers8 September 2026 — 10,838 subscribers11 September 2026 — 10,836 subscribers12 September 2026 — 10,834 subscribers14 September 2026 — 10,832 subscribers16 September 2026 — 10,830 subscribers2 October 2026 — 10,808 subscribers7 October 2026 — 10,799 subscribers12 October 2026 — 10,794 subscribers14 October 2026 — 10,791 subscribers16 October 2026 — 10,789 subscribers17 October 2026 — 10,788 subscribers18 October 2026 — 10,787 subscribers19 October 2026 — 10,786 subscribers20 October 2026 — 10,785 subscribers21 October 2026 — 10,783 subscribers22 October 2026 — 10,780 subscribers23 October 2026 — 10,775 subscribers26 October 2026 — 10,774 subscribers27 October 2026 — 10,772 subscribers28 October 2026 — 10,770 subscribers29 October 2026 — 10,768 subscribers30 October 2026 — 10,767 subscribers1 November 2026 — 10,765 subscribers3 November 2026 — 10,762 subscribers4 November 2026 — 10,758 subscribers5 November 2026 — 10,755 subscribers6 November 2026 — 10,754 subscribers7 November 2026 — 10,751 subscribers9 August 20267 November 2026
47 measurements spanning 90 days, net -131. 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 10,731–10,903 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
7 Nov 2026, 03:2710,751-3
6 Nov 2026, 02:4510,754-1
5 Nov 2026, 02:4510,755-3
4 Nov 2026, 04:5910,758-4
3 Nov 2026, 02:0910,762-3
1 Nov 2026, 22:4010,765-2
30 Oct 2026, 21:1710,767-1
29 Oct 2026, 21:5710,768-2
28 Oct 2026, 18:4110,770-2
27 Oct 2026, 17:1410,772-2
26 Oct 2026, 19:1910,774-1
23 Oct 2026, 18:2010,775-5
22 Oct 2026, 15:0510,780-3
21 Oct 2026, 12:1910,783-2
20 Oct 2026, 06:5010,785-1
19 Oct 2026, 09:0710,786-1
18 Oct 2026, 10:4710,787-1
17 Oct 2026, 10:4510,788-1
16 Oct 2026, 07:5810,789-2
14 Oct 2026, 04:4010,791first reading

Engagement

39 posts held, back to 21 May 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 42 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.3%
avg views ÷ 10,751 subscribers
Avg views / post
2,290
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 39 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 3 November 2026
Posts held39 (21 May 2026 – 3 November 2026)
Views total13,710
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 21:02 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
181
Links
166

Lifetime counters from Telegram’s own channel header, read 7 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (0%) 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).

3 Nov 2026, 04:50 UTC≈1,260 viewsread 7 November 2026

Что важно знать при сокращени численности (штата) 👉 При сокращении численности или штата работодателем часто допускаются нарушения трудового законодательства, в части, когда работнику не предложили вакансии в день увольнения. Например, работники были предупреждены о сокращении за два месяца. На момент предупреждения работников о сокращении штата у работодателя отсутствовали вакантные должности, котор…

23 Oct 2026, 04:05 UTC≈2,700 viewsread 7 November 2026

Если работник заболел во время отпуска, должен ли работодатель его перенести? ✅Если работник заболел во время отпуска и не выразил желания его перенести, отпуск автоматически продлевается на число дней временной нетрудоспособности ст. 124 ТК. Писать для этого отдельное заявление работник не обязан. Он может вернуться на работу после выздоровления и использования оставшихся дней отпуска. При этом работнику необходим…

19 Oct 2026, 08:10 UTC≈3,600 viewsread 7 November 2026

Можно ли на работника возложить обязанность выполнять любые поручения руководства? 👉При определении должностных обязанностей работника бывает проблематично предусмотреть все возможные трудовые действия, которые могут от него потребоваться. Поэтому работодатели нередко оставляют себе лазейку, подстраховываясь на случай возникновения необходимости в выполнении работником таких обязанностей, которые прямо поименованы …

5 Oct 2026, 06:50 UTC≈3,750 viewsread 7 November 2026

Вопрос: Может ли работодатель уволить по сокращению численности (штата) работницу с ребенком до 3 лет, если она сама просит уволить ее по данному основанию❓ 👉Работодатель не имеет права уволить по сокращению численности или штата работницу, имеющую ребенка в возрасте до трех лет, даже если она сама просит об этом и в организации идет процедура сокращения. Исключение составляют случаи ликвидации организации или прекр…

30 Sept 2026, 04:15 UTC≈4,150 viewsread 7 November 2026

Вопрос: Имеет ли право работодатель привлекать к работе или требовать объяснения через мессенджеры или по телефону работника, находящегося в отпуске или на больничном❓ ⚖Ответ: Работодатель не имеет права привлекать работника к работе или требовать объяснения через мессенджеры или по телефону, если работник находится в отпуске или на больничном. Исключение – случаи отзыва работника из отпуска с его письменного соглас…

24 Sept 2026, 05:01 UTC≈5,000 viewsread 7 November 2026

Вопрос: Можно ли привлекать к сверхурочной работе работника на основании одного заявления (согласия), написанного на весь год❓ 👉 Ответ: Необходимо отметить, что с 1 сентября 2026 года в ст. 99 ТК РФ внесены новые нормы, устанавливающие условия привлечения к сверхурочной работе сверх 120 часов в год. Согласно нововведений, привлечение к сверхурочной работе начиная со 121 часа в году во всех случаях требует письм…

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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.

РОСПРОФЖЕЛ
@rosprofzhel_rzd · 26,660
Telegram ranks this channel #7 of 93 here — alongside 92 others — read 11 September 2026
РЖД | Первый кадровый
@ckadr_rzd · 22,211
Telegram ranks this channel #90 of 95 here — alongside 94 others — read 20 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“Правовой инспектор РОСПРОФЖЕЛ” (@pravovoyinspector), 10,751 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/pravovoyinspector.

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.