Telegram RegisterThe public register of Telegram
Telegram profile photo for Afeng的加密日记

Channel

Afeng的加密日记

@PEAKFIRE

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

13,469subscribers

+103 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-1001500820649
TypeChannel
Username@PEAKFIRE
Description只是记录炒币赚与亏,谨慎跟单,亏损自负 没有任何逻辑和思维,完全是看自己的感觉来 所以一切都是DYOR 赚钱不易,且行且珍惜 Owner&Marketing: @Afeng_sir @miuvikiii TW:https://x.com/aa_AFeng
CreatedBetween 1 January 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/PEAKFIRE

Growth

13,36613,46913,417.57 August 2026 — 13,366 subscribers7 August 2026 — 13,366 subscribers7 August 2026 — 13,370 subscribers8 August 2026 — 13,376 subscribers9 August 2026 — 13,420 subscribers10 August 2026 — 13,439 subscribers11 August 2026 — 13,438 subscribers12 August 2026 — 13,444 subscribers14 August 2026 — 13,439 subscribers15 August 2026 — 13,452 subscribers17 August 2026 — 13,469 subscribers7 August 202617 August 2026
11 measurements spanning 10 days, net +103. 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 13,351–13,484 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 10:1413,469+17
15 Aug 2026, 17:4913,452+13
14 Aug 2026, 09:3813,439-5
12 Aug 2026, 22:1513,444+6
11 Aug 2026, 22:1613,438-1
10 Aug 2026, 20:4113,439+19
9 Aug 2026, 21:1613,420+44
8 Aug 2026, 18:0613,376+6
7 Aug 2026, 19:4813,370+4
7 Aug 2026, 12:3113,366no change
7 Aug 2026, 12:2513,366first reading

Engagement

40 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
27.1%
avg views ÷ 13,469 subscribers
Avg views / post
3,650
40 posts measured
Reaction rate
0.393%
reactions ÷ views · ER floor
Posts in window
40
of 40 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 38 of 40 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held40 (3 August 202617 August 2026)
Views total145,860
Reactions total546
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 19:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
2,700
Videos
50
Links
766

Lifetime counters from Telegram’s own channel header, read 17 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

546 reactions across 38 posts, in 16 distinct kinds. The most used accounts for 45.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
25045.8%
🤣7714.1%
👍6511.9%
🌚478.61%
😁254.58%
👀183.30%
😨132.38%
👏112.01%
🤔112.01%
🔥91.65%
🙏50.916%
🥰50.916%
40.733%
🐳30.549%
🦄20.366%
❤‍🔥10.183%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 38 of the 40 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 546reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 3 August 2026 to 17 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

17 Aug 2026, 14:30 UTC≈1,400 views6 reactionsread 17 August 2026

挂了12m的单 明早收菜

😁51

Signed Afeng Feng

17 Aug 2026, 14:00 UTC≈1,680 views4 reactionsread 17 August 2026

之前那个叼毛暗示了 关注就飞了

2😁2

Signed Afeng Feng

17 Aug 2026, 14:00 UTC≈1,740 views3 reactionsread 17 August 2026

basecat吃了一波 0xb200000000000000000000b8d3746d2e56596578 这个感觉也有机会。那个叼毛关注就是10m+ 赌博了

😁21

Signed Afeng Feng

15 Aug 2026, 06:38 UTC≈3,010 views13 reactionsread 17 August 2026

叙事已死, 实用当立 BSC正在把MEME带向实用 GOOD

🤣7👍41🌚1

Signed Afeng Feng

15 Aug 2026, 06:34 UTC≈2,990 views12 reactionsread 17 August 2026

utility CAN WIN

👍92🌚1

Signed Afeng Feng

14 Aug 2026, 14:21 UTC≈3,330 views26 reactionsread 17 August 2026

utility token 将会在bsc达到它之前在其他公链达不到的高度 cz想要 cz得到 五年前的愿望 如今实现

👍13🤣54😨3🔥1

Signed Afeng Feng

14 Aug 2026, 14:19 UTC≈3,310 views27 reactionsread 17 August 2026

0xede00776439f9c49c592e43eee34777a51847777 cz会买入

15🌚4🤣42🔥2

Signed Afeng Feng

11 Aug 2026, 09:45 UTC≈4,760 views16 reactionsread 17 August 2026
Sticker

Sticker, posted without a caption

🤔8👀32🌚1🐳1🤣1

Signed Afeng Feng

10 Aug 2026, 17:31 UTC≈4,690 views23 reactionsread 17 August 2026
Sticker

Sticker, posted without a caption

👀10😁7🌚3🤔21

Signed Afeng Feng

9 Aug 2026, 14:36 UTC≈4,980 views59 reactionsread 17 August 2026

滴水之恩涌泉相报。

43🌚11👍2🤣2❤‍🔥1

Signed Afeng Feng

9 Aug 2026, 14:34 UTC≈4,810 views62 reactionsread 17 August 2026

打回去每个人0.3 请你们吃大餐 感谢

45😁9🙏5🦄2🌚1

Signed Afeng Feng

9 Aug 2026, 14:33 UTC≈4,620 views16 reactionsread 17 August 2026

就三个人给我打 了0.01。好人啊 我草。

13👍3

Signed Afeng Feng

Showing the 12 most recent of 40 posts we hold for @PEAKFIRE. 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,448,511 of 1,480,975entries 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.

Appears in Telegram’s recommendations for other channels

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.

Btok.com Official Channel
@BTOKOFFICIALCHANNEL · 333,996
Telegram ranks this channel #60 of 71 here — alongside 70 others — read 17 August 2026
Baby Doge 公告
@BabyDogeAnnZH · 90,151
Telegram ranks this channel #66 of 85 here — alongside 84 others — read 17 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Afeng的加密日记” (@PEAKFIRE), 13,469 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/PEAKFIRE.

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.