DAPPOS 자고 일어난 사이 바낸퓨처도 가고, 2차 에드도 바로 뿌리고 레전드 감다살이네... https://x.com/dappOS_com/status/2087207380627128533?s=20
❤2
Signed inhu|기웃기웃

Channel
@inhu0
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,906subscribers
-8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002107531589 |
|---|---|
| Type | Channel |
| Username | @inhu0 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/inhu0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:07 | 5,906 | -9 |
| 9 Aug 2026, 01:51 | 5,915 | +2 |
| 6 Aug 2026, 10:00 | 5,913 | -1 |
| 6 Aug 2026, 03:31 | 5,914 | no change |
| 6 Aug 2026, 02:03 | 5,914 | first reading |
38 posts held, back to 3 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 9 pagesof 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 26 of 38 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 38 (3 August 2026 – 11 August 2026) |
| Views total | 20,493 |
| Reactions total | 51 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:43 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.
33 reactions across 16 posts, in 2 distinct kinds. The most used accounts for 97.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32 | 97.0% | |
| 👍 | 1 | 3.03% |
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 26 of the 38 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 51reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 3 August 2026 to 11 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.
DAPPOS 자고 일어난 사이 바낸퓨처도 가고, 2차 에드도 바로 뿌리고 레전드 감다살이네... https://x.com/dappOS_com/status/2087207380627128533?s=20
❤2
Signed inhu|기웃기웃
$DOS listed on Bithumb spot
❤1
Signed inhu|기웃기웃
액조디아 상장은 첨보네
❤2
Signed inhu|기웃기웃
[거래] BTC, USDT 마켓 신규 거래지원 안내 (CYS, ICNT, XAN, EDEN, AIOZ, ALLO) 🔗 공지사항 확인하기
Signed inhu|기웃기웃
DAPPOS (DOS) 바이낸스 알파 8월 10일 상장 https://x.com/BinanceWallet/status/2086355840311926814?s=20
❤2
Signed inhu|기웃기웃
L2 체인 NFT가 이렇게 잘 가는거 처음 보는거 같네요.
❤6
Signed inhu|기웃기웃
ARC 알파 챗 t.me/arcfrontrunners GIWA 알파 챗 t.me/giwaalphachat CA 올라오는거 사진 않고 분위기만 보고 있어여.
Signed inhu|기웃기웃
$STONKBROKER 생태계가 확실히 탄탄하네요. 금일 출시 한 STONKBROKER 생태계 DEX 프로젝트가 출시하자마자 ATH $10M, NFT FP 0.85ETH 달성했네요. (플랫폼은 아직 런칭도 안 함) https://x.com/MancerXYZ https://opensea.io/collection/chain-mancers (스나이핑 성공 한 지갑들은 대부분 $1.5M ~ $2M이 평단 인 듯) 다음 기대주는 $CLOCKIN https://x.com/clockincoin/status/2085072595712647664?s=20
❤4
Signed inhu|기웃기웃
아 국내 거래소 줴줴이야 BSB 레전드 설거지 코인 상장은 섭섭하네
❤2
Signed inhu|기웃기웃
DAPPOS 에어드랍 포털 공개 기존에 DAPPOS 활동에 참여했던 분들은 공식 페이지에서 지갑을 연결한 뒤, Phase 1 에어드랍 대상 여부와 할당량을 확인해 보시면 됩니다. https://dappos.com/airdrop https://x.com/dappOS_com/status/2084907647980216355
Signed inhu|기웃기웃
정말 도움을 요청드리고 싶어 이렇게 올립니다. 정말 무거운 마음으로 이 글을 올리게됩니다. 저희 아버지는 대형회사에서 IT담당 임원으로 계십니다. 메모리가격 인상에 따라 계약을 재체결하는 과정에서 높은가격으로 재 계약을 진행하는 과정에서 제대로 이전 계약 마무리가 제대로 되지 못하고 진행이됨과 함께 최종 결재자가 되시면서 감사에서 계속해서 회사에 수백억에 가까운 손해를 입혔다고 압박을 받으시는것 같습니다. 결론이 나지 않았지만 수백억을 추징을 당할 수 있다는 압박감에… 좋지못한 선택을 시도하셨습니다. 혹시 이와관련하여 상담을 할 수 있거나 관련 전문가를 알고 계신분이 있다면 지나치치지마시고 한번만이라도 조언을 주시면 너무나도 감사하겠습니다. 제가 지금 당장 못하더라도 꼭 평생에 걸쳐서라도 보은하겠습니다 @netdebtzer0 로 연…
❤1
Signed inhu|기웃기웃
이쯤해서 다시보는 블라드의 로빈후드 생태계 팔로우 목록 1. 캐시캣 2. 인덱스 3. 폰즈 4. Wen 근데 솔직히 냉정하게, 캐시캣말고는 너무 저시총이고.. Wen은 좀 뭐랄까 흠..좀..이긴함
❤1
Signed inhu|기웃기웃
Showing the 12 most recent of 38 posts we hold for @inhu0. 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 — 106,803 of 1,169,250entries 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.
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 7 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.
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.
“인후는 외롭지 않아요.” (@inhu0), 5,906 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/inhu0.
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.