Channel
@yieldnspread
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
22,089subscribers
+522 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001589472530 |
|---|---|
| Type | Channel |
| Username | @yieldnspread |
| Description | 채권 애널리스트 김성수 & 크레딧 애널리스트 한시화 |
| Created | 25 July 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/yieldnspread |
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 88% 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 1 other registered channel. 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.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @coinkcgchannel | 18 (8/8 hand-verifiable sample passed) | 1.00 | 71 minutes | this entry (18–0) |
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 157 comparable posts for this entry, running 31 July 2026 to 11 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 key clone_source, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 00:38 | 22,089 | -5 |
| 8 Nov 2026, 13:15 | 22,094 | +23 |
| 6 Nov 2026, 09:16 | 22,071 | -6 |
| 5 Nov 2026, 09:16 | 22,077 | +4 |
| 4 Nov 2026, 07:36 | 22,073 | +13 |
| 3 Nov 2026, 07:31 | 22,060 | -4 |
| 2 Nov 2026, 06:11 | 22,064 | -2 |
| 1 Nov 2026, 02:46 | 22,066 | -5 |
| 31 Oct 2026, 00:29 | 22,071 | -7 |
| 29 Oct 2026, 22:56 | 22,078 | +13 |
| 28 Oct 2026, 19:20 | 22,065 | -9 |
| 27 Oct 2026, 17:55 | 22,074 | -5 |
| 26 Oct 2026, 16:18 | 22,079 | -5 |
| 25 Oct 2026, 14:16 | 22,084 | -6 |
| 24 Oct 2026, 16:14 | 22,090 | -3 |
| 23 Oct 2026, 17:45 | 22,093 | +3 |
| 22 Oct 2026, 20:11 | 22,090 | +25 |
| 20 Oct 2026, 12:46 | 22,065 | +1 |
| 19 Oct 2026, 15:19 | 22,064 | +7 |
| 18 Oct 2026, 11:48 | 22,057 | first reading |
242 posts held, back to 31 July 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 86 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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 242 (31 July 2026 – 11 November 2026) |
| Views total | 267,356 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 03:06 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 11 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.
Telegram’s own ‘edited’ marker: 8 of 72 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).
Lorie Logan 달라스 연은 총재 (매우 강경, 투표권 있음) • 현재 전망을 감안하면 연준은 최소 두 차례 더 25bp 기준금리 인상을 단행할 필요(at least two more 25-basis-point rate increases). 인상 속도는 단기 경제·금융 여건에 달려 있으며, 이번 겨울에는 올가을보다 더 빠르게 움직일 수 있음(It may be possible to move more rapidly this winter) • 현재 기준금리는 다소 긴축적인 수준보다 최소 50bp 낮다고 추정. 두 차례 인상 뒤에는 기준금리를 동결하고 추가 조치를 점검하는 것이 합리적. 목표는 통화정책을 다소 긴축적(modestly restrictive)으로 만드는 것 • 10월 동결은 시장 변동성 확대에 따른 점진적 조정의 일환. 한 번 건너…
Signed 성수
Photo, posted without a caption
Signed 성수
10월 미국 소비자물가: 예상치 상회했습니다
Signed sihwa
■ 앤트로픽 상장 • 11월 10일 수정 신고서 기준 희망밴드는 주당 70~78달러, 8억2,500만주로 최대 643.5억달러 조달. 별도 사모 260억달러를 더하면 최대 904억달러 규모. 나스닥(티커 ANT)에 이달 중순 상장 예정 • 기업가치는 상단(78달러) 기준 추정치는 약 1조200억달러~ 1조4,050억달러 수준. 시장이 기대하던 2조달러보다 30~50% 로이터 기준 절반가량 낮은 규모
Signed 성수
Christopher Waller 연준 이사 (강경파, 당연직) • 10월 물가가 9월보다 나아지더라도 본인은 12월 FOMC에서 기준금리 25bp 인상을 지지하는 쪽으로 기울어 있음(leaning toward supporting an increase in our policy rate of 25 basis points). 물가를 중기적으로 2%에 이르는 경로로 되돌리려면 추가 긴축이 머지않아(sooner rather than later) 필요 • 10월 CPI가 앞선 두 달과 비슷해 근원 CPI가 0.3% 안팎이거나 그보다 높으면 12월에 50bp 인상을 검토해야 하며, 25bp 인상에 그치면 신뢰성이 위험해질(Hiking only 25 basis points would put our credibility at risk) 가능성 • 긴축…
Signed 성수
10월 금통위 의사록 ■ 위원 1(기준금리 동결) • 글로벌 AI 투자 확대 영향으로 예상보다 강한 수출 증가세 지속, 올해와 내년 성장률 모두 지난 8월 전망치 상회 및 잠재성장률 수준 상회, GDP갭 플러스 전환 예상 • 소비자물가 및 근원물가 상승률 모두 2%대 후반으로 목표 수준 큰 폭 상회, 명목성장률의 큰 폭 확대가 경제 전반의 수요압력을 추가로 높이면서 높은 근원물가 오름세가 장기화될 가능성 • 현재의 긴축 기조 지속 필요성이 있지만 3.00% 유지 후 지난 두 차례 선제적 인상의 영향과 높아진 대내외 불확실성의 향방을 지켜보는 것이 바람직하다는 의견, 향후 기준금리 추가 인상 시기 등 결정 ■ 위원 2(기준금리 동결) • 재정건전성 우려 확산으로 장기 국채금리 등 시장금리가 크게 상승하며 실물경제와 금융시장 전반에 …
Signed 성수
■ 일본은행 10월 금융정책결정회의 Summary of Opinion • 이번 동결 근거로는 경제·물가 위험과 금융여건 변화를 조금 더 점검해야 한다는 의견과, 경기 일부에 약한 모습이 보여 과거 기준금리 인상의 누적 효과를 확인해야 한다는 의견이 주된 내용. 기조적 물가상승률이 물가안정 목표에 대체로 부합하고 금융여건이 완화적이어서 경제·물가·금융여건에 따라 기준금리를 계속 인상하는 것이 적절하다는 의견도 제시됨. 다음 인상은 지나치게 신중해지지 말고 가능할 때 결정하되, 인구 감소·고령화를 감안해 소비의 기조적 흐름 등 경제의 복원력을 살펴야 한다는 지적 • 중립금리까지 기준금리를 올리는 속도에 대해서는 의견이 갈림. 기업의 금리 관련 내성이 커져 과거 인상 효과가 아직 나타나지 않았고 금융여건도 완화적이어서 중립금리로 가는 속도를 높…
Signed 성수
회사채 수요예측 11/3~11/9 업데이트(8건) ■ 케이씨씨 82-1 (AA-, 확정) 만기 2년 수요예측 10/27(화) 발행규모 | 모집액 800억 → 발행액 1,500억 공모 희망밴드 | 개별 -30~30bp 가산금리 | -7bp 발행금리 | 4.308% ■ 케이씨씨 82-2 (AA-, 확정) 만기 3년 수요예측 10/27(화) 발행규모 | 모집액 1,200억 → 발행액 2,500억 공모 희망밴드 | 개별 -30~30bp 가산금리 | -7bp 발행금리 | 4.388% ■ 에스케이렌터카 59-1 (A0, 확정) 만기 2년 수요예측 10/28(수) 발행규모 | 모집액 400억 → 발행액 1,400억 공모 희망밴드 | 개별 -30~30bp 가산금리 | +24bp 발행금리 | 4.974% ■ 에스케이렌터카 59-2 (A0, 확정) 만기…
Signed sihwa
Photo, posted without a caption
Signed sihwa
Austan Goolsbee 시카고 연은 총재 (강경파, 투표권 없음) • 고용과 성장은 꽤나 안정적. 큰 문제는 물가. 물가목표 달성 실패를 받아들이고 대응해야 함(We've got to come to terms with inflation failure) • 서비스 물가가 다시 상승하기 시작(Starting to see inflation kicking up in services) • 데이터센터 투자는 고전적인 수요 과열처럼 보임(old-fashioned overheating). 과열은 한번 생기면 없애기 매우 고통스러워 초기에 공격적으로 대응해 경제를 과열시키지 않는 것이 통념. 기대가 클수록 경제의 역량 이상으로 과열되지 않을까 우려스러움 • 낮은 실업률과 꽤 견조한 임금 상승에 기반한 광범위한 소비가 성장의 주된 동력. 역사적으로 완전…
Signed 성수
Photo, posted without a caption
Signed 성수
[FI Weekly] AI에도 Fed Put이 가능한가 ▶ AI 리스크 관련 연준 지원 가능성 점검 ▶ 2027년 보험사 자본성증권 차환 수요1 • 이론적으로 AI 기업들이 무너지면 연준의 지원은 불가능하지 않음. 다만, 이전 위기 때만큼의 직접적인 도움은 어려울 것. CP 매입은 잔액이 있는 기업들 다수가 매입 요건에 미충족. 시장조성의 일환으로 AI 기업 부채를 보유한 딜러를 지원하거나, AI 기업 익스포저가 큰 은행들을 지원할 수는 있지만 이는 어디까지나 간접적 지원. 실효성에는 의문부호가 붙음 • 2023년 IFRS17 및 K-ICS 도입을 앞두고 보험사들이 2022년 대규모로 발행한 자본성증권의 첫 콜옵션 행사 가능일이 2027년부터 본격 도래. 조기상환 물량은 자체 자금으로 상환하거나 신규 발행을 통해 차환 가능. 향후 대응 …
Signed 성수
Showing the 12 most recent of 242 posts we hold for @yieldnspread. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
대차대조표 업데이트
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
오늘 금통위
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 242 most recent posts we hold, published 31 July 2026 to 11 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 49 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 21 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 39 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“YIELD & SPREAD” (@yieldnspread), 22,089 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/yieldnspread.
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.