'미국'바이오
🙏5👍1👎1🤬1😇1

Channel
@hogniel
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
15,475subscribers
+316 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001301601966 |
|---|---|
| Type | Channel |
| Username | @hogniel |
| Created | 18 June 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/hogniel |
Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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.
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.
Posts published here appear in near-verbatim form on 12 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @bornlupin/210165 Nov 2026, 08:49 UTC | @hogniel/71247 · this entry5 Nov 2026, 11:29 UTC | 1.00 | 2.7 hours |
| @FastStockNews/12279512 Aug 2026, 07:12 UTC | @hogniel/68138 · this entry12 Aug 2026, 08:16 UTC | 1.00 | 64 minutes |
| @hogniel/71110 · this entry3 Nov 2026, 07:00 UTC | @kimu_nim/479343 Nov 2026, 07:18 UTC | 1.00 | 18 minutes |
| @kimu_nim/481715 Nov 2026, 03:21 UTC | @hogniel/71246 · this entry5 Nov 2026, 10:51 UTC | 1.00 | 7.5 hours |
| @kimu_nim/481855 Nov 2026, 08:49 UTC | @hogniel/71247 · this entry5 Nov 2026, 11:29 UTC | 1.00 | 2.7 hours |
| @kimu_nim/482936 Nov 2026, 06:08 UTC | @hogniel/71299 · this entry6 Nov 2026, 06:18 UTC | 1.00 | 9 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Ten_level | 29 (8/8 hand-verifiable sample passed) | 1.00 | 7 minutes | @Ten_level (23–6) |
| @bornlupin | 14 (8/8 hand-verifiable sample passed) | 1.00 | 25 minutes | @bornlupin (10–4) |
| @FastStockNews | 13 (8/8 hand-verifiable sample passed) | 0.99 | 22 minutes | @FastStockNews (12–1) |
| @kimu_nim | 7 (7/7 hand-verifiable sample passed) | 1.00 | 14 minutes | this entry (4–3) |
| @mootda | 14 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | even |
| @bbong_tta | 9 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @bbong_tta (8–1) |
| @elite_instructor | 6 (6/6 hand-verifiable sample passed) | 1.00 | 10 minutes | this entry (4–2) |
| @umbrellaresearch | 15 (8/8 hand-verifiable sample passed) | 1.00 | 31 minutes | @umbrellaresearch (8–7) |
| @tazastock | 5 (5/5 hand-verifiable sample passed) | 1.00 | 34 minutes | this entry (3–2) |
| @Yeouido_Lab | 17 (8/8 hand-verifiable sample passed) | 1.00 | 4 minutes | @Yeouido_Lab (10–7) |
| @sharpha | 6 (6/6 hand-verifiable sample passed) | 1.00 | 28 minutes | @sharpha (4–2) |
| @pengmeup | 6 (6/6 hand-verifiable sample passed) | 1.00 | 35 minutes | this entry (5–1) |
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. 21 of the 21 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 252 comparable posts for this entry, running 6 August 2026 to 15 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 16 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 13:00 | 15,475 | +20 |
| 12 Nov 2026, 03:45 | 15,455 | +101 |
| 10 Nov 2026, 06:48 | 15,354 | -3 |
| 8 Nov 2026, 15:46 | 15,357 | -2 |
| 7 Nov 2026, 11:38 | 15,359 | -3 |
| 6 Nov 2026, 14:01 | 15,362 | +16 |
| 5 Nov 2026, 12:37 | 15,346 | +4 |
| 4 Nov 2026, 15:35 | 15,342 | +10 |
| 3 Nov 2026, 16:35 | 15,332 | +8 |
| 2 Nov 2026, 15:45 | 15,324 | +42 |
| 1 Nov 2026, 14:31 | 15,282 | -5 |
| 31 Oct 2026, 15:46 | 15,287 | -2 |
| 30 Oct 2026, 15:41 | 15,289 | -4 |
| 29 Oct 2026, 12:59 | 15,293 | -4 |
| 27 Oct 2026, 10:49 | 15,297 | -5 |
| 26 Oct 2026, 07:16 | 15,302 | +1 |
| 25 Oct 2026, 04:47 | 15,301 | +7 |
| 24 Oct 2026, 04:46 | 15,294 | -6 |
| 23 Oct 2026, 01:37 | 15,300 | -6 |
| 19 Oct 2026, 22:28 | 15,306 | first reading |
1,101 posts held, back to 6 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 81 pages 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 227 of 377 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 1,101 (6 August 2026 – 16 November 2026) |
| Views total | 666,549 |
| Reactions total | 1,498 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 19:22 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.
Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 18 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
3,936 reactions across 542 posts, in 48 distinct kinds. The most used accounts for 18.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 725 | 18.4% | |
| 👍 | 638 | 16.2% | |
| 🤮 | 372 | 9.45% | |
| 🖕 | 323 | 8.21% | |
| 😁 | 308 | 7.83% | |
| 🤬 | 219 | 5.56% | |
| 🥰 | 179 | 4.55% | |
| 🤣 | 147 | 3.73% | |
| 👎 | 132 | 3.35% | |
| 😭 | 127 | 3.23% | |
| 💩 | 99 | 2.52% | |
| 🔥 | 81 | 2.06% | |
| 👏 | 73 | 1.85% | |
| 😱 | 48 | 1.22% | |
| 🍌 | 39 | 0.991% | |
| 🤔 | 37 | 0.94% | |
| 🤯 | 33 | 0.838% | |
| 💯 | 31 | 0.788% | |
| 👌 | 30 | 0.762% | |
| 🙏 | 29 | 0.737% | |
| 28 further kinds | 266 | 6.76% |
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 587 of the 1,000 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 3,936 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 10 August 2026 to 16 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.
Telegram’s own ‘edited’ marker: 20 of 377 posts held from the last 30 days (5.31%) 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).
'미국'바이오
🙏5👍1👎1🤬1😇1
사진
👍12🤮3🥰3❤1😭1
이제 바이오입니다.
🤣10❤4💩1
ㅎㄷㄷㄷ하네용
😱8👎2🥰1😭1
* 하나증권 미래산업팀 * 스몰캡/로봇/AI (Analyst 한유건, 권태우, 박찬솔) ★ 디케이티(290550.KQ) : 비수기에 확인된 이익 체력, 2027년엔 휴머노이드까지 ★ 원문링크: https://buly.kr/1RHWkhS 1. 3Q26 리뷰: 영업이익 129억원, 추정치 55% 상회 - 3Q26은 OLED 부문 매출 비중이 처음으로 절반 아래(45.8%)로 내려온 분기 - 연결 매출액은 1,496억원(+41.5% YoY), 영업이익은 129억원(+168.0% YoY, OPM 8.6%)으로 당사 추정 영업이익을 55% 상회 - 스마트폰 비수기를 ESS BMS와 전장, 로보틱스 성장이 상쇄하며 올해 가장 높은 분기 영업이익률 기록 - 4Q26은 S시리즈 양산이 더해지며 매출액 1,565억원(+36.4% YoY), 영업이익 10…
❤1
[메리츠증권 전기전자/IT부품 양승수] - TrendForce, AI 서버 핵심 부품 공급망 점검 자료 업데이트. 금주 MLCC 리드타임은 전주 대비 2주 증가한 40주를 기록한 반면, 나머지 주요 부품은 기존 수준 유지 - 특히 MLCC의 수급 상태가 기존 Tight에서 Very Tight으로 상향 조정되면서 공급 부족 심화 확인. 정상 수급 수준인 12주 대비 리드타임이 3배 이상 장기화 - ABF 기판과 HDD 역시 리드타임이 50주 내외에서 유지되는 등 AI 서버 핵심 부품의 구조적 공급 부족 지속. 1. CPU (25~30주, 전주 동일) - 에이전틱 AI 서비스 확산에 따른 고코어 프로세서 수요 증가로 데이터센터 내 CPU 수요 확대 지속 - 리드타임은 정상 수급 수준인 16~20주를 상회하는 25~30주 유지 2. G…
Sticker, posted without a caption
🤮10❤3🎉2👍1
하지만 이잼데믹에 아무소용이없게쪄 ㅜ
😇4👍1🤮1
2026.11.16 16:49:55 기업명: 후성(시가총액: 1조 71억) A093370 보고서명: 분기보고서 (2026.09) 잠정실적 : N 매출액 : 2,038억(예상치 : 1,906억, +6.9%) 영업익 : 361억(예상치 : 243억, +48.5%) 순이익 : 113억(예상치 : 188억, -40.0%) **최근 실적 추이** (기간/ 매출/ 영업익/ 순익) 2026.3Q 2,038억/ 361억/ 113억 2026.2Q 1,882억/ 234억/ 250억 2026.1Q 1,414억/ 93억/ -72억 2025.4Q 1,193억/ 49억/ 126억 2025.3Q 1,210억/ 58억/ 144억 공시링크: https://dart.fss.or.kr/dsaf001/main.do?rcpNo=20261116001782
❤2
연결자회사 한텍 op가 38억인데.. 361억이나 나왔네요?
❤1
후성(093370) 분기보고서 (2026.09)(연결) [영업이익] 361 억원 (최근 4분기 중 최대) QoQ(%) 54.2 YoY(%) 522.1 컨센대비(%) 48.5 [PER(연율)] 21.7 http://dart.fss.or.kr/dsaf001/main.do?rcpNo=20261116001782
전.인.류를 구.원해주소서!!
🤷6❤2🤮2🙏2👍1
Showing the 12 most recent of 1,101 posts we hold for @hogniel. 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.
Republished by 50 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 148 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 3 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.
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.
This channel appears in 45 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“호그니엘” (@hogniel), 15,475 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/hogniel.
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.