Channel
@JestTech
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,031subscribers
-33 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002067155409 |
|---|---|
| Type | Channel |
| Username | @JestTech |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/JestTech |
Technology — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 20:01 | 1,031 | -4 |
| 12 Sept 2026, 10:20 | 1,035 | -1 |
| 8 Sept 2026, 14:36 | 1,036 | -5 |
| 3 Sept 2026, 02:29 | 1,041 | -3 |
| 30 Aug 2026, 19:03 | 1,044 | -5 |
| 28 Aug 2026, 00:37 | 1,049 | +1 |
| 25 Aug 2026, 10:43 | 1,048 | -2 |
| 21 Aug 2026, 23:57 | 1,050 | -2 |
| 18 Aug 2026, 20:07 | 1,052 | -5 |
| 15 Aug 2026, 10:44 | 1,057 | -3 |
| 11 Aug 2026, 15:43 | 1,060 | -4 |
| 7 Aug 2026, 11:32 | 1,064 | no change |
| 7 Aug 2026, 11:27 | 1,064 | first reading |
20 posts held, back to 14 June 2026 — 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
v0.6.16 - Security: Trade executions and cancellations now await exchange confirmation before reporting success, improving protection against race conditions or false positives. - Security: Terminal sessions use safer cookie handling for authentication, avoiding leakage of tokens to the client. - Security: Production startup enforces strong secrets and strict access control for administrative actions and encrypted s…
Signed Scientio
v0.6.14 - Feature: Optional live trading latency tracking, with summary stats available. Sampling mode for canary testing. - Feature: Added support for spot trading actions and automated buying on supported platforms. - Feature: Strategy versions now save full parameter details and unique IDs. - Feature: Only verified strategies can be deployed. - Feature: Validation for strategy usage is now more strict; cached res…
Signed Scientio
https://x.com/JestTech/status/2084805526794461393
Signed Scientio
https://x.com/JestTech/status/2084115533797196281?s=20
Signed Scientio
v0.6.13 - Fix: Auto-trades work even if Hyperliquid keys are frozen or wallet status lags. - Feature: More specific error codes appear for exchange setup and auth issues, so Telegram gives clearer fixes. - Fix: Auto-trading lag is healed for strategy signals; missing wallets use the correct error code.
Signed Scientio
v0.6.12 - Telegram menu now shows Oroboros link when enabled, allowing one-tap Telegram login for Oroboros traders. - Added deep linking: users opening Oroboros from Telegram are signed in automatically, skipping manual login. - Desktop login flow improved for Oroboros with automatic session setup and redirect. - Fixed: Oroboros session now initializes smoothly on first load, strips login parameters from the URL aft…
Signed Scientio
JESTER v0.6.11 is a major cleanup and control update across the terminal. Automation can now be configured per strategy, routed by venue, managed globally, and controlled in bulk, while stuck deployments recover properly and each mode shows the right controls. Trading flows are now more reliable across manual, assisted, automated, batched, and close actions. Strategy stats, portfolio refreshes, conversation sync, Te…
Signed Scientio
JESTER v0.6.11 - Fix: Strategy live stats now stay accurate for each pair after removing a market; stats storage and live updates are properly cleaned up and resynced as pairs are managed. - Fix: Terminal setup for Telegram login improved to prevent wallet login from interfering with Telegram session and terms activation; UI clarifies wallet connection state; additional wallet supported. - Fix: Manual and assisted t…
Signed Scientio
Channel name was changed to «Jester | News»
Introducing Oroboros Oroboros is the first standalone product built on the JESTER engine. It uses the same JESTER accounts, backend strategies, execution infrastructure, and trading engine we have been building for years, packaged inside a purpose-built trading terminal. app.jester.trade/oroboros
NEW: Tesseract Charts have one glaring issue. They are almost entirely built from the past. Candles show what price did. Volume shows what already traded. Indicators are usually calculations performed on that same historical data. The market also exists in the present, through live participation, trade flow, volatility, and pressure. And it has an implied future structure, through the liquidity already sitting in…
Most AI agents still work alone. They can be intelligent, they can have access to good tools and good data, but they are still isolated inside a single conversation. One agent researches something, another agent somewhere else researches the same thing, and neither benefits from what the other has already seen. They repeat work, repeat mistakes, and arrive at conclusions without ever having those conclusions challeng…
Showing the 12 most recent of 20 posts we hold for @JestTech. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Jester | News” (@JestTech), 1,031 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/JestTech.
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.