Telegram RegisterThe public register of Telegram

Channel

김피카썬더볼트

@Pika_Kim

On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry

1,632subscribers

-2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003458583744
TypeChannel
Username@Pika_Kim
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Pika_Kim

Growth

1,6321,6361,6346 August 2026 — 1,634 subscribers6 August 2026 — 1,634 subscribers6 August 2026 — 1,636 subscribers9 August 2026 — 1,635 subscribers12 August 2026 — 1,632 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net -2. 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 1,631–1,637 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:051,632-3
9 Aug 2026, 23:361,635-1
6 Aug 2026, 14:201,636+2
6 Aug 2026, 07:201,634no change
6 Aug 2026, 02:051,634first reading

Engagement

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

ERR · 30 days
40.4%
avg views ÷ 1,632 subscribers
Avg views / post
659
29 posts measured
Reaction rate
0.318%
reactions ÷ views · ER floor
Posts in window
29
of 29 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 13 of 29 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 7 August 2026
Posts held29 (31 July 20267 August 2026)
Views total19,097
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:53 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.

Reaction mix

17 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 52.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
952.9%
😱741.2%
🤔15.88%

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 13 of the 29 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 30reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 29 most recent posts we hold, published 31 July 2026 to 7 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.

Advertising

Ad load
3.45%
1 of 29 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
635
over 1 measured post
Median views · rest
633
over 28 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 29 most recent posts we hold, published 31 July 2026 to 7 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

7 Aug 2026, 14:00 UTC288 viewsread 7 August 2026

오늘도 얼추 먹여준 것 같네요 얘기 들어보니 흠..

7 Aug 2026, 13:27 UTC185 viewsread 7 August 2026
Forwarded from @pannpunchPhoto

8.05~8.07 상장 모음 GRVT, UB, CAP, KMNO, BSB 전반적인 기조 - 현선 0 - 혹은 낮은 현선 괴리 1~2%띠기 잡풀 - 업비트 시작 갭 별로 없는 편 - 1% 띠기 - 거래량 바닥 - 빗썸의 경우 호가 x - UB/BSB의 경우 거래 시작 전 호가가 없는 수준이라 2~3% 위에 걸어둔 사람이 피뢰침 먹고 이후 노갭 (소액) - 업비트의 경우 거래 시작 후 후펌이 자주 나옴 - 후펌으로 현선 괴리가 벌어지는 경우도 노션 복기 ⤵️ $GRVT 상장 (Up) $UB 상장 (Bit) $CAP 상장 (Up) $KMNO 상장 (Up) $BSB 상장 (Up/Bit) 이번주동안 상장만 총 8차례했네요 모두 크게 특기사항 없이 비슷한 양상이었고, 차트 궁금하신 분들만 노션 보시면 될 것 같네요 따저씨들도 더 이

7 Aug 2026, 12:41 UTC324 viewsread 7 August 2026

시발 우리집에 불난거 모르고 헤헤거리고 있었내 개같은거;

7 Aug 2026, 12:41 UTC324 viewsread 7 August 2026

김치 프리미엄 : -0.14% USD/KRW : 1,409.4원 USDT/KRW : 1,407.4원

7 Aug 2026, 12:06 UTC375 views4 reactionsread 7 August 2026

약속 잡을 때 (청모라던지 다른 모임이라던지..) 0월 0일 괜찮아? 질문 받으면 "어... 그 날 일이 있는지 그 날 가봐야 해서..." 하는거 나뿐이야? 용기 내서 막상 나갔더니 상장떠서 당일 파토내거나 앞에서 폰만 만지고 있는거 나뿐이야?

4

7 Aug 2026, 12:01 UTC396 views2 reactionsread 7 August 2026
Photo

막줄은 킥이네... 어제 쓰신건가...

2

7 Aug 2026, 12:00 UTC386 viewsread 7 August 2026

https://www.teumjournal.com/post/98c5b35d-7d4d-48f2-ac16-d06efc196a0e?letter=sent 금일의 큐레이션 돈으로 어디까지 행복해질 수 있는 것일까에 관하여. 따리꾼들이라면 모두 공감하지 않을지.

6 Aug 2026, 13:37 UTC518 views1 reactionsread 7 August 2026

케이스가 비슷해서 따로 복기할건 없고, 요새 계속 반복되는 패턴 같은데.. 기존에 1시간-1시간 30분 전이 생따의 저점이었다면 지금은 최대3-40분전에(어쩌면 막차까지) 크게 딥 한 번 주고 상장해서 국내 역프 찍은다음에 해외에서 약 20분 정도 후 가격 견인해서 올리는 느낌. 지금까지의 얕은 데이터로는 3-40분 전에 매수 + 쌩 던지고 롱 (후펌분 먹기) + 적당히 롱 익절 후 음봉 박히는 지점에서부터 숏해서 홀딩이 무적인 것 같은데.. 좀 더 지켜볼 필요 있을 것 같음. 일단 오늘 테스트로 쳐본 CAP 후펌숏은 성공적이었음. 하지만 전력으로 하는건 굉장히 비추함. 10번 성공해도 1번으로 다 잃을 수 있는 모든걸 잃을 수 있는 아주 극 리스키한 전략이라고 생각.

🤔1

4 Aug 2026, 14:05 UTC803 views1 reactionsread 7 August 2026

바낸 알파에서 샀으면 개인ㅇ지갑을 반드시 거쳐라 아니면 돈이 공중에서 사라진다

1

Showing the 12 most recent of 29 posts we hold for @Pika_Kim. 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 — 205,317 of 1,160,990entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“김피카썬더볼트” (@Pika_Kim), 1,632 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Pika_Kim.

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.