다행히 수술도 잘끝나고 회복중에 계십니다 어제오늘 이야기를 나누어 봤을때 법률적인 대응도 대응이지만 심리 상담 및 치료가 우선으로 보여 차주부터 진료 먼저받기로 약속하셨습니다. 주위에 계신 가족들 꼭 잘 챙기고 연락드리세요. 그리고 정말 일면식 없는 저에게 선의를 다들 베풀어주셔서 너무 감사드립니다. 내일중으로 연락주신분들께 감사인사 꼭 다 한분씩 드리겠습니다. 금요일 잘 보내세요
❤57👍15🙏1

Channel
@yeouidobi
On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,960subscribers
+503 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002917230747 |
|---|---|
| Type | Channel |
| Username | @yeouidobi |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/yeouidobi |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 15 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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 why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
4,440 average views per post against 1,960 subscribers — an engagement rate of 226.4%. Across the 374 registered channels in the same cohort — 1,007–3,130 subscribers, posting mainly in Korean — the middle half sit between 9.18% and 36.2%, with a median of 19.0%.
| Window | 30 days (16 July 2026 – 15 August 2026) |
|---|---|
| Posts measured | 21 of 23 published in the window (9 exact, 12 rounded by Telegram) |
| Views totalled | 93,194 |
| Mature posts only | 236.2% over 20 posts read at least 24h after publication |
| Subscribers | 1,960 measured 13 August 2026 |
| Cohort | b1000:kor · 374 channels · p10 5.32% · p25 9.18% · p50 19.0% · p75 36.2% · p90 60.3% |
| Position in cohort | 99.196th percentile · 11.9× the cohort median |
| Uncertainty | ±0.151% of the figure, from Telegram’s rounding |
| Post language | Korean · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 15 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:33 | 1,960 | +1 |
| 9 Aug 2026, 18:42 | 1,959 | +181 |
| 6 Aug 2026, 17:30 | 1,778 | +321 |
| 6 Aug 2026, 07:47 | 1,457 | no change |
| 6 Aug 2026, 03:37 | 1,457 | first reading |
23 posts held, back to 4 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 2 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 14 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 23 (4 August 2026 – 7 August 2026) |
| Views total | 93,194 |
| Reactions total | 609 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:35 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.
605 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 40.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 244 | 40.3% | |
| 🙏 | 161 | 26.6% | |
| ❤ | 157 | 26.0% | |
| 👍 | 18 | 2.98% | |
| 🖕 | 8 | 1.32% | |
| 🤬 | 6 | 0.992% | |
| 💩 | 5 | 0.826% | |
| 👎 | 2 | 0.331% | |
| 😱 | 2 | 0.331% | |
| 🎉 | 1 | 0.165% | |
| 🤝 | 1 | 0.165% |
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 14 of the 23 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 609reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 4 August 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.
다행히 수술도 잘끝나고 회복중에 계십니다 어제오늘 이야기를 나누어 봤을때 법률적인 대응도 대응이지만 심리 상담 및 치료가 우선으로 보여 차주부터 진료 먼저받기로 약속하셨습니다. 주위에 계신 가족들 꼭 잘 챙기고 연락드리세요. 그리고 정말 일면식 없는 저에게 선의를 다들 베풀어주셔서 너무 감사드립니다. 내일중으로 연락주신분들께 감사인사 꼭 다 한분씩 드리겠습니다. 금요일 잘 보내세요
❤57👍15🙏1
많은 분들이 연락을 주셨고 정말 감사드립니다. 지금 집 수습 및 입원수속 막 마치고, 돌아왔습니다. 몇몇분이 말씀하신거 때문에 굳이 더 잡음 안만들고 싶어서 정리 합니다. 우선 제가 이전부터 들었던 내용으로 구성하였기에 저도 좀 더 내용을 들어볼 예정입니다. 아버지께서는 금융권 IT에 계시고 기존에 PC계약을 대당 XX만원에 계약이 되어있다가 납품업체에서 메모리 가격 급등으로 인해 해당 단가로 납품을 거절하였고 재계약 단가를 올려서 재입찰을 해야했고, 실무진에서 가격을 올려 재계약해야 납품이 된다고 하셔서 가격을 높게 기재한 것이 낙찰이 되었다고 합니다. 기존 계약에 대해서 제대로 마무리가 안되거나 위약처리를 하지 못하고 신규 계약을 체결했다고합니다. 금년 운영체제 이슈에 따른 재교체 수요 + PC가격 인상에 따른 기존보다 높은 교…
❤70🙏17💩3😱2🤝1
정말 도움을 요청드리고 싶어 이렇게 올립니다. 정말 무거운 마음으로 이 글을 올리게됩니다. 저희 아버지는 대형회사에서 IT담당 임원으로 계십니다. 메모리가격 인상에 따라 계약을 재체결하는 과정에서 높은가격으로 재 계약을 진행하는 과정에서 제대로 이전 계약 마무리가 제대로 되지 못하고 진행이됨과 함께 최종 결재자가 되시면서 감사에서 계속해서 회사에 수백억에 가까운 손해를 입혔다고 압박을 받으시는것 같습니다. 결론이 나지 않았지만 수백억을 추징을 당할 수 있다는 압박감에… 좋지못한 선택을 시도하셨습니다. 혹시 이와관련하여 상담을 할 수 있거나 관련 전문가를 알고 계신분이 있다면 지나치치지마시고 한번만이라도 조언을 주시면 너무나도 감사하겠습니다. 제가 지금 당장 못하더라도 꼭 평생에 걸쳐서라도 보은하겠습니다 @netdebtzer0 로 연…
😭244🙏143❤13🖕8🤬6👎2💩2🎉1
반도체 투심에 대한 생각 1. 지금까지 반도체를 끌고온건 급격한 가격상승이었음 2. 그러면서 계속 상승한 GPM(매출총이익률)이 주가상승을 견인함 3. 그런데 반도체 컨콜에서 GPM은 이제 거의 상단에 도달했다고 하면서 투심이 꺾이고 있음 (특히 샌디스크, 마이크론) 4. 즉, 시장은 더 이상 가격은 유의미하게 오르지 않는다고 보고있는 것 5. 하지만, 이 논리에서 놓치는건 Q임. 일론머스크와 빅테크들이 전부 메모리가 부족하다고 말하고 있음 6. Q가 계속되고, 이전 사이클 최고 수준의 GPM이 유지된다면 생산을 늘리지 않을 이유가 없음 7. 하지만 애플이 보여준 것처럼, 공장 늘렸는데 갑자기 안산다고 할 수도 있음 8. 그걸 막기 위해서 LTA, SCA를 체결하고 선급금도 지급하고 있다고 봐야함 9. 매출 100에 GPM 85% 인것…
❤11
알트코인인줄 알았어요
수협증권도 나오나요? SH투자증권이네
❤1
✅ Sh수협은행, 상상인증권 품는다…연내 거래 완료 추진 https://n.news.naver.com/mnews/article/001/0016236515?sid=101
빚쟁이는 여의도로 pinned a photo
치킨5마리 이벤트 받아왔어요. 친구가 지금 카카오 사용자기준 현재 서비스 이용자 200명인데 500명 다음주까지 돌파하면 여기 채널에 치킨 5마리 뿌린다고 합니다. 치킨메뉴는 황올 아니면 허니콤보!! 인증방법은 링크타고 들어가서 카카카오 가입이후에 https://www.chartpalja.com 이름에 “텔레그램닉네임yeouidobi” 쓰고 가입하면됩니다. 실명 쓰면 바로 경품당첨되자마자 이름밝혀지는거야.. 친구들한테는 그냥 가입시키고 본인들만 이벤트 참여하면 확률이 올라가겠죠? 다음주 수요일까지 달려잇
❤2
빚쟁이는 여의도로 pinned a photo
주목!!!!!! 사주팔자 좋아하는 사람은 더 주목 제 친구가 이번에 서비스를 하나 런칭했어요. https://www.chartpalja.com 솔직히 맨날 사이드 플젝한다한다 했는데 드디어 처음 런칭했습니다. 스캠일까봐 제가 사주 앱 몇개깔아서 테스트 해봤는데 잘맞추네요. 내 사주넣고 차트를 보니깐 코스피가 다시 10,000 갈듯 코인러 및 주식쟁이들 맞춤으로 운세를 차트로 보여줌. 돈받은건 아닌데 트래픽 터지면 치킨좀 받아와볼게요. 들어가봐야겠지?
👍3
국민 연금이라는 뜻을 모르시는건 아니겠죠? 행정부 돈통이 아니라는 나쁜말은 멈춰줘~
❤2
Showing the 12 most recent of 23 posts we hold for @yeouidobi. 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 — 2,017 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.
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 2 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“빚쟁이는 여의도로” (@yeouidobi), 1,960 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/yeouidobi.
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.