🟢 $80,000 @bitcoin_price
❤1

Channel
@PASACREW
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,930subscribers
-1,057 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001680904256 |
|---|---|
| Type | Channel |
| Username | @PASACREW |
| Created | 29 October 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/PASACREW |
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 12 September 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 01:58 | 5,930 | -12 |
| 5 Nov 2026, 15:58 | 5,942 | -2 |
| 2 Nov 2026, 17:29 | 5,944 | -7 |
| 30 Oct 2026, 16:54 | 5,951 | -16 |
| 27 Oct 2026, 16:36 | 5,967 | -7 |
| 25 Oct 2026, 02:18 | 5,974 | -15 |
| 22 Oct 2026, 12:40 | 5,989 | +3 |
| 19 Oct 2026, 05:08 | 5,986 | -10 |
| 16 Oct 2026, 12:56 | 5,996 | -20 |
| 13 Oct 2026, 16:49 | 6,016 | -36 |
| 7 Oct 2026, 20:58 | 6,052 | -54 |
| 30 Sept 2026, 20:55 | 6,106 | -268 |
| 16 Sept 2026, 15:59 | 6,374 | -124 |
| 12 Sept 2026, 13:00 | 6,498 | -116 |
| 8 Sept 2026, 06:01 | 6,614 | -170 |
| 3 Sept 2026, 10:28 | 6,784 | -138 |
| 30 Aug 2026, 23:08 | 6,922 | -82 |
| 27 Aug 2026, 17:34 | 7,004 | +1 |
| 25 Aug 2026, 03:18 | 7,003 | +20 |
| 21 Aug 2026, 09:29 | 6,983 | first reading |
150 posts held, back to 5 August 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 14 pages of Telegram’s post history, 20 posts per page.
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 14 of 22 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 150 (5 August 2026 – 4 November 2026) |
| Views total | 8,283 |
| Reactions total | 34 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 01:09 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,280 reactions across 113 posts, in 6 distinct kinds. The most used accounts for 76.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 984 | 76.9% | |
| 👍 | 233 | 18.2% | |
| ⚡ | 30 | 2.34% | |
| 😢 | 15 | 1.17% | |
| 🤬 | 11 | 0.859% | |
| 🤣 | 7 | 0.547% |
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 134 of the 150 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 1,428 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 150 most recent posts we hold, published 5 August 2026 to 4 November 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.
Telegram’s own ‘edited’ marker: 2 of 22 posts held from the last 30 days (9.09%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🟢 $80,000 @bitcoin_price
❤1
비트코코... 해치운건가...?
🟢 $79,000 @bitcoin_price
😄peaqOS x 삼성 스마트싱스 연동 출시! 이제 peaqOS를 탑재한 로봇들이 삼성 스마트싱스로 직접 문을 열고 기기를 제어할 수 있게 되었습니다! 💡핵심 요약 삼성 스마트싱스의 생태계와 peaq의 코디네이션 기술이 만나, 로봇이 스마트홈 환경에서 맡은 작업을 완수하는 환경이 열렸습니다 🦾어떻게 작동하나요? 머신은 매번 잠금을 해제할 때마다 발급되는 일회용 키와 자체 온체인 신원을 사용해 작동 • peaqOS: 머신의 고유 신원 증명 및 작업 조율 제공 • 삼성 스마트싱스: 스마트홈 및 빌딩 IoT 기기 제어 담당 🏢 무엇이 달라지나요? [AS-IS] - 기존 모든 스마트 도어락은 허가된 대상만 통과 가능. - 로봇들은 문을 지나가지 못하거나, '사람의 계정'을 빌려 들어가야 했음. [TO-BE] - 빌딩 앱에 별도의 …
❤1
다이나믹하네....
👍1
🟢 $78,000 @bitcoin_price
코인 망했나..?
🔴 $76,000 @bitcoin_price
구시대 유물 MIL.K CU 랑 지속적으로 협업(?) 중인데, 밀크앱에서 CU 3회 방문 미션하고 (30m 근방가서 방문 확인. 물건 안사도됨) 받기 버튼 누르면 CU 앱으로 이동되고 CU 앱에서 포키 받을 수 있음.
❤2
뭐 이래저래... 지금 AI로 뭔가 하시는 분들 코딩에서 SNS 자동화쪽으로 대부분 눈길을 많이 돌리신 것 같긴 한데.. 그 이유가 AI 슬롭이라고 흔히들 말하는 저품질 영상과 사진들이 어플리케이션 단에서도 만연해 있기 때문.. (여기서 어플리케이션은 사용자들이 사용하는 무언가를 말함) 스토어 앱일 수도 있고, 웹앱일 수도 있는 그러한 것들이 쏟아져 나와서 이미 만들고 싶어하는 앱들이 검색해보면 수십 수백개가 앱스토어에 있음. 그렇다면.. 사람이 일하기 싫은 본질은 무엇일까? "그냥 즐기고 싶다" 일텐데 또 그것의 본질은 "소비"가 바닥에 있음. 집에서 아무것도 안하고 쉬어도 침대가 있어야 하고 눕다보면 더 좋은 침대가 필요하고.. 헌데 AI로 그런건 만들 수 없으니 결국 AI로 소비할 수 있는 무언가를 만드는 것은 "컨텐츠" …
❤1
강릉 출발해서 양양 들름 낙산사 좋으네
👍3
강릉 그란데마레 걸어서 3분 사천해변 요기어때 , 야놀자보다 myrraltrip 이 제일 쌈 씨뷰 보려면 3층 이상 해야되고 제대로 보려면 4층 이상 (4층에서 찍은 사진) https://accommodation.myrealtrip.com/union/products/3187669?checkIn=2026-11-04&checkOut=2026-11-05&roomCount=1&adultCount=2&childCount=0&providerRoomId=&segment=&isDomestic=true 레퍼럴 있거나 그러지 않음
❤6
Showing the 12 most recent of 150 posts we hold for @PASACREW. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 registered channels — 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.
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.
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.
This channel appears in 22 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“PASA 공지방” (@PASACREW), 5,930 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/PASACREW.
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.