망년회 시즌입니다. 밥먹고삽시다
👍19❤11💩2🤯2🖕1

Channel
@nq_rgc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,010subscribers
+1,165 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003800716407 |
|---|---|
| Type | Channel |
| Username | @nq_rgc |
| Description | 그녀석 맞습니다. |
| Created | Between 1 February 2026 and 23 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/nq_rgc |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 02:08 | 7,010 | +14 |
| 3 Nov 2026, 02:59 | 6,996 | -23 |
| 31 Oct 2026, 05:56 | 7,019 | -5 |
| 28 Oct 2026, 02:49 | 7,024 | -26 |
| 24 Oct 2026, 16:09 | 7,050 | -12 |
| 21 Oct 2026, 11:49 | 7,062 | +134 |
| 18 Oct 2026, 12:27 | 6,928 | +542 |
| 15 Oct 2026, 11:36 | 6,386 | +4 |
| 12 Oct 2026, 11:18 | 6,382 | +26 |
| 5 Oct 2026, 14:58 | 6,356 | +36 |
| 27 Sept 2026, 14:15 | 6,320 | +49 |
| 15 Sept 2026, 10:57 | 6,271 | +6 |
| 12 Sept 2026, 00:01 | 6,265 | +115 |
| 7 Sept 2026, 09:37 | 6,150 | -5 |
| 2 Sept 2026, 17:12 | 6,155 | -9 |
| 30 Aug 2026, 17:34 | 6,164 | +15 |
| 27 Aug 2026, 10:57 | 6,149 | +41 |
| 24 Aug 2026, 16:14 | 6,108 | +34 |
| 21 Aug 2026, 01:52 | 6,074 | +24 |
| 18 Aug 2026, 01:22 | 6,050 | first reading |
128 posts held, back to 23 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 17 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 82 of 103 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 128 (23 July 2026 – 7 November 2026) |
| Views total | 219,904 |
| Reactions total | 1,264 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 16:38 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 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
1,694 reactions across 102 posts, in 25 distinct kinds. The most used accounts for 28.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 490 | 28.9% | |
| 👍 | 298 | 17.6% | |
| 🤯 | 212 | 12.5% | |
| 🖕 | 147 | 8.68% | |
| 🤣 | 139 | 8.21% | |
| 😁 | 98 | 5.79% | |
| 👏 | 67 | 3.96% | |
| 🤮 | 56 | 3.31% | |
| 👎 | 41 | 2.42% | |
| 💩 | 32 | 1.89% | |
| 🔥 | 27 | 1.59% | |
| 🥰 | 23 | 1.36% | |
| 🤡 | 15 | 0.885% | |
| 🍌 | 12 | 0.708% | |
| 😭 | 8 | 0.472% | |
| 🤪 | 6 | 0.354% | |
| 🫡 | 6 | 0.354% | |
| 🍾 | 5 | 0.295% | |
| 💯 | 3 | 0.177% | |
| 🤔 | 3 | 0.177% | |
| 5 further kinds | 6 | 0.354% |
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 104 of the 128 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 1,694 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 128 most recent posts we hold, published 23 July 2026 to 7 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: 2 of 103 posts held from the last 30 days (1.94%) 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).
망년회 시즌입니다. 밥먹고삽시다
👍19❤11💩2🤯2🖕1
Photo, posted without a caption
❤12💩1🤯1
즉 중간선거 수혜주가 될 수도 있다
👍13💩1🤯1
이 친구들은 상당히 억울한게 사장 자체는 머스크한테 감사하단 말을 자주합니다.(굉장히 인성이 바른 사람임) 우주 산업 개화시켜줘서 고맙다고 직접 트위터에 표현하고 그랬는데 머스크 이새끼가 아스퍼거 증후군이라 뻑하면 AST스페이스모바일 사업계획 말안되니뭐니 견제구 날리고 그거땜에 억울하게 주가 하락 거기다가 트럼프 정부 + 스페이스X상장 이후 대놓고 머스크 몰아주기 들어가면서 스타링크 대비 기대치가 낮아지는 억울함까지 경험했습니다. 그리고 블루오리진에게 얘네의 위성 발사 프로젝트를 수주했다가 아마존 대머리가 재활용 로켓 기술 성공만 자랑하고 위성은 목표궤도에 보내지도 못하는 해괴한 일도 터지고 이후 어쩔 수 없이 자기를 졸라게 깠던 머스크에게 위성 발사를 맡기는.. 뭐 그런 수모만 주구장창 겪었는데 위에서 말했듯이 사장인 아벨 영감…
❤12🖕3💩2🙏1
AST 스페이스모바일이 자체 재사용 로켓 개발 계획 발표. AST 스페이스모바일은 최대 5기의 블루버드 위성을 한 번에 발사할 수 있는 20톤급 재사용 로켓 '블랙리프트(Blacklift)' 개발을 추진하며, 2028년 말 운용 개시를 목표로 설정. 이를 위해 파이어플라이 에어로스페이스와 13억 달러 이상의 계약 체결. 주요 계약 내용은 다음과 같음. • 초기 블랙리프트 로켓 3기에 사용할 엔진 공급 • AST 스페이스모바일이 미국 내 신규 시설에서 파이어플라이의 미란다 및 비라 엔진을 자체 생산할 수 있는 영구 라이선스 확보 • 향후 3년간 엔지니어링 기술 지원 제공 AST 스페이스모바일은 계약에 따라 약 8억 달러를 선지급할 예정이며, 현금 4억 달러와 자사 주식 1,000만~1,400만 주로 구성. 이와 별도로 엔진 공급에 2…
❤7
어제 BKSY도 그렇고 우주쪽 좋은소식이 들려오네요
파이어플라이, ASTS와 13억 달러 이상 규모의 로켓 엔진 계약 체결 파이어플라이가 AST 스페이스모바일의 신규 대형 발사체에 엔진을 공급하는 3년 계약을 체결했습니다. 계약 내용은 다음과 같습니다. 파이어플라이는 AST의 첫 3기 로켓용으로 미란다(Miranda) 엔진 27기와 비라(Vira) 엔진 9기를 포함해 총 36기의 엔진을 인도합니다. ASTS는 엔진 제조 라이선스와 함께 엔지니어링 지원을 받습니다. 엔진 지식재산권(IP)은 파이어플라이가 계속 보유합니다. ASTS는 파이어플라이에 현금과 ASTS 주식을 합쳐 13억 달러 이상을 지급하며, 주식에는 보호예수(락업) 기간이 적용됩니다. ASTS의 목표는 자사 발사 일정에 대한 통제력을 높이는 것입니다. 파이어플라이는 추가 자금을 통해 엔진 시험 능력을 확대하고 자체 발사체 생산을…
❤5
굿
😁8
미국과 이란, 평화 협상 돌파구 마련 임박 블룸버그 통신에 따르면, 미국과 이란이 전쟁 종식을 위한 잠재적 합의에 한층 더 가까워지고 있음. 이란(테헤란) 측은 그동안 협상 불가 영역으로 여겨졌던 핵 문제에 대해서도 기꺼이 논의할 의향이 있는 것으로 전해졌으며, 이는 협상 국면의 변화 가능성을 시사함.
안녕하세요. 기존 에테르의 일본&미국 채널을 운영하는 에테르입니다. 지난 10월 27일에 올해 8월부터 지속적인 신고 누적으로 인해 텔레그램 계정에 신용사기딱지가 붙었습니다. 이후 텔레그램측에 해결하기 위해 수차례 이메일, 문의등등 방법으로 접촉을 시도해보았지만, 연락이 닿지 않아 아직까지도 어떠한 응답을 못받았습니다. 따라서 기존 계정을 작성된 글들을 최대한 백업해서 새로운 채널인 https://t.me/aethersemiconductor 로 옮겼습니다. 기존 채널은 옆에 (구)를 붙일거고, 당분간은 폐쇄하지 않을 방침입니다. 제 채널을 구독하는 분이라면 새로운 채널로 이전해주시면 대단히 감사하겠습니다. https://t.me/aethersemiconductor
👍7❤1
저 스킬은 작년 관세 빔 때도 유효하긴 했는데 리스크의 성질 자체가 다른 부분이 있어서 똑같이 통할지는 모르겠습니다. 통하면 뭐 내가 인생 잘 산거고 아니면 아직 부족한거고
🖕11❤4
+하루만에 여기 인근에 도달한게 황당
Showing the 12 most recent of 128 posts we hold for @nq_rgc. 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 4 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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“나스닥혁명수비대” (@nq_rgc), 7,010 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/nq_rgc.
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.