Channel
@redstone760500
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
598subscribers
+45 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001996399496 |
|---|---|
| Type | Channel |
| Username | @redstone760500 |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/redstone760500 |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 |
|---|---|---|
| 12 Sept 2026, 05:59 | 598 | +4 |
| 27 Aug 2026, 16:27 | 594 | +6 |
| 21 Aug 2026, 13:13 | 588 | +13 |
| 14 Aug 2026, 19:45 | 575 | +22 |
| 8 Aug 2026, 03:36 | 553 | no change |
| 7 Aug 2026, 15:38 | 553 | first reading |
18 posts held, back to 7 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
속보: 전 세계 실물 금을 기반으로 한 ETF는 7월에 30억 달러의 자금 유입을 기록하며, 4월 이후 가장 큰 월간 유입액을 기록했습니다. 이는 전 세계 금 ETF의 보유량을 23톤 증가시켜 4,068톤으로 끌어올렸으며, 이는 2월 27일에 기록된 사상 최고치인 4,176톤에 약간 못 미치는 수준입니다. 유럽 펀드가 21억 달러로 가장 큰 유입을 보였으며, 그 뒤를 아시아(6억 달러)와 북미(7100만 달러)가 이었습니다. 이는 5월과 6월에 각각 20억 달러, 90억 달러의 월간 자금 유출에 이은 것입니다. 올해 들어 전 세계 금 ETF는 총 110억 달러의 자금 유입을 기록했습니다. 전 세계 금 수요가 빠르게 회복되고 있습니다.
뉴욕 연준, 7월 1년물 물가 기대치 3.6%로 발표, 전월 3.7% 대비 하락함.
美 ‘고용 충격’…7월 일자리 2만3000개 줄었다 https://naver.me/5mvbDFSD
검찰이 수사권이 없다고 당당하게 말하네 ㅋㅋㅋㅋㅋㅋㅋㅋㅋ
1400원 초반
NFP 하락은 정부 일자리에서 53k 감소 월드컵 수혜가 2달 연속 사라진건지 레저접객에서 40k 감소
고용 쇼크
속보: 미국 경제가 2020년 팬데믹 이후 세 번째로 큰 월간 고용 감소폭을 기록하면서, 9월 금리 인상 가능성이 40%로 하락했습니다. 며칠 전만 해도 시장에서는 9월 금리 인상 가능성이 70% 이상으로 평가되었습니다. 이 소식에 금 가격은 온스당 4,400달러를 넘어서 급등하고 있습니다.
속보: 미국 경제가 7월에 예상보다 훨씬 낮은 -23,000개의 일자리를 잃었습니다. 예상은 +85,000개였습니다. 실업률은 4.1%로 하락했으며, 이는 예상치인 4.2%보다 낮은 수치입니다. 또한, 6월의 일자리 수치는 -37,000개 감소로 수정되었습니다. 이는 2020년 팬데믹 이후 세 번째로 큰 월간 일자리 감소폭입니다.
미국 경제가 2020년 팬데믹 이후 세 번째로 큰 규모의 월간 일자리 감소를 예상치 못하게 기록하면서, 9월 금리 인상 확률이 40%로 하락 (불과 며칠 전만 해도 시장은 9월 금리 인상 가능성을 70% 이상으로 예상)
지들이 쳐뽑아놓고 이제와서 지랄이노
클리앙 민심도 이런가보네
Showing the 12 most recent of 18 posts we hold for @redstone760500. 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.
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 1 registered channel — 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“거북이의 해외선물” (@redstone760500), 598 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/redstone760500.
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.