Bot

Olma Job

@olma_job_bot

On this record: Growth · Engagement · Citations · Cite this entry

18,890monthly users

+2,181 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	8106385597
Type	Bot
Username	@olma_job_bot
First recorded	17 August 2026
Last confirmed live	30 August 2026
Measurements held	17
Confirmed unchanged	1 time, most recently 30 August 2026
On Telegram	t.me/olma_job_bot

Growth

17 measurements spanning 22 days, net +2,181. 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 16,382–19,217 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
30 Aug 2026, 03:58	18,890	+100
28 Aug 2026, 01:45	18,790	+885
26 Aug 2026, 23:27	17,905	-561
25 Aug 2026, 04:14	18,466	+541
24 Aug 2026, 02:58	17,925	-515
22 Aug 2026, 13:43	18,440	+8
21 Aug 2026, 04:07	18,432	+711
19 Aug 2026, 04:34	17,721	-416
17 Aug 2026, 10:12	18,137	no change
17 Aug 2026, 09:26	18,137	+457
15 Aug 2026, 17:28	17,680	+6
14 Aug 2026, 06:08	17,674	+54
12 Aug 2026, 23:23	17,620	+168
11 Aug 2026, 21:15	17,452	+171
11 Aug 2026, 00:18	17,281	+152
8 Aug 2026, 21:58	17,129	+420
7 Aug 2026, 22:49	16,709	first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 4 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.

Named by

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

Вакансии в Фергане
@fargona_bandlik · 18,56112 posts FARGONA ISH
@fargona_ish_bor · 50,0668 posts FARGONA ISH BOR
@fargona_ish_bor_margilon_ish · 236,3278 posts ISHBOR ISHKEREMI
@ishbort · 291,5885 posts

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

“Olma Job” (@olma_job_bot), 18,890 monthly users as measured 30 August 2026. Telegram Register, tgregister.com/channel/olma_job_bot.

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.