Channel
@yieldnspread
On this record: Topic · Growth · Engagement · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
22,020subscribers
+453 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 |
| Created | 25 July 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 14 October 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 14:49 | 22,020 | -6 |
| 13 Oct 2026, 06:06 | 22,026 | +9 |
| 8 Oct 2026, 23:20 | 22,017 | +6 |
| 4 Oct 2026, 15:54 | 22,011 | -7 |
| 26 Sept 2026, 16:17 | 22,018 | -12 |
| 17 Sept 2026, 11:19 | 22,030 | +30 |
| 15 Sept 2026, 10:01 | 22,000 | -2 |
| 13 Sept 2026, 17:01 | 22,002 | +1 |
| 12 Sept 2026, 00:57 | 22,001 | -2 |
| 9 Sept 2026, 12:56 | 22,003 | +3 |
| 6 Sept 2026, 04:41 | 22,000 | +4 |
| 4 Sept 2026, 01:02 | 21,996 | +11 |
| 2 Sept 2026, 15:27 | 21,985 | +9 |
| 1 Sept 2026, 11:26 | 21,976 | +3 |
| 31 Aug 2026, 13:53 | 21,973 | +30 |
| 30 Aug 2026, 11:25 | 21,943 | +4 |
| 29 Aug 2026, 10:28 | 21,939 | +15 |
| 28 Aug 2026, 08:45 | 21,924 | +3 |
| 27 Aug 2026, 10:42 | 21,921 | +29 |
| 26 Aug 2026, 07:04 | 21,892 | first reading |
170 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 69 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 12 October 2026 |
|---|---|
| Posts held | 170 (31 July 2026 – 12 October 2026) |
| Views total | 291,370 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Oct 2026, 08:17 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.
신현송 한국은행 총재 • 향후 통화정책은 물가와 경기 흐름, 금융안정 상황을 면밀히 점검하면서 추가 기준금리 인상의 시기와 속도 등을 결정해 나갈 계획. 10월이나 11월 추가 인상 여부를 묻는 질의에는 가장 중요한 것은 인플레이션 추이 • 7·8월 연속 기준금리 인상은 통화정책 기조를 주요국보다 조금 일찍 인상 방향으로 잡은 것이며, 인상이 5~6월에 상당 부분 시장가격에 반영돼 시간을 벌었다고 평가 중. 시장에 쫓겨 나중에 방어적으로 인상하는 상황보다 경제적 비용이 훨씬 적다는 판단 • 포워드 가이던스가 국고채 금리 상승을 부추겼다는 지적에는 일장일단이 있음. 그러나 선제적으로 움직여 시장의 중심을 잡고 궁극적인 비용을 줄일 수 있다는 입장. 최근 2~3주 국채 금리는 상당히 안정적으로 유지되는 중 • 물가는 누적된 비용 압력의 전…
Signed 성수
신현송 한국은행 총재 • 물가는 상당 기간 목표 수준 상회하는 오름세 예상
Signed 성수
[FI Weekly] 늘어난 수요, 더 늘어난 공급 ▶ 글로벌 금리상승, 메꾸지 못하는 중앙은행의 빈 자리 ▶ 증권채 발행만기 장기화 • 최근 주요 선진국(G7) 국채의 민간 수요는 2010년대보다 분명히 강함. 그러나 민간 부문에서 받아줘야 하는 물량은 1.8σ로 더 크게 증가. 중앙은행이 돌아오지 않는 한 공급 우위의 수급 환경은 쉽게 바뀌지 않음 • 올해 4분기에는 증권사 조달 만기 장기화 수요에 따라 증권채 발행이 늘어날 전망. 2027년부터 유동성 관리 대상 증권사가 국내 49개사로 확대되고, 신조정유동성비율이 도입되기 때문. 향후 증권채 발행은 자기자본 4조원 이상의 우량 증권사를 중심으로 이뤄질 전망
Signed 성수
- G7 국채시장 보유주체별 비중 및 수급 상황 추이
Signed 성수
■ 내심 바라는 자들, 선 그은지 얼마 안된 자들 - 우리는 줄곧 금리 상승의 근본 원인을 수급부담으로 설명해왔음. 그런데 정작 정부는 국채 발행을 줄일 생각이 전혀 없어 보임. 쓸 곳은 많고, 찍으면 누군가는 사 준다는 믿음이 여전한 탓. 투자자들도 바보는 아니라서, 이런 정부를 보며 국채라는 안전자산의 지위에 슬슬 의구심을 품기 시작함. 2027년은 물론이고 2020년대 후반 채권시장의 핵심은 "정부와 중앙은행의 관계가 재정립될 수 있느냐"일 것. 수급부담을 풀어줄 주체가 있다면 중앙은행 하나뿐. 정부 입장에서는 재정 건전화라는 숙제를 하느니 중앙은행에 답안지를 베껴 달라고 조르는 편이 빠르다는 계산이 나올 수 있음 - 주요 선진국 국채시장의 수급을 같은 잣대로 비교하기 위해 수요와 공급 지수를 자체 적으로 산출해 보았음. 수요지수는 …
Signed 성수
Photo, posted without a caption
Signed 성수
Christopher Waller 연준 이사 (강경파, 당연직) • 기준금리를 2025년 12월~2026년 9월 수준에 유지했다면 물가를 적시에(in a timely manner) 2%로 되돌리지 못했을 것. 9월 25bp 인상은 8월 CPI 한 건이 아니라 몇 달간 쌓인 증거(preponderance of evidence)에 따른 결정 • 물가의 보다 적시 복귀를 위해 추가 인상을 예상(I anticipate additional hikes). 다만 인상이 연속 회의에서 이뤄질 필요는 없으며(do not need to come at consecutive meetings) 적절한 기간 안에 이뤄지면 되고, 당분간 정책은 물가 책무에 초점을 두고 통화정책을 운영할 것 • 점도표는 최종 도착점을 고정하지 않고 정책 방향을 알리는 신호 역할을 …
Signed 성수
Photo, posted without a caption
Signed 성수
박홍근 기획예산처 장관 1. 노르웨이는 적자국채 발행이 필요 없음에도 지속적으로 국채를 발행 중. 국채시장의 변동성을 완화시키기 위한 것 2. 국채 발행량 변동이 너무 크면 불필요한 비용이 발생. 발행량을 평탄하게 유지하는게 노르웨이의 공식적인 방침 3. 우리나라의 국채 발행 규모는 코로나19와 대규모 세수결손을 거쳐 200조원대로 확대. 이런 부분들까지 종합적으로 고려할 필요
Signed 성수
Photo, posted without a caption
Signed 성수
■ 9월 FOMC 의사록 [통화정책] • 참석자 전원이 기준금리 25bp 인상(3.75~4.00%) 지지. 거의 모든 참석자가 물가 위험은 상방, 고용 위험은 축소되어 대체로 균형이라고 평가 • 다수(many)는 예상보다 강한 수요나 추가 공급 충격에 대비한 위험관리 차원에서 더 높은 금리 경로가 타당하다고 강조. 상당수(a number of)는 위험관리가 아닌 기본 전망만으로도 인상 필요하다는 입장 • 대부분(most)은 연말까지 한 차례 추가 인상이 적절할 가능성이 높다고 평가. 여러 명(several)은 현 금리가 제약적이지 않거나 약간만 제약적이라고 판단, 두어 명은 중립금리 추정치 상향 [대차대조표] • 몇몇(a few) 참석자는 국채시장이 원활하게 작동 중이라고 평가 • 다만 시장 스트레스에 대한 사전 대비 필요성 지적. …
Signed 성수
Photo, posted without a caption
Signed 성수
Showing the 12 most recent of 170 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 170 most recent posts we hold, published 31 July 2026 to 12 October 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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“YIELD & SPREAD” (@yieldnspread), 22,020 subscribers as measured 14 October 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.