Telegram RegisterThe public register of Telegram

Channel

Dappos 한국 커뮤니티 공지방

@Dappos_KR

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

2,534subscribers

+12 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-1003244919374
TypeChannel
Username@Dappos_KR
CreatedBetween 1 October 2025 and 31 January 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/Dappos_KR

Growth

2,5212,5342,527.56 August 2026 — 2,522 subscribers6 August 2026 — 2,522 subscribers6 August 2026 — 2,521 subscribers9 August 2026 — 2,523 subscribers12 August 2026 — 2,534 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +12. 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 2,519–2,536 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:152,534+11
9 Aug 2026, 12:362,523+2
6 Aug 2026, 14:222,521-1
6 Aug 2026, 05:332,522no change
6 Aug 2026, 02:052,522first reading

Engagement

22 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
22.1%
avg views ÷ 2,534 subscribers
Avg views / post
560
22 posts measured
Reaction rate
0.309%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 5 of 22 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 held22 (31 July 20267 August 2026)
Views total12,313
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:25 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

6 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
466.7%
👍116.7%
👏116.7%

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

Measured over the 22 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.

Recent posts

7 Aug 2026, 09:29 UTC89 viewsread 7 August 2026
Photo

📰 DappOS 데일리 브리핑 · 2026.08.07 (금) 오늘은 AI가 지갑을 직접 쥐기 시작한 소식들이 눈에 띄네요. ━━━ 같은 섹터 흐름 · AI ━━━ 🌐 AI 에이전트가 직접 자산을 다루는 흐름이 뚜렷해요. • 메타마스크도 뛰어든 AI 지갑 경쟁 • 네이버 AI탭, 월 사용자 1천만 돌파 • 고래, 12억 달러 BTC 매입 AI 에이전트에게 내 지갑 한도를 맡길 수 있을까요?

7 Aug 2026, 04:36 UTC≈1,300 views3 reactionsread 7 August 2026
Photo

🚀 dappOS, CoinMarketCap 상장 신청 완료 📋 신청 정보 접수 티켓 ID: 1443484 dappOS가 CoinMarketCap(CMC)에 정식으로 상장 신청서를 제출했습니다! 🔜 이제 남은 건 제출이 완료된 만큼, 다음 진행 상황은 업데이트되는 대로 바로 공유하겠습니다. ✨ 좋은 소식, 함께 기대해요 🔗공지원문보기

2👍1

7 Aug 2026, 04:02 UTC141 views1 reactionsread 7 August 2026
Photo

📢 사업을 하려고 코더가 될 필요는 없습니다 📌 xBubble Business Plan은 OPC가 직접 코딩하지 않아도 사업에 집중할 수 있게 해줍니다 🔎 어떻게 달라지나요 ✅ Bubble Up을 통해 맞춤형 SOP 코딩을 요청할 수 있습니다. ✅ Bubble Engine이 뒤에서 SOP를 개발하고, 최적화하고, 계속 개선해 나갑니다. ✅ 코드 작성, 기술적 문제 디버깅, 복잡한 워크플로우 수동 관리는 xBubble이 대신 처리합니다. 📌 그래서 남는 건 ✅ OPC는 기술적 복잡함을 신경 쓸 필요 없이 오직 사업 목표에만 집중하면 됩니다. 👉 코딩 복잡함은 줄이고, 사업을 키우는 데 더 집중하세요. 🔗원문내용보기

1

6 Aug 2026, 09:59 UTC180 views1 reactionsread 7 August 2026
Photo

📰 DappOS 데일리 브리핑 · 2026.08.06 (목) 오늘은 AI 쪽에서 하드웨어·현장 적용 소식과 토큰 프로젝트 정리 소식이 함께 나왔어요. ━━━ 같은 섹터 흐름 · AI ━━━ 🌐 AI는 반도체·농기계 실물 확장과 토큰 정리가 엇갈렸어요. • 대동, AI 트랙터 '간편모드' 추가 • TSMC 3나노 증산, AI 반도체 주도권 • 엘리자OS 재단 해산에 20% 급락 AI 섹터에서 실물 인프라와 토큰 프로젝트, 여러분은 지금 어느 쪽에 더 관심이 가시나요?

1

5 Aug 2026, 10:59 UTC276 viewsread 7 August 2026
Photo

🚨 DAPPOS 사칭(스캠) 사이트 주의 안내 🚨 현재 DAPPOS를 사칭한 피싱 사이트 및 스캠 링크가 유포되고 있습니다. ⚠️ 아래 사항을 꼭 확인해 주세요! ✔️ 공식 채널에서 공유된 링크만 이용하기 ✔️지갑 연결 전 URL 다시 한번 확인하기 ✔️출처가 불분명한 DM이나 링크는 클릭하지 않기 에어드롭 시즌에는 피싱 사이트가 많이 등장하는 만큼, 반드시 공식 DAPPOS 채널 및 커뮤니티을 통해 접속하시기 바랍니다. 모두 안전하게 이용하시고 피해 없으시길 바랍니다!

5 Aug 2026, 09:57 UTC232 viewsread 7 August 2026
Photo

📰 DappOS 데일리 브리핑 · 2026.08.05 (수) 오늘은 dAppOS의 사용자 경험 실험과 AI 섹터의 비용·감시·결제 인프라 소식이 함께 들어왔어요. 📌 dAppOS, "결과만 말하는" Web3 📍 복잡한 절차 대신 원하는 결과만 말하면 되는 환경을 지향한다는 이야기라, 지갑·체인 조작에 지쳤던 이용자에겐 눈여겨볼 만한 방향이에요. ━━━ 같은 섹터 흐름 · AI ━━━ 🌐 비용과 개방성, 그리고 AI가 직접 쓰는 인프라가 화두예요. • 딥시크 V4, 입력비 7분의 1 • AI 4개로 준비금 실시간 감시 • 클플, AI 에이전트 지갑 착수 여러분은 "원하는 결과만 말하는" 방식이 정말 Web3 진입장벽을 낮출 거라고 보시나요?

5 Aug 2026, 09:44 UTC44 viewsread 7 August 2026
Forwarded from @basketballcryptoPhoto

🎁 DAPPOS x 농직통 (농구직접통역) AMA! 이번주 수요일 저녁 10시에 DAPPOS 테일러님과 함께 AMA를 진행합니다. 장소는 트위터에서할지 텔레에서 할지 고민즁. 사전에 커뮤니티 입장 해두어야겠죠?? 별도로 이 포스팅에 댓글 남겨주시는 분들은 추첨 시 1표 더 넣어서 돌리겠습니다. (안그래도 경쟁 안빡센데 한표 더 넣고 돌리면??) 📌 사전에 커뮤니티 입장 및 팔로우 해두기 농구 공지방 / 채팅방 / 트위터 DAPPOS 공지방 / 채팅방 🎉 AMA 보상 ☕️ 메가커피 아메리카노 100명 🍕 파파존스 피자 10명 🍗 치킨 + 콜라 세트 10명 ※ 모든 보상은 쿠포니봇(Coupony Bot)​을 통해 지급되며 영업일 기준 5일 이내로 지급이 완료될 예정입니다.

5 Aug 2026, 07:47 UTC≈1,650 viewsread 7 August 2026
Photo

📢 DAPPOS 에어드랍 포털 오픈!! 📌 DAPPOS 에어드랍 포털이 이용 가능해졌습니다. 이제 Phase 1 에어드랍 체크가 열렸습니다. ⚠️ 반드시 공식 DAPPOS 링크만 이용해 주세요. ☑️ 아래 링크에서 바로 확인하세요. 👉에어드랍 포털 바로가기 🔗공지 원문 보기

5 Aug 2026, 06:00 UTC628 viewsread 7 August 2026
Photo

🔥 Dappos, 현재 Pre-TGE 프로젝트 마인드쉐어 1위! #Dappos #PreTGE #Mindshare 👉🏻 마인드쉐어 확인

4 Aug 2026, 09:55 UTC210 viewsread 7 August 2026
Photo

📰 DappOS 데일리 브리핑 · 2026.08.04 (화) 오늘은 AI 쪽 소식이 눈에 띄어요, 정책부터 투자 전략까지 함께 훑어볼게요. ━━━ 같은 섹터 흐름 · AI ━━━ 🌐 정부 투자와 월가 전략까지, AI 이야기가 넓게 퍼지고 있어요. • 제조AI에 민관 20조원 투입 • JP모건, 헬스케어 비중 추가 제안 • 美 ‘코인 주담대’ 정치권 논의 여러분은 오늘 AI 소식 중 어떤 게 가장 눈에 들어오셨나요?

4 Aug 2026, 08:27 UTC196 views1 reactionsread 7 August 2026
Photo

📢 DAPPOS 8월 개발 업데이트! 📌 이번 업데이트는 크게 두 축입니다. 누구나 쉽게 쓰도록 요금제를 손봤고, Agent와 봇을 자동으로 굴리는 기반을 깔았습니다! 🤩시스템 · 제품 업그레이드 ▫️ 개인 요금제 확대 — 월 10달러부터, 초대 코드 없이 바로 구매 ▫️공개 SOP 1,000개 이상 이용 가능 ▫️ BNB Agent Studio + 예약 실행 인프라 — 반복 작업 · 텔레그램 발송 · 외부 서비스 연결 ▫️멀티모달 과금 개선 — 음성·영상·디지털 휴먼에서도 크레딧 차감 일관성 강화 ✏️ Bubble Engine SOP 학습 ▫️ 예측 시장 DApp — 요청 한 번으로 생성 ▫️ 실시간 디지털 휴먼 — 음성·영상 결합 라이브 방송 ▫️ 텔레그램 봇 자동화 — Bubble Code로 빠

👏1

4 Aug 2026, 05:25 UTC97 viewsread 7 August 2026
Forwarded from @fireant_cryptoPhoto

✏️ Dapp OS는 선물시장에서 약 380M FDV를 기록중 DappOS가 상장을 앞두고 선물마켓에 상장했습니다. 딱 생각했던 밸류가 400M인데 사람 눈 다 비슷비슷한가봅니다. 선물시장에서 이정도 받고, 상장 공지와 함께 좀 더 올라주면 헷징잡기 아주 딱 좋을듯. 진짜 TGE 할만한 프로젝트가 얼마 안남았는데 DappOS가 스타트 끊어주기를! 선물시장 구경가기

Showing the 12 most recent of 22 posts we hold for @Dappos_KR. 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 — 37,572 of 1,350,102entries 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

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

Named by 13 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.

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.

“Dappos 한국 커뮤니티 공지방” (@Dappos_KR), 2,534 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Dappos_KR.

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.