Telegram RegisterThe public register of Telegram
Telegram profile photo for job_in_lviv

Channel

job_in_lviv

@job_in_lviv

On this record: Topic · Growth · Engagement · Posts · Cite this entry

18subscribers

-3,032 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004458302399
TypeChannel
Username@job_in_lviv
Created4 September 2026 — measured — dated from the channel’s first post
First recorded15 September 2026
Last confirmed live11 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/job_in_lviv

Topic

Job listings — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 80% 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.

Growth

43,0541,5297 August 2026 — 3,050 subscribers8 August 2026 — 3,054 subscribers11 August 2026 — 3,046 subscribers14 August 2026 — 3,047 subscribers17 August 2026 — 3,027 subscribers20 August 2026 — 3,033 subscribers24 August 2026 — 3,030 subscribers27 August 2026 — 3,027 subscribers30 August 2026 — 3,035 subscribers2 September 2026 — 3,039 subscribers8 September 2026 — 4 subscribers15 September 2026 — 4 subscribers30 September 2026 — 10 subscribers11 October 2026 — 18 subscribers187 August 202611 October 2026
14 measurements spanning 65 days, net -3,032. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 11:5618+8
30 Sept 2026, 06:3910+6
15 Sept 2026, 23:234no change
8 Sept 2026, 06:414-3,035
2 Sept 2026, 19:443,039+4
30 Aug 2026, 12:423,035+8
27 Aug 2026, 05:293,027-3
24 Aug 2026, 04:133,030-3
20 Aug 2026, 21:283,033+6
17 Aug 2026, 21:033,027-20
14 Aug 2026, 11:583,047+1
11 Aug 2026, 06:273,046-8
8 Aug 2026, 08:313,054+4
7 Aug 2026, 18:533,050first reading

Engagement

1 post held, back to 4 September 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 1 post for this entry, the most recent from 4 September 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @job_in_lviv. 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 October 2026 — this entry's latest reading, not the date you are reading this.

“job_in_lviv” (@job_in_lviv), 18 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/job_in_lviv.

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.