Based on Anthropic’s S-1/A-2 filing, the estimated share count is expected to be revised
❤1

Channel
@tlsrltnf
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
22,343subscribers
-452 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001451407215 |
|---|---|
| Type | Channel |
| Username | @tlsrltnf |
| Description | 문의사항 @rokorea 블로그:https://blog.naver.com/jinriwarman 공지방:https://t.me/tlsrltnf 채팅방:https://t.me/helpmetebi |
| Created | 24 April 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/tlsrltnf |
Marketing & affiliate — 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 47% 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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @tlsrltnf/22621 · this entry16 Oct 2026, 05:55 UTC | @mujammin123/3024716 Oct 2026, 05:59 UTC | 1.00 | 4 minutes |
| @tlsrltnf/22698 · this entry2 Nov 2026, 05:00 UTC | @Honeyofwhitesocks_2/126192 Nov 2026, 05:58 UTC | 1.00 | 58 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mujammin123 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 49 minutes | this entry (4–1) |
| @Honeyofwhitesocks_2 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 10 minutes | this entry (4–3) |
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 91 comparable posts for this entry, running 4 August 2026 to 13 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_mutual, last confirmed 14 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 |
|---|---|---|
| 12 Nov 2026, 17:19 | 22,343 | -12 |
| 10 Nov 2026, 13:48 | 22,355 | -22 |
| 9 Nov 2026, 02:51 | 22,377 | -16 |
| 7 Nov 2026, 22:30 | 22,393 | -23 |
| 6 Nov 2026, 22:56 | 22,416 | -11 |
| 5 Nov 2026, 22:29 | 22,427 | -9 |
| 4 Nov 2026, 23:16 | 22,436 | -13 |
| 4 Nov 2026, 01:24 | 22,449 | -10 |
| 3 Nov 2026, 00:54 | 22,459 | -7 |
| 1 Nov 2026, 23:09 | 22,466 | -4 |
| 30 Oct 2026, 21:28 | 22,470 | -11 |
| 30 Oct 2026, 00:28 | 22,481 | -17 |
| 28 Oct 2026, 22:56 | 22,498 | -16 |
| 27 Oct 2026, 19:17 | 22,514 | -14 |
| 26 Oct 2026, 17:39 | 22,528 | -4 |
| 25 Oct 2026, 19:16 | 22,532 | -8 |
| 24 Oct 2026, 20:18 | 22,540 | -7 |
| 23 Oct 2026, 16:44 | 22,547 | -16 |
| 22 Oct 2026, 13:30 | 22,563 | -21 |
| 21 Oct 2026, 05:28 | 22,584 | first reading |
261 posts held, back to 3 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 111 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 57 of 66 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 261 (3 August 2026 – 13 November 2026) |
| Views total | 110,004 |
| Reactions total | 149 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 03: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 14 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 9 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.
547 reactions across 191 posts, in 9 distinct kinds. The most used accounts for 90.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 494 | 90.3% | |
| 👍 | 24 | 4.39% | |
| 🤯 | 10 | 1.83% | |
| 🔥 | 7 | 1.28% | |
| 🕊 | 5 | 0.914% | |
| 😢 | 3 | 0.548% | |
| 💯 | 2 | 0.366% | |
| 😁 | 1 | 0.183% | |
| 🙏 | 1 | 0.183% |
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 205 of the 261 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 566 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 261 most recent posts we hold, published 3 August 2026 to 13 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tlsrltnf. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 261 most recent posts we hold for this entry, published 3 August 2026 to 13 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 261 most recent posts we hold, published 3 August 2026 to 13 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 14 of 66 posts held from the last 30 days (21.2%) 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).
Based on Anthropic’s S-1/A-2 filing, the estimated share count is expected to be revised
❤1
과거에 내가 열심히 코인을 했던 시절에는 낭만이라기보다 알파가 넘쳤다. 미리 알 수 있는 상장 루트라던지 지금은 Market feed 와 같은 곳에서 신규 리스팅 토큰 알림이라던지 누구든지 알지만 그때는 거의 없던 시절부터 이러한 알파를 활용했었고 트위터 매매도 반응이 상당히 느렸기 때문에 개발자 트위터에 올라오고 사도 10% 씩은 먹여주던 낭만의 시장부터 코인을 했었다. 그러다보니 빠르게 벌었고, 원상 메타가 원래 따리 하면 2배는 기본에 5배까지도 먹여주던 시장에서 플레이 하다가 어느순간부터(2018년 말) 는 원상 메타가 상당히 맛이 없었고(그래도 10% 이상) 코인들의 가격이 계속 내려가는 시장이라 신규 플레이어가 거의 없었다. 그래서 그때 나는 바로 이 도파민의 끝을 청산하기 위해 코인을 접었고, 모든 자산을 달러로 바꿔서 …
❤8
📌김프 2% 구간 알림 현재 김프 : 2.44% 환율(USD) : 1335 테더(USDT) : 1367 최대 김프 : SOPH(77.95%) 최소 김프 : RED(1.12%) 전체김프 보기 | @theddari_kimp
❤1
코덱스 뱅크드리셋 들어옴 .
❤3
이번 앤트로픽(하리 롱/바낸 숏) 차익 거래를 제시한 친구가 복기한 글인데 관심 있으셨던 분들은 읽어보시면 좋을듯요. 타임라인은 11/07에 IPO 연기로 갭이 다시 벌려졌다가 11/10 로드쇼 타이밍 때 공모가 공시 + IPO 연기 불확실성 해소되면서 갭 다 붙는 과정이었네요. 생각보다 차질 없는 거래였는듯.
❤1
새벽에 발견한 흥미로운 떡밥 https://blog.naver.com/berry-grow/224473340314 올해 세무사 수석 ai사용 부정의혹?(일각에서 제기된 의혹임, 확인된 사실 없음) 수석합격자 본인이 올린 후기글에 현직 세무사들이 일기토 많이거는듯 부정이든 아니든 뭔가 ai가 사회에 남긴 여파는 큰거같네. 일반적인 범위를 벗어난 성과를 보이면 ai로 의심하게 되는게 참 씁쓸한거같기도하고
❤1
일본마운자로 국내따리 3개월치 허용됫구나 국내가격도 이제 좀 내리려나
안녕하세요 여러분 🙏 RoboStrategy와 함께 서울에서 로보틱스와 피지컬 AI를 이야기하는 저녁 자리를 준비했습니다. 아직 서툰 부분이 많지만, 편하게 오셔서 함께 이야기 나눠주시면 정말 감사하겠습니다..! (제발요) 피지컬 AI가 연구실을 벗어나 현실로 들어오고 있는 지금, 빌더, 투자자, 커뮤니티 분들과 함께 로보틱스가 어디로 가고 있는지 이야기 나눠보고 싶었습니다. 📅 11월 22일(일) 18:00~22:00 KST 📍 서울 청담동 🎟 무료, 승인제 100명 타임테이블 18:00 입장, 웰컴 드링크 및 체크인 18:30 오프닝 및 RoboStrategy 소개 19:00 패널 토론: 로보틱스는 지금 어디쯤 와 있을까? 19:30 RoboStrategy 팀과의 Q&A 20:00 자유 대화 및 네트워킹 귀한 시간 내주신 패널 분…
Fable한도리셋권뿐아니라 클로드 주간한도리셋권도들어왔네요.
❤1
아이폰 업데이트필수 매번 업데이트하는데도 계속 취약점나오네
❤1
LBANK 이용하다 13억 동결당한 한국인 원문 블로그도 보니 8,574 USDT 입금하고 최대 260만불까지 불렸다가 180만불에서 동결당하고 현재 추가 손실로 100만불 남아있다고 함 십스캠 거래소들은 고객이 버는 만큼 거래소 손실로 직결되기 때문에 눈 뜨고 25억을 잃게 생겼는데 어떻게든 명분을 내세워서 출금을 막습니다. 혹시나 마이너한 거래소에서 수익이 나셨다면 꼭 출금하시길 바랍니다. 가장 좋은건 이용을 안하는 것
❤5
바낸에서 굿즈준다네요
Showing the 12 most recent of 261 posts we hold for @tlsrltnf. 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.
@tlsrltnf edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 52 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 66 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 12 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.
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 20 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 31 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“신기술은 돈이 된다 공지방” (@tlsrltnf), 22,343 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/tlsrltnf.
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.