유사 손흥민, 의료기기 산신령, CFA Charterholder, 2권을 집필한 작가, 독도명예주민, Mensan, Rescue/Master Diver, Classic Suit, 생활체육인, 그리고 월급쟁이 직장인
본 채널의 게시물은 투자권유가 아닌 기록과 산업에 대한 단순의견입니다. 반박시 선생님 말씀이 절대적으로 옳습니다.
게시물의 내용은 부정확할수 있고 매매의 손실은 거래당사자의 책임이며, 법적 책임소재의 증빙자료로 사용될 수 없습니다.
Created
25 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
Observations
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.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (5 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 83 comparable posts for this entry, running 4 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Recorded under the key clone_mutual, last confirmed 11 November 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.
Growth
57 measurements spanning 96 days, net -75. 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 12,017–12,189 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)
Subscribers
Change
9 Nov 2026, 21:01
12,054
-3
8 Nov 2026, 15:09
12,057
+1
7 Nov 2026, 07:21
12,056
+11
6 Nov 2026, 05:45
12,045
+3
5 Nov 2026, 07:16
12,042
-4
4 Nov 2026, 03:08
12,046
-9
2 Nov 2026, 03:19
12,055
-1
1 Nov 2026, 02:50
12,056
-1
31 Oct 2026, 02:50
12,057
+20
29 Oct 2026, 03:58
12,037
-2
28 Oct 2026, 00:25
12,039
-1
26 Oct 2026, 22:46
12,040
-2
25 Oct 2026, 19:17
12,042
-2
24 Oct 2026, 22:40
12,044
-1
23 Oct 2026, 19:27
12,045
-5
22 Oct 2026, 22:11
12,050
-6
21 Oct 2026, 21:00
12,056
-4
20 Oct 2026, 14:35
12,060
-1
19 Oct 2026, 13:38
12,061
-3
18 Oct 2026, 13:36
12,064
first reading
Engagement
164 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 65 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
13.0%
avg views ÷ 12,054 subscribers
Avg views / post
1,560
63 posts measured
Reaction rate
0.464%
reactions ÷ views · ER floor
Posts in window
63
of 164 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 11 November 2026
Posts held
164 (4 August 2026 – 11 November 2026)
Views total
98,559
Reactions total
457
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 08:54 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.
What this channel posts
Photos
118
Videos
1
Links
58
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
1,112 reactions across 159 posts, in 5 distinct kinds. The most used accounts for 38.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
424
38.1%
❤
306
27.5%
😁
182
16.4%
😢
141
12.7%
🤯
59
5.31%
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 162 of the 164 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,132 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 164 most recent posts we hold, published 4 August 2026 to 11 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.
Recent posts
Telegram’s own ‘edited’ marker: 7 of 63 posts held from the last 30 days (11.1%) 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).
고영: 실적의 눈높이를 더 올려야할 때
*보고서: https://han.gl/6aUVw
고영이 AI발 수혜에 힘입어 2연속 어닝서프라이즈를 냈습니다. 지난 분기에 이어 특히 서버고객이 실적을 하드캐리하고 있고요. 덩달아 밸류에이션 프리미엄 요소인 AI 솔루션 사업 매출도 사상 최대 실적을 경신했습니다. 반도체 사업도 좋고요. 이제 투자자들의 시선은 내년으로 향할텐데요. 내년 수요도 견조해보입니다.
고영은 지난 10년간 늘 프리미엄을 받아왔고, 프리미엄을 스스로 정당화 시켜왔습니다. 다만, 검사장비 업체로서는 상대적으로 높은 프리미엄을 받고 있는 만큼 펀더멘탈이나 실적과는 별개로 반도체 관련 변동성이 커지고 있는 상황에서 주가 변동성이 확대될 가능성은 있어 보입니다.
*당사 Compliance 승인을 거친 보고서 요약 자료입니다. 고객의…
Dynamic Korea.
일요일에 한강공원 산책중 지갑분실. 지금까지 지갑을 잃어버리면 항상 찾았기에 난 한국인에 대한 믿음이 있었음.
단, 그때가 비가 내리던 날이라 유동인구가 거의 없어서 아마 사람이 돌아다니기 시작하면 분명히 제보가 올거라고 믿음.
그런데 어제 연락이 없었고, 다시 한번 그자리를 가봤으나 못찾음. 그래서 이놈의 성질머리때문에 바로 신고하고 카드 재발급때림.
근데 어제 신청했는데 오늘 재발급해서 카드 찾아가라고 문자오심 그리고 카드 찾았다고 근처 편의점에 맡겨둔다고 전화오심. ㄷㄷㄷ 그나마 아직 도착하지 않은 카드, 주민증, 사원증 재발급취소하려고 맡겼더니 전부 제작중이라고.
이런 시민의식과 이런 행정속도를 모두 가진 한국.. 진짜 자랑스럽다. 근데 왜 눈물이 나냐 ㅜㅜ
안녕하세요. 씨어스 커뮤니케이션팀입니다.
대웅제약과 씨어스 양사 대표가 긴급 회동을 갖고, AI 입원환자 모니터링 시스템 씽크(thynC™)의 공급 정상화 방안을 논의하고 공급 재개에 합의했다는 더벨 기사가 보도됐습니다.
기사에 따르면 양사는 AI 서버 수급 차질로 지연된 약 200억원 규모의 공급 물량을 해소하기 위해 발주 및 납품 일정을 최종 조율하고 있습니다.
특히 이번 회동은 양사 최고경영진이 직접 공급 정상화에 뜻을 모았다는 점에서 의미가 있습니다. 대웅제약 측에서도 3분기 공급 지연이 씽크 사업의 성장 둔화나 병원 수요 감소가 아닌 일시적인 서버 수급 문제였다고 설명했습니다.
자세한 내용은 아래 기사를 참고해 주시기 바랍니다.
https://www.thebell.co.kr/front/newsview.asp?click=F&ke…
주식은 축구 출전명단을 뽑는것과 비슷한거 같다.
어쨌든 11명은 맞춰야하고,
그런 점에서 모두 잘하는 거보다 해당 포지션에 맞는 뾰죡한 장점이 필요하고,
무엇보다 같은 포지션내에서 상대평가가 중요하다.
즉, 한 주식이 맛탱이가 가버린다면 결국 해당 섹터/테마에서 다른 주식이 그 자리를 꽤찰것. 물론 그 주식도 상태가 영 맘에 들지 않을수 있겠으나, 어쩌겠나 한국 국대는 한국선수안에서 뽑아야지. 갑자기 일본선수를 뽑을순 없느 노릇이니.
지금 XX 테마는 딱 얘다! 하는 붙박이 주전이 사라진 상태. 과연 누가 상대평가의 벽을 뛰어넘을 것인가.
한편 씽크는 의료기기와 네트워크 장비, AI 서버 등으로 구성된 시스템으로, 자재 수급부터 제품 생산과 서버 확보까지 한 분기 이상 소요되는 경우가 있습니다. 이에 따라 회사는 병원의 실제 도입 시점에 맞춰 생산하기보다 예상 수요를 기반으로 제품을 선제적으로 생산하고 있습니다.
판매사인 대웅제약은 병원별 도입 일정과 영업 상황을 바탕으로 차기 분기에 필요한 물량을 회사와 협의해 발주하고, 씨어스는 해당 물량을 전 분기 말까지 공급하는 구조입니다. 즉, 병원과 대웅제약 간에는 주로 의료수가 기반의 수익배분 모델이 적용되는 반면, 씨어스와 대웅제약 간에는 제품 기반의 시스템 공급계약에 따라 매출을 인식합니다.
사업 초기에는 판매사에 대한 공급 물량과 병원의 실제 설치 물량 간 차이가 크지 않았습니다. 그러나 지난해 하반기부터 씽크 도입 병원이 빠…
[씨어스] 3분기 실적설명회 관련 대표이사 서한
투자자 여러분께 드리는 말씀
존경하는 투자자 여러분, 씨어스 대표이사 이영신입니다.
우선 지난 11월 6일 3분기 실적설명회에서 매출 차질의 원인과 대응 방안, 향후 사업 전망을 충분히 설명드리지 못한 점 대표이사로서 진심으로 사과드립니다. 특히 경영진의 준비와 소통이 부족해 회사의 사업 펀더멘털과 성장성에 대한 우려까지 불러일으킨 점을 무겁게 받아들이고 있습니다.
이번 실적설명회는 3분기 실적 부진의 원인과 대응 상황을 신속하게 설명드리고자 마련한 자리였습니다. 다만 당시 판매사와 추가 발주 및 공급 물량에 대한 협의가 마무리되지 않아 향후 매출 전망을 구체적으로 제시하기 어려운 상황이었습니다.
그럼에도 투자자 여러분께서 가장 궁금해하시는 사업 전망과 성장 가능성에 대해 충분히 설명드렸어야…
파마리서치: 이제 조정은 충분히 받았다
*보고서: https://han.gl/2DRZE
부정적인 환율과 내수 미용시술 경쟁심화 속에서도 견조한 실적을 달성했습니다. 파마리서치는 화장품 비중(4Q25 26% -> 3Q26 36%) 및 해외 비중 (4Q25 41% -> 3Q26 49%)확대되며 지역적, 품목적 다각화가 진행되며 매출 구조가 건강해지고 있습니다. 물론 이 과정에서 과거보다 마진은 하락할 것으로 예상됩니다.
내년부터 다양한 신제품들이 출시되는데, 특히 EBD 장비는 리쥬란과 패키지마케팅으로 내수 성장률 방어에 기여할 것으로 예상됩니다. 여러가지 요인으로 어느덧 12개월 선행 P/E 12배까지 조정받았습니다. 조정은 충분히 받은 것 같습니다.
*당사 Compliance 승인을 거친 보고서 요약 자료입니다. 고객의 증권투자 결과에…
👍1
Showing the 12 most recent of 164 posts we hold for @globalmedtech. 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.
Posts recorded as deleted after publishing
We recorded 2 posts on @globalmedtech as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
13 August 2026
Most recent seen missing
13 August 2026
Median time before seen missing
19 hours
Seen missing in the last 30 days
0
Forward network
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.
Mentions
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@globalmedtech named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@asia_square named in 1 post, 13 August 2026 – 13 August 2026
Appears in Telegram’s recommendations for other channels
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.
허혜민의 제약/바이오 소식통 @huhpharm · 24,265 Telegram ranks this channel #23 of 93 here — alongside 92 others — read 16 September 2026
유진투자증권 코스닥벤처팀 @SmallCap · 22,994 Telegram ranks this channel #71 of 96 here — alongside 95 others — read 19 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“[충간지의 글로벌 의료기기/디지털 헬스/로보틱스 연구소]” (@globalmedtech), 12,054 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/globalmedtech.
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.