불개미 X 아메리칸포트리스 AMA🎙 요즘 애들 커뮤니티 이벤트 활발하게 하는 중 ➡️들으러가기
❤2👍2😁1

Channel
@cobacknamannounce
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
16,931subscribers
-2,690 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001770920592 |
|---|---|
| Type | Channel |
| Username | @cobacknamannounce |
| Description | 유튜브 코백남 공지방입니다. https://linktr.ee/cobacknam contact DM : @cobacknam |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/cobacknamannounce |
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 82% 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 3 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 |
|---|---|---|---|
| @fireant_crypto/434058 Aug 2026, 14:11 UTC | @cobacknamannounce/15863 · this entry8 Aug 2026, 17:06 UTC | 1.00 | 2.9 hours |
| @fireant_crypto/452705 Nov 2026, 08:56 UTC | @cobacknamannounce/16865 · this entry5 Nov 2026, 10:05 UTC | 1.00 | 68 minutes |
| @fireant_crypto/4553415 Nov 2026, 16:40 UTC | @cobacknamannounce/17053 · this entry15 Nov 2026, 16:40 UTC | 1.00 | under a minute |
| @WeCryptoTogether/681729 Nov 2026, 15:07 UTC | @cobacknamannounce/16921 · this entry9 Nov 2026, 15:38 UTC | 1.00 | 31 minutes |
| @WeCryptoTogether/6832915 Nov 2026, 16:39 UTC | @cobacknamannounce/17053 · this entry15 Nov 2026, 16:40 UTC | 1.00 | under a minute |
| @cobacknamannounce/16842 · this entry4 Nov 2026, 06:57 UTC | @leedogin2/247324 Nov 2026, 07:01 UTC | 1.00 | 4 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @fireant_crypto | 5 (5/5 hand-verifiable sample passed) | 1.00 | 48 minutes | @fireant_crypto (5–0) |
| @WeCryptoTogether | 5 (5/5 hand-verifiable sample passed) | 1.00 | 31 minutes | @WeCryptoTogether (5–0) |
| @leedogin2 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 4 minutes | this entry (3–2) |
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. 4 of the 4 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 152 comparable posts for this entry, running 5 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, 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 |
|---|---|---|
| 16 Nov 2026, 02:19 | 16,931 | -45 |
| 12 Nov 2026, 12:47 | 16,976 | -44 |
| 10 Nov 2026, 08:06 | 17,020 | -33 |
| 8 Nov 2026, 19:49 | 17,053 | -5 |
| 7 Nov 2026, 15:46 | 17,058 | -10 |
| 6 Nov 2026, 18:19 | 17,068 | -17 |
| 5 Nov 2026, 15:15 | 17,085 | -13 |
| 4 Nov 2026, 17:07 | 17,098 | -9 |
| 3 Nov 2026, 16:44 | 17,107 | -14 |
| 1 Nov 2026, 19:50 | 17,121 | -14 |
| 31 Oct 2026, 18:28 | 17,135 | -22 |
| 30 Oct 2026, 18:41 | 17,157 | -32 |
| 29 Oct 2026, 21:39 | 17,189 | -3 |
| 28 Oct 2026, 19:49 | 17,192 | -14 |
| 27 Oct 2026, 20:28 | 17,206 | -15 |
| 26 Oct 2026, 17:58 | 17,221 | -21 |
| 25 Oct 2026, 20:57 | 17,242 | -8 |
| 24 Oct 2026, 18:55 | 17,250 | -4 |
| 23 Oct 2026, 21:05 | 17,254 | -5 |
| 22 Oct 2026, 21:15 | 17,259 | first reading |
491 posts held, back to 4 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 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. It is computed over the 222 of 236 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 | 491 (4 August 2026 – 16 November 2026) |
| Views total | 258,914 |
| Reactions total | 1,157 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 17:55 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 12 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.
4,610 reactions across 456 posts, in 19 distinct kinds. The most used accounts for 45.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,080 | 45.1% | |
| 👍 | 1,358 | 29.5% | |
| 👏 | 504 | 10.9% | |
| ⚡ | 309 | 6.70% | |
| 🔥 | 132 | 2.86% | |
| ❤🔥 | 62 | 1.34% | |
| 😁 | 38 | 0.824% | |
| 🙏 | 37 | 0.803% | |
| 🤩 | 20 | 0.434% | |
| 💋 | 19 | 0.412% | |
| 😐 | 18 | 0.39% | |
| 🤣 | 10 | 0.217% | |
| 🍌 | 7 | 0.152% | |
| 🐳 | 5 | 0.108% | |
| 🌭 | 4 | 0.087% | |
| 👌 | 4 | 0.087% | |
| 🍓 | 1 | 0.022% | |
| 🎉 | 1 | 0.022% | |
| 💯 | 1 | 0.022% |
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 477 of the 491 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 5,014 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 491 most recent posts we hold, published 4 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: 28 of 236 posts held from the last 30 days (11.9%) 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).
불개미 X 아메리칸포트리스 AMA🎙 요즘 애들 커뮤니티 이벤트 활발하게 하는 중 ➡️들으러가기
❤2👍2😁1
머리카락 카메라... 이걸 어떻게 찾을건데
❤3👍2👏1
친척 동생 이번에 수능 보는 19살인데.. 잘 마무리되었으면 좋겠네요 ㅠ
👍7❤1👏1
진짜 세상에 대혼돈이 오고 있다..
❤3⚡1👍1
포밈에서 요트 및 툭툭이 디자인 대회 진행✔️ 어차피 코인충들 다 똑같은 AI 쓸 것 같은데 혹시나 디자인에 일가견있으시면 도전해보시길 선정되면 5명한테 각각 200 USDT ➡️트윗 원문
❤2👍2
라이터 MM 지갑 뭐 털린 것 같다네요 가지고 계신 분들 대응 참고 !
❤2👍1👏1
지금 진행 중인 Zoth 세일 근황✔️ 500K 타겟 중 현재 100K 모였네요 SILVER 등급으로 참전해볼까 고민 중입니다 요약👀 - 11월 16일 오늘부터 판매 시작 - KOREA 코드 사용 시 10% 캐시백 지원 - 3가지 등급으로 각 베스팅 조건 다름 - 이더리움 체인 스테이블코인으로 참여 가능 ➡️10% 캐시백 링크
❤2👍1👏1
솔라나 메인넷 1.0 발표 현재 라이브 중✔️ 요약👀 - 솔라나 출시 때부터 지금까지는 베타 버전 - 이제 Solana 1.0, 정식 메인넷 시작 - Alpenglow 적용으로 트랜잭션 빨라짐 - Firedancer라는 두 번째 검증 클라이언트 배포
❤2👍1👏1
앰버쪽 자금 유출 의혹
❤3👍1
2026년 개인정보 유출된 주요 국내 업체👀 1. 따릉이 : 1월 2. 사랑의열매, 진학사 : 3월 3. 듀오 : 4월 4. 티빙 : 6월 5. BGF (CU), 모두의 창업 (중기부) : 6월 6. 정부24 : 8월 7. GS리테일 : 8월 과징금 8. 뮤팟, 카카오게임즈 : 9월 9. 빗썸, 고팍스, 블록미디어, 신한, 하나, 국민, 새마을, 미래에셋, 부산, 현대캐피탈, OK저축, 산은캐피탈, 대신증권 등 여러 은행, 할리스, 대한항공 및 아시아나, G마켓, NOL, 서울대, 연세대, 서울사이버대, 부경대 : 10월 10. 금융보안원, 조폐공사 앱 '착' : 11월 10월에 무슨 일이 있었던거죠? AI가 발전하면서 개인 정보 탈탈 털리는 중
❤4👍2👏1
두나무, 2026년 3분기 영업손실 35억원📉 전년 동기 매출 60% 감소 이것저것 많이 상장시키긴했는데 결국 시장을 이기진 못했나보네요.. ➡️뉴스 원문
👍4❤1👏1
0G 프로젝트 풀요약본 업로드했습니다✔️ 8분 안에 빠르게 압축해서 상세히 알려드림 작년 10월, 올해 10월마다 상승해준 코인이니 10월 바람이 끝나기 전에 알아보았습니다. 혹시 0G 활용법 모르시면 꼭 보시는 걸 추천 ! 참고로 이번에 오랜만에 제 목소리로 녹음함 구좋댓알은 저에게 큰 위로가 됩니다❤️❤️ ➡️0G 영상 보러가기
❤6👍5👏4🔥2
Showing the 12 most recent of 491 posts we hold for @cobacknamannounce. 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.
We recorded 1 post on @cobacknamannounce as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 53 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 8 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.
@cobacknamannounce named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 23 seed channels' Telegram-generated recommendation lists in total. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“코백남 공지방” (@cobacknamannounce), 16,931 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/cobacknamannounce.
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.