Telegram RegisterThe public register of Telegram

Channel

우리는 트윗충

@twitchoong

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

71,586subscribers

-1,390 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001733576671
TypeChannel
Username@twitchoong
Description제보&문의: @twitbug #크립토 관련 세계 각국 뉴스, 떠도는 트윗 중에서 중요한 정보들만 골라 기록하는 나만의 공간 이 곳은 리딩방이 아님. 팩트 체크&판단 각자 제 채널 글에 근거한 #매매금지 모든 글은 매수, 매도 추천이 아니며, 참고자료도 될 수 없으며, 뉴스의 사실 여부와 수익을 보장하지 않고, 원금 손실이 있을 수 있으니 제 채널 글에 근거한 매매는 엄격히 금합니다.
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/twitchoong

Growth

71,58672,97672,2816 August 2026 — 72,976 subscribers6 August 2026 — 72,947 subscribers7 August 2026 — 72,820 subscribers9 August 2026 — 72,639 subscribers10 August 2026 — 72,214 subscribers11 August 2026 — 72,073 subscribers12 August 2026 — 71,938 subscribers13 August 2026 — 71,713 subscribers14 August 2026 — 71,586 subscribers6 August 202614 August 2026
9 measurements spanning 8 days, net -1,390. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 71,378–73,185 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 06:5871,586-127
13 Aug 2026, 01:2471,713-225
12 Aug 2026, 01:1171,938-135
11 Aug 2026, 01:2572,073-141
10 Aug 2026, 02:1872,214-425
9 Aug 2026, 01:1472,639-181
7 Aug 2026, 22:0572,820-127
6 Aug 2026, 23:4472,947-29
6 Aug 2026, 10:3172,976first reading

Engagement

23 posts held, back to 3 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.61%
avg views ÷ 71,586 subscribers
Avg views / post
5,450
13 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
13
of 23 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held23 (3 July 202614 August 2026)
Views total70,800
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 21:23 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.

What this channel posts

Photos
1,550
Videos
7
Links
1,690

Lifetime counters from Telegram’s own channel header, read 14 August 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.

Recent posts

14 Aug 2026, 08:32 UTC≈3,310 viewsread 14 August 2026

업비트, 빗썸 힘내라..!! 제발 잘 버텨주세요🙏🏻 코인거래소 매출 반토막…반 년새 원화예치금 2조 8천억 이탈 빗썸, 2분기 순손실 218억…두 개 분기 연속 적자 가상자산 시장 침체에…두나무, 2분기 영업이익 84% 급감

11 Aug 2026, 09:00 UTC≈4,970 viewsread 14 August 2026
Photo

바이낸스, #아이콘 #소폰 포함 5종 유의종목 지정 #ICX #SOPH #GLMR #RARE #MOVR 공지 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

10 Aug 2026, 06:53 UTC≈4,440 viewsread 14 August 2026

#보라 카카오게임즈, 메타보라에 80억 지원 #BORA http://v.daum.net/v/20260810072030513 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

6 Aug 2026, 13:40 UTC≈4,500 viewsread 14 August 2026
Photo

#플룸 DTCC 디지털 자산 산업 워킹 그룹에 합류하여 토큰화 서비스 혁신을 추진 #PLUME https://x.com/plumenetwork/status/2085336469678506347?s=46 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

4 Aug 2026, 01:01 UTC≈4,400 viewsread 14 August 2026
Photo

#플룸 & 신한자산운용 - 원화 토큰화 펀드 실증 협력 #PLUME ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

3 Aug 2026, 13:36 UTC≈5,290 viewsread 14 August 2026
Photo

#리스크 재단, 향후 45일 동안 100만 달러 (약 15억 상당) 바이백 예정 #LSK 공지 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

3 Aug 2026, 03:31 UTC≈4,170 viewsread 14 August 2026
Photo

바이낸스, #어크로스프로토콜 #해시플로우 #불칸포지드 등 5종 상장 폐지 #ACX #HFT #PYR #PIVX #VANRY 공지 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

24 Jul 2026, 13:57 UTC≈6,260 viewsread 14 August 2026
Photo

키네틱 그룹, 공개 시장 매입과 장외 거래를 통해 #플루이드 토큰 공급량의 최대 10%까지 구매할 계획 #FLUID 공지 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

24 Jul 2026, 03:00 UTC≈6,440 viewsread 14 August 2026
Photo

바이낸스, #리스크 #스택스 #어크로스프로토콜 유의 종목 지정 #LSK #STX #ACX 공지 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

23 Jul 2026, 02:46 UTC≈5,450 viewsread 14 August 2026
Photo

#다날 주가 20%대 강세 - 금일 일시 상한가 터치 https://www.cbci.co.kr/news/articleView.html?idxno=591282 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

21 Jul 2026, 17:57 UTC≈5,750 viewsread 14 August 2026

#무브먼트 랩스, 챕터11 파산 보호 신청 #MOVE 뉴스 원문 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

20 Jul 2026, 09:51 UTC≈10,100 viewsread 14 August 2026
Photo

#질리카 보안 이슈 발생 #ZIL 질리카 재단 공지 ※“우리는 트윗충의 모든 게시글은 매수, 매도 등 권유를 구성하지 아니하며 내용의 그 어느 부분도 투자 결정을 위한 기초 또는 근거가 될 수 없습니다.”

Showing the 12 most recent of 23 posts we hold for @twitchoong. 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.

Posts edited after publishing

@twitchoong edited 2 posts 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.

First edit seen
14 August 2026
Most recent edit
14 August 2026

Citation-graph rank

Citation-graph rank — 402,632 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“우리는 트윗충” (@twitchoong), 71,586 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/twitchoong.

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.