Telegram RegisterThe public register of Telegram
Telegram profile photo for GCC & LEVANT Jobs

Supergroup

GCC & LEVANT Jobs

@WePostJobs

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

4,482members

-253 since we began measuring on 7 August 2026

77 online right now

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

Register entry

Telegram ID-1001507534537
TypeSupergroup
Username@WePostJobs
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live6 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/WePostJobs

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 13 September 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 the other topics.

Growth

4,4824,7354,608.57 August 2026 — 4,735 members10 August 2026 — 4,726 members13 August 2026 — 4,715 members16 August 2026 — 4,707 members20 August 2026 — 4,695 members24 August 2026 — 4,684 members27 August 2026 — 4,673 members30 August 2026 — 4,664 members2 September 2026 — 4,661 members2 September 2026 — 4,661 members6 September 2026 — 4,651 members11 September 2026 — 4,643 members14 September 2026 — 4,620 members19 September 2026 — 4,604 members29 September 2026 — 4,587 members6 October 2026 — 4,564 members13 October 2026 — 4,546 members16 October 2026 — 4,535 members19 October 2026 — 4,530 members22 October 2026 — 4,523 members25 October 2026 — 4,514 members28 October 2026 — 4,511 members31 October 2026 — 4,502 members3 November 2026 — 4,490 members6 November 2026 — 4,482 members7 August 20266 November 2026
25 measurements spanning 91 days, net -253. 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 4,444–4,773 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
6 Nov 2026, 15:544,482-8
3 Nov 2026, 13:284,490-12
31 Oct 2026, 06:304,502-9
28 Oct 2026, 03:354,511-3
25 Oct 2026, 06:464,514-9
22 Oct 2026, 16:064,523-7
19 Oct 2026, 17:564,530-5
16 Oct 2026, 13:574,535-11
13 Oct 2026, 03:184,546-18
6 Oct 2026, 13:384,564-23
29 Sept 2026, 14:004,587-17
19 Sept 2026, 09:354,604-16
14 Sept 2026, 17:594,620-23
11 Sept 2026, 07:584,643-8
6 Sept 2026, 07:574,651-10
2 Sept 2026, 22:034,661no change
2 Sept 2026, 00:374,661-3
30 Aug 2026, 05:154,664-9
27 Aug 2026, 11:164,673-11
24 Aug 2026, 08:064,684first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.

“GCC & LEVANT Jobs” (@WePostJobs), 4,482 members as measured 6 November 2026. Telegram Register, tgregister.com/channel/WePostJobs.

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.