오랜만에 하는 TGE 상장 1. TGE 상장의 정석대로 dex 뜨자마자 120m 정도에서 긁음 2. 생각 이상으로 잘 가서 150m 정도에 다 팖 3. Legion 세일 물량 떨어져서 가격 레운 4. 다시 주워볼 만하다 생각해서 평단 125m 맞춰서 줍고 업비트 보냄 5. 135m (192원~194원)에 매도 원래 제 TGE 상장 가이드라인은 dex 뜨자마자 매수하고 대가리 깨고 업비트 보내서 파는 건데 이번에는 처음 샀을 때 꽤 잘 오르고, 장도 안 좋아서 그냥 따리 한 셈 치고 그냥 팔았네유 다시 살 기회 준 건 운이 좋았던 거긴 한데, 지금 같은 장에는 업비트 보내기 전에 파는 것도 나쁘지 않은 듯듯 맥모닝 gud

Channel
Pache Punch
@pachepunch
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,959subscribers
-31 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 | -1001869932358 |
|---|---|
| Type | Channel |
| Username | @pachepunch |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/pachepunch |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 00:38 | 2,959 | +3 |
| 3 Sept 2026, 21:58 | 2,956 | -2 |
| 31 Aug 2026, 04:12 | 2,958 | -3 |
| 27 Aug 2026, 19:18 | 2,961 | -5 |
| 24 Aug 2026, 20:54 | 2,966 | -8 |
| 21 Aug 2026, 09:12 | 2,974 | -1 |
| 18 Aug 2026, 13:49 | 2,975 | -7 |
| 15 Aug 2026, 18:17 | 2,982 | -2 |
| 12 Aug 2026, 01:32 | 2,984 | -5 |
| 9 Aug 2026, 11:32 | 2,989 | -3 |
| 6 Aug 2026, 16:31 | 2,992 | +2 |
| 6 Aug 2026, 05:02 | 2,990 | no change |
| 6 Aug 2026, 02:37 | 2,990 | first reading |
Engagement
19 posts held, back to 6 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 3 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
8 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348307660271788404 | 3 | 37.5% | |
| custom 6141138754594671873 | 3 | 37.5% | |
| custom 5348236286505265186 | 2 | 25.0% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 3 of the 19 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 6 July 2026 to 4 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
QUID - 체인: base - CA: 0x1a44233fae8d50f1aeb3a5d58dd426ff4814cb53 - 총 공급량: 1B / 초기 유통량: 142.9M 가량 - 상장 시간/TGE 시간 (금일 오후 10시) - 바이낸스 알파/크라켄/비트겟 08.04 22:00 - 빗썸: 08.04 22:00 (동시간대 META, USDG 상장도 있음(연기될듯)) - 업비트: 08.04 23:00 - 세일 관련 - 세일가: $0.045 (FDV 45M) - 세일 물량: 50M (Total Supply 5%) - 현재 장외가 - https://trade.aspecta.ai/projects/usdt/Squid - 1 key = 10 QUID * liq pool은 pancakeswap v3로 들어갈 예정
Sticker, posted without a caption
이제 아무도 안 하는 따리 바낸에서 샀으면 베이스는 막혀서 븐브로 나간 다음 스타게이트 쓰면 됨 https://stargate.finance/ 물량 들어오는 꼬라지 보니까 이번에도 연기될 거 같네
custom 53483076602717884043
주식 덕분인지 하리 볼륨 중 HIP-3가 차지하는 비중이 63%까지 올라옴 이제 xyz가 본체다 😕
custom 53482362865052651862
콘플럭스 원상관련 참고사항 텔레그램 망령들은 기억할텐데, 4월 15일 상장된 칸톤의 경우에도 같은 사유로 갑자기 상장이 멈춘 적이 있습니다. (당시 공지) 이때 어땠는지 알면 참고가 되겠지? 이때는 오후 2시 상장발표 -> 오후 3시 50분쯤 무기한 연기를 때린 후 다음날 오후 2시에 다시 상장 공지가 떴던 바가 있어요. (한시간 후인 3시에 후딱 상장했음) 한줄요약 : 재수없으면 오늘 내에 상장 안될수도 있겠구나~ 하고 참고 하시면 됩니다 (안참으면 어쩔건대)
아침에 일이 있어서 이제 시장을 보는데 재밌는일이 있었네요 이 쪽으로는 이 분이 탑이라서 글 여러개 링크 첨부합니다 https://t.me/Web3LearningWithInger/1930 https://t.me/Web3LearningWithInger/1932 https://t.me/Web3LearningWithInger/1934 https://t.me/Web3LearningWithInger/1939
1위가 바뀐레후
CXMT 상장 완료 장중 중국 A주 시총 1위 달성, 53위안 돌파($7.7달러) 시 중국 상장사 전체 시총 1위 달성 (현재 1위 텐센트) 한국, 일본, 중국 모두 메모리 관련 기업이 시총 1위가 될 수 있음
1년인가 2년 전에 네사 노드몽현 돌렸던 거 14계정 해서 150불 나옴 서버비도 못 뽑았다 🤒
custom 61411387545946718733
어제부터 개쳐오른 거 머임
https://t.me/UPBITDEPOSIT 업비트 원상 집금을 자동으로 추적해주는 봇을 만들어봤습니다 잘 작동할지는 오늘 봐야할듯 일단 evm이랑 sol 지원합니다
Showing the 12 most recent of 19 posts we hold for @pachepunch. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@cryptopangpang · 11,5591 post싸이버트럭
@cybertruck666 · 10,4721 post검멀레 마을회 (GMR Village Hall)
@gmrvillage · 6,3851 postZi존파워잼민
@jammin0720 · 3,5741 post종명이의 딸깍
@jh_6598 · 8,9311 postDegen Guy
@justdegenguy · 8,6111 postAI 구독료 벌어야하는 레오
@leo_autotrading · 1,1501 postPnpm
@pnpmarchive · 6521 post사랑방🍬(CRYPTO ALPHA)
@Sarangbang_Crypto · 7,8121 post
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Pache Punch” (@pachepunch), 2,959 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pachepunch.
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.