Channel
@opendisco
On this record: Growth · Engagement · Posts · Citations · Cite this entry
219subscribers
+152 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004467061169 |
|---|---|
| Type | Channel |
| Username | @opendisco |
| Created | Between 1 June 2026 and 21 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/opendisco |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 09:24 | 219 | +119 |
| 22 Aug 2026, 07:58 | 100 | +33 |
| 21 Aug 2026, 17:45 | 67 | first reading |
20 posts held, back to 21 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 1 page 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 1 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 20 (21 August 2026 – 21 August 2026) |
| Views total | 15,890 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Aug 2026, 17:45 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.
🔧 수주공시 정정 · KC코트렐(119650) [2026-08-21 18:15] [원문보기] 👉 97.6억 · 매출대비 2.8% - 사유: 계약기간 종료일 변경 (원공시 2024-12-04) - 최근매출: 3,550.3억 - 상대: TECHNO ELECTRIC AND ENGINEERING CO. LTD. - 기간: 2022-08-08 ~ 2029-12-31
👤 5% 대량보유 · 부국증권(001270) [2026-08-21 17:26] [원문보기] 일반 보고 보고자 김중건 - 보유 약 364만 주 · 35.12% · 증감 780주 (0.00%p) - 보유목적: 경영권 영향 - 보고사유 - 보고자, 특별관계자의 유가증권시장에서의 주식 매매
Channel name was changed to «AI 공시알리미 by 유건호»
🛒 자기주식 취득 · 삼성전자(005930) [2026-08-21 17:20] [원문보기] 자기주식취득 결정 👉 취득예정 약 5,329만 주 · 15조원 발행주식총수 약 58.46억 주 대비 0.91% - 기간: 2026-08-24 ~ 2026-11-21 - 목적: 임직원 주식보상 · 유가증권시장을 통한 장내 매수
AI 공시알리미 by 유건호 pinned «📋공정공시 · 삼성전자(005930) [원문보기] 2026년 주주환원 예상 규모 및 시행 방안 정책 · 2024~2026년 3년간 총 Free Cash Flow의 50%를 주주환원 · 매년 9.8조원 정규배당, 잔여재원 발생시 추가 환원 시행 실적 · 2024~2025년 29.3조원 시행 (현금배당 20.9조원 · 자사주 매입/소각 8.4조원) 2026년 · 잔여 재원 약 90~110조원 규모로 예상 (3년간 총 FCF 50%에서 29.3조원 차감) ·…»
👤 5% 대량보유 · 미래산업(025560) [2026-08-21 17:07] [원문보기] 일반 보고 보고자 넥스턴앤롤코리아 - 보유 약 1,028만 주 · 37.02% · 증감 약 823만 주 (-3.38%p ▼) - 주요계약 2.70% · 약 75만 주 - 보유목적: 경영권 영향 - 보고사유 주식 질권 설정 계약
📋공정공시 · 삼성전자(005930) [원문보기] 2026년 주주환원 예상 규모 및 시행 방안 정책 · 2024~2026년 3년간 총 Free Cash Flow의 50%를 주주환원 · 매년 9.8조원 정규배당, 잔여재원 발생시 추가 환원 시행 실적 · 2024~2025년 29.3조원 시행 (현금배당 20.9조원 · 자사주 매입/소각 8.4조원) 2026년 · 잔여 재원 약 90~110조원 규모로 예상 (3년간 총 FCF 50%에서 29.3조원 차감) · 3분기 정규 분기배당 포함 30조원 내외 현금배당 시행 계획, 10월말 이사회에서 확정 예정 · 나머지 규모와 시행 방안은 2027년 1월말 이사회에서 최종 결정, 별도 발표 예정 👾 supported by AI (Opus 5.0)
🛎 주주총회소집(임시) · 진에어(272450) [2026-08-21 17:06] [원문보기] 2026-12-07 09:00 · 기준일 2026-11-10 · 합병 계약 체결 승인의 건 서울 강서구 마곡중앙로 143, 머큐어 서울 마곡 4층 연회장
🛎 주주총회소집(임시) · 에어부산(298690) [2026-08-21 17:06] [원문보기] 2026-12-07 10:00 · 기준일 2026-11-10 · 합병계약 체결 승인의 건 부산광역시 강서구 유통단지1로 57번가길 6 에어부산 사옥 8층 대강당
📊 실적(확정) · NH올원리츠(400760) [2026-08-21 17:03] [원문보기] 매출액 266.4억 (직전대비 -4.5%) 영업이익 149.8억 (직전대비 -20.2%) 당기순이익 -18.3억 (적자전환) - 사유: - 연결기준 세금과공과(재산세 등) 및 금융자산 미실현 평가손실 반영 연결 · 2026-01-01 ~ 2026-06-30
💰 배당 · NH올원리츠(400760) [2026-08-21 17:02] [원문보기] 부동산투자회사 금전배당 결정 👉 1주당 150원 · 시가배당률 4.9% · 총액 82.4억 - 기준일: 2026-06-30 - 지급: 정기주주총회일로부터 1개월 이내
🛎 주주총회소집(정기) · NH올원리츠(400760) [2026-08-21 17:01] [원문보기] 2026-09-21 09:00 · 기준일 2026-06-30 · 제13기 재무제표 승인의 건 · 제13기 현금배당 결의의 건 · 자본준비금 감액의 건 · 정관 변경의 건 · 외 2건 서울시 영등포구 국제금융로8길 2, 5층(여의도동) NH농협리츠운용 내 대회의실
Showing the 12 most recent of 20 posts we hold for @opendisco. 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.
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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“AI공시알리미 by 미래에셋증권 유건호” (@opendisco), 219 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/opendisco.
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.