Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐉𝐄𝐒̶𝐓𝐄̶𝐑𝐒̶

Channel

𝐉𝐄𝐒̶𝐓𝐄̶𝐑𝐒̶

@JESTERSTM

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

218subscribers

+21 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003799239580
TypeChannel
Username@JESTERSTM
Created29 May 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/JESTERSTM

Growth

197218207.58 August 2026 — 197 subscribers9 August 2026 — 197 subscribers16 August 2026 — 218 subscribers8 August 202616 August 2026
3 measurements spanning 8 days, net +21. 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 194–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 19:46218+21
9 Aug 2026, 02:11197no change
8 Aug 2026, 15:15197first reading

Engagement

13 posts held, back to 29 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Jun 2026, 10:08 UTC408 viewsread 8 August 2026

⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ➿➿➿➿➿➿➿➿➿ В био: js†r j.str js jstr jtrs ➿➿➿➿➿➿➿➿➿ В ник: ʲˢ†ʳ ʲˢ ʲˢᵗʳ ʲᵗʳˢ ⱼₛ†ᵣ (Копируется при нажатии).

26 Jun 2026, 08:07 UTC260 viewsread 8 August 2026
Photo

LEADER CO-LEADER @KS6MR9 @KMERTX SENIOR ADMIN @goxxyoxyo ㅤ CHAT ADMIN @NLXOS ADMIN BY ASSET @ ADMIN BY INTERACTIVE @ ADMIN BY VIDEO @kaiziizo

26 Jun 2026, 08:05 UTC203 viewsread 8 August 2026
Photo

Начиная с 26.06.2026, на постоянной основе за нами закреплено название: JESTERS Его использование – в том числе частичное, искаженное или в ином контексте – без прямого согласования с владельцами приравнивается к нарушению авторских прав. Предупреждение дано в открытом доступе. Не знание приоритетов JESTERS не освобождает вас от ответственности.

26 Jun 2026, 08:04 UTC152 viewsread 8 August 2026
Photo

Чат 17+ Проверка документов в обязательном порядке. @JESTRSBot – бот для проверки документов. В мире человеческого отчаяния и хаоса мы стали ведущими для ведомых. Двери шатра «JESTERS» открыты для всех: для потерянных, для любопытных, для тех, кто ищет своё место среди шума и тьмы. Но помни — войти под купол гораздо проще, чем покинуть его прежним. Добро пожаловать под купол, где безумие говорит громче здравого см

26 Jun 2026, 08:04 UTC175 viewsread 8 August 2026
Photo

⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ➿➿➿➿➿➿➿➿ Администрация ➿➿➿➿➿➿ Патент ➿➿➿➿➿➿➿➿ Правила ➿➿➿➿➿➿ Инициалы ➿➿➿➿➿➿➿➿ Тик ток ➿➿➿➿➿➿ Буст

Showing the 12 most recent of 13 posts we hold for @JESTERSTM. 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.

Citation-graph rank

Citation-graph rank — 1,160,119 of 1,565,402entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

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

“𝐉𝐄𝐒̶𝐓𝐄̶𝐑𝐒̶” (@JESTERSTM), 218 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/JESTERSTM.

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.