Telegram RegisterThe public register of Telegram
Telegram profile photo for Peachpuff 加密幻想鄉

Channel

Peachpuff 加密幻想鄉

@peachpuffgensokyo

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

18subscribers

-1 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-1001656660703
TypeChannel
Username@peachpuffgensokyo
Created15 November 2021 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live8 October 2026
Measurements held3
Confirmed unchanged5 times, most recently 8 October 2026
On Telegramt.me/peachpuffgensokyo

Topic

Crypto & trading — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 76% 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

181918.57 August 2026 — 19 subscribers11 August 2026 — 19 subscribers29 August 2026 — 18 subscribers7 August 202629 August 2026
3 measurements spanning 22 days, net -1. 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–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 08:2618-1
11 Aug 2026, 16:4519no change
7 Aug 2026, 01:3919first reading

Engagement

11 posts held, back to 15 November 2021 — 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 11 posts for this entry, the most recent from 10 March 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Feb 2023, 01:48 UTC139 viewsread 11 August 2026

開空,開空,美國要在俄羅斯撤僑了,又一波政治危機,開空。

9 Jan 2023, 02:45 UTC117 viewsread 11 August 2026

月初開始把薪水的30%定投DOT,沒想到這麼快就見效了。上半年熊市就每月定投DOT了,如有新增幣種再來同步。

8 Nov 2022, 16:35 UTC149 viewsread 11 August 2026
Photo

中午在0.225接到了車厘子的補倉,太舒服了,今晚不看了,本單平倉,睡覺。

5 Nov 2022, 14:17 UTC108 viewsread 11 August 2026
Photo

接上一條,200U已經變成360U,外加一單合約,很舒服。

4 Nov 2022, 08:18 UTC183 viewsread 11 August 2026
Photo

輕倉200U車厘子五倍做多槓桿代幣,先拿到世界杯開始看看。

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

“Peachpuff 加密幻想鄉” (@peachpuffgensokyo), 18 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/peachpuffgensokyo.

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.