Telegram RegisterThe public register of Telegram
Telegram profile photo for GJESM

Channel

GJESM

@gjesm

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

261subscribers

-2 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-1001331321624
TypeChannel
Username@gjesm
CreatedBetween 1 March 2018 and 1 June 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 October 2026
Measurements held6
Confirmed unchanged2 times, most recently 9 October 2026
On Telegramt.me/gjesm

Topic

Education — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

260263261.57 August 2026 — 263 subscribers8 August 2026 — 263 subscribers8 August 2026 — 262 subscribers7 September 2026 — 261 subscribers15 September 2026 — 260 subscribers30 September 2026 — 261 subscribers2617 August 202630 September 2026
6 measurements spanning 53 days, net -2. 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 260–263 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 01:15261+1
15 Sept 2026, 01:20260-1
7 Sept 2026, 22:36261-1
8 Aug 2026, 11:58262-1
8 Aug 2026, 09:03263no change
7 Aug 2026, 21:14263first reading

Engagement

20 posts held, back to 1 June 2018 — 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 20 posts for this entry, the most recent from 4 July 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 May 2019, 15:47 UTC≈5,610 viewsread 8 August 2026

قابل توجه نشریات علمی و پژوهشگران: در سامانه Scimago وابسته به پایگاه استنادی Scopus تعداد 174 نشریه ایرانی نمایه شده در SJR را ملاحظه فرمایید: این نشریات براساس (Q1, Q2, Q3 ,Q4) ردیف شده است. https://www.scimagojr.com/journalrank.php?country=IR

Showing the 12 most recent of 20 posts we hold for @gjesm. 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 30 September 2026 — this entry's latest reading, not the date you are reading this.

“GJESM” (@gjesm), 261 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/gjesm.

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.