Telegram RegisterThe public register of Telegram
Telegram profile photo for Afriwork Applicant Bot

Bot

Afriwork Applicant Bot

@afriworkapplicantbot

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

71,270monthly users

+1,929 since we began measuring on 6 August 2026

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

Register entry

Telegram ID6222760680
TypeBot
Username@afriworkapplicantbot
First recorded11 August 2026
Last confirmed live6 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/afriworkapplicantbot

Topic

Other / unclassifiable — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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

65,95478,26172,107.56 August 2026 — 69,341 monthly users7 August 2026 — 69,495 monthly users9 August 2026 — 69,616 monthly users10 August 2026 — 69,380 monthly users11 August 2026 — 69,380 monthly users12 August 2026 — 69,203 monthly users12 August 2026 — 69,048 monthly users14 August 2026 — 69,304 monthly users15 August 2026 — 69,797 monthly users16 August 2026 — 69,301 monthly users17 August 2026 — 69,085 monthly users18 August 2026 — 69,413 monthly users19 August 2026 — 69,314 monthly users20 August 2026 — 69,709 monthly users22 August 2026 — 70,480 monthly users24 August 2026 — 70,259 monthly users25 August 2026 — 69,771 monthly users26 August 2026 — 69,705 monthly users27 August 2026 — 69,603 monthly users28 August 2026 — 70,068 monthly users29 August 2026 — 70,466 monthly users30 August 2026 — 69,970 monthly users31 August 2026 — 69,419 monthly users2 September 2026 — 69,425 monthly users3 September 2026 — 69,202 monthly users4 September 2026 — 70,053 monthly users7 September 2026 — 69,334 monthly users10 September 2026 — 68,276 monthly users12 September 2026 — 67,867 monthly users14 September 2026 — 65,954 monthly users15 September 2026 — 67,389 monthly users17 September 2026 — 70,558 monthly users28 September 2026 — 71,188 monthly users5 October 2026 — 72,499 monthly users9 October 2026 — 75,000 monthly users13 October 2026 — 75,006 monthly users14 October 2026 — 76,607 monthly users15 October 2026 — 77,707 monthly users16 October 2026 — 78,261 monthly users18 October 2026 — 76,683 monthly users19 October 2026 — 72,738 monthly users20 October 2026 — 73,695 monthly users22 October 2026 — 73,796 monthly users23 October 2026 — 74,091 monthly users24 October 2026 — 73,622 monthly users25 October 2026 — 73,117 monthly users26 October 2026 — 72,437 monthly users28 October 2026 — 72,260 monthly users29 October 2026 — 72,354 monthly users30 October 2026 — 72,799 monthly users31 October 2026 — 73,232 monthly users1 November 2026 — 72,838 monthly users2 November 2026 — 72,096 monthly users3 November 2026 — 71,376 monthly users4 November 2026 — 71,210 monthly users4 November 2026 — 71,235 monthly users6 November 2026 — 71,270 monthly users71,2706 August 20266 November 2026
57 measurements spanning 91 days, net +1,929. 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 64,108–80,107 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 57
Measured (UTC)Monthly usersChange
6 Nov 2026, 03:0671,270+35
4 Nov 2026, 23:5971,235+25
4 Nov 2026, 02:5971,210-166
3 Nov 2026, 04:1971,376-720
2 Nov 2026, 03:4972,096-742
1 Nov 2026, 07:2072,838-394
31 Oct 2026, 05:0173,232+433
30 Oct 2026, 08:1672,799+445
29 Oct 2026, 07:3772,354+94
28 Oct 2026, 06:4872,260-177
26 Oct 2026, 12:5972,437-680
25 Oct 2026, 14:0473,117-505
24 Oct 2026, 13:0673,622-469
23 Oct 2026, 10:3174,091+295
22 Oct 2026, 07:3773,796+101
20 Oct 2026, 22:1573,695+957
19 Oct 2026, 23:2772,738-3,945
18 Oct 2026, 20:4176,683-1,578
16 Oct 2026, 20:0978,261+554
15 Oct 2026, 19:1877,707first 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.

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

“Afriwork Applicant Bot” (@afriworkapplicantbot), 71,270 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/afriworkapplicantbot.

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.