Telegram RegisterThe public register of Telegram
Telegram profile photo for Pan

Channel

Pan

@PanSystem

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

19,155subscribers

-5,130 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002465296934
TypeChannel
Username@PanSystem
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 October 2026
Measurements held54
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/PanSystem

Topic

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

Growth

19,15524,28521,7207 August 2026 — 24,285 subscribers7 August 2026 — 24,285 subscribers8 August 2026 — 24,099 subscribers9 August 2026 — 24,062 subscribers10 August 2026 — 23,924 subscribers11 August 2026 — 23,745 subscribers12 August 2026 — 23,568 subscribers14 August 2026 — 23,497 subscribers15 August 2026 — 23,299 subscribers16 August 2026 — 23,156 subscribers17 August 2026 — 23,040 subscribers18 August 2026 — 22,991 subscribers19 August 2026 — 22,835 subscribers20 August 2026 — 22,837 subscribers22 August 2026 — 22,764 subscribers23 August 2026 — 22,571 subscribers25 August 2026 — 22,494 subscribers26 August 2026 — 22,412 subscribers27 August 2026 — 22,346 subscribers28 August 2026 — 22,306 subscribers29 August 2026 — 22,242 subscribers30 August 2026 — 22,162 subscribers31 August 2026 — 22,093 subscribers1 September 2026 — 21,979 subscribers2 September 2026 — 21,888 subscribers3 September 2026 — 21,832 subscribers5 September 2026 — 21,673 subscribers9 September 2026 — 21,477 subscribers11 September 2026 — 21,360 subscribers13 September 2026 — 21,273 subscribers15 September 2026 — 21,236 subscribers16 September 2026 — 21,179 subscribers19 September 2026 — 21,066 subscribers26 September 2026 — 20,749 subscribers4 October 2026 — 20,314 subscribers8 October 2026 — 20,064 subscribers13 October 2026 — 19,895 subscribers14 October 2026 — 19,800 subscribers15 October 2026 — 19,777 subscribers16 October 2026 — 19,745 subscribers17 October 2026 — 19,715 subscribers18 October 2026 — 19,687 subscribers19 October 2026 — 19,669 subscribers20 October 2026 — 19,624 subscribers21 October 2026 — 19,567 subscribers22 October 2026 — 19,517 subscribers23 October 2026 — 19,505 subscribers24 October 2026 — 19,432 subscribers25 October 2026 — 19,418 subscribers26 October 2026 — 19,375 subscribers27 October 2026 — 19,309 subscribers28 October 2026 — 19,285 subscribers29 October 2026 — 19,232 subscribers30 October 2026 — 19,155 subscribers7 August 202630 October 2026
54 measurements spanning 84 days, net -5,130. 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 18,386–25,055 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
30 Oct 2026, 17:5819,155-77
29 Oct 2026, 15:4919,232-53
28 Oct 2026, 18:3919,285-24
27 Oct 2026, 19:5819,309-66
26 Oct 2026, 18:3819,375-43
25 Oct 2026, 16:3719,418-14
24 Oct 2026, 15:3019,432-73
23 Oct 2026, 17:4019,505-12
22 Oct 2026, 20:3119,517-50
21 Oct 2026, 13:5919,567-57
20 Oct 2026, 13:2119,624-45
19 Oct 2026, 10:2819,669-18
18 Oct 2026, 11:0619,687-28
17 Oct 2026, 08:4919,715-30
16 Oct 2026, 11:0619,745-32
15 Oct 2026, 14:3819,777-23
14 Oct 2026, 16:0119,800-95
13 Oct 2026, 04:2819,895-169
8 Oct 2026, 23:5820,064-250
4 Oct 2026, 11:4220,314first reading

Engagement

33 posts held, back to 7 July 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 57 pages 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 33 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Sept 2026, 13:41 UTC9 viewsread 3 September 2026

Users don’t buy GPUs. They buy reliable runtime: job starts, job finishes, and usage is metered correctly. https://t.co/jjRbhEd3kc — PAN (@Pan_Ecosystem) Sep 1, 2026

Signed IFTTT

26 Aug 2026, 15:36 UTC14 viewsread 3 September 2026

Listing distributed GPUs is easy. Making different cards, drivers, and networks behave like one reliable product is the hard part. — PAN (@Pan_Ecosystem) Aug 26, 2026

Signed IFTTT

25 Aug 2026, 18:31 UTC12 viewsread 3 September 2026

Cheap GPU time isn’t cheap when the node dies halfway through a job. Price the completed run, not the advertised hour. — PAN (@Pan_Ecosystem) Aug 25, 2026

Signed IFTTT

23 Aug 2026, 16:41 UTC16 viewsread 3 September 2026

Idle GPUs aren’t compute. If developers can’t discover them, verify them, run jobs to completion, and pay for actual usage, they’re just hardware. — PAN (@Pan_Ecosystem) Aug 23, 2026

Signed IFTTT

20 Aug 2026, 15:16 UTC18 viewsread 3 September 2026

Agent compute is not one big bill. It is hundreds of small executions that become visible only after they add up. https://t.co/tRbmilJYPy — PAN (@Pan_Ecosystem) Aug 20, 2026

Signed IFTTT

18 Aug 2026, 19:41 UTC20 viewsread 3 September 2026

14,000 designs. 9 binders. 3 sub-nanomolar. The agent didn't win because it was smart. It won because the loop was closed: design → wet-lab validate → feed back. Autonomous execution only pays off when there's a checkpoint at the end. https://t.co/zyvvLjIMdN — PAN (@Pan_Ecosystem) Aug 18, 2026

Signed IFTTT

18 Aug 2026, 15:11 UTC19 viewsread 3 September 2026

A wallet is not an approval system. If an agent can spend, you need to define: what it can buy, how much it can spend, and when a human must approve. https://t.co/sdhiFPaKlh — PAN (@Pan_Ecosystem) Aug 18, 2026

Signed IFTTT

16 Aug 2026, 18:26 UTC23 viewsread 3 September 2026

Open models do not just create more builders. They create more agent attempts. More experiments. More tool calls. More failed runs. More inference demand. More need to verify what actually happened. The open-source wave expands the execution market, not just the model market. https://t.co/Sg0KVkPqk7 — PAN (@Pan_Ecosystem) Aug 16, 2026

Signed IFTTT

14 Aug 2026, 13:26 UTC24 viewsread 3 September 2026

Agents need receipts. Not screenshots. Not vague logs. A real one should show: intent → compute → verification → payment → result. PAN is building that execution record. https://t.co/i2DVVPjjDD — PAN (@Pan_Ecosystem) Aug 14, 2026

Signed IFTTT

13 Aug 2026, 13:11 UTC26 viewsread 3 September 2026

Training compute is easy to spot. Big clusters. Big budgets. Big announcements. Agent compute will be harder to see. Small jobs. Always running. Spread across tools, apps, and users. Paid for one action at a time. The biggest compute market may be the one nobody sees. https://t.co/rI6uYqRSgb — PAN (@Pan_Ecosystem) Aug 13, 2026

Signed IFTTT

11 Aug 2026, 16:36 UTC21 viewsread 3 September 2026

Training compute is easy to recognize. Big clusters. Big budgets. Big announcements. Agent compute will be harder to see. Small jobs. Always running. Spread across tools, apps, and users. Paid for one action at a time. That market may be much larger than it looks. — PAN (@Pan_Ecosystem) Aug 11, 2026

Signed IFTTT

10 Aug 2026, 13:21 UTC19 viewsread 3 September 2026

Official Announcement Thrilled to partner with @XAgent_official the zero-code platform empowering anyone to Speak to Build custom AI Agents. As the Demand Layer for AI Compute PAN will explore seamless compute access agent-to-agent payments and scalable infrastructure for the https://t.co/mYgOtdDTjz — PAN (@Pan_Ecosystem) Aug 10, 2026

Signed IFTTT

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

“Pan” (@PanSystem), 19,155 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/PanSystem.

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.