Channel
@nojobnoplan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,673subscribers
+93 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002323312052 |
|---|---|
| Type | Channel |
| Username | @nojobnoplan |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/nojobnoplan |
Crypto & trading — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 18 Sept 2026, 16:41 | 3,673 | +33 |
| 14 Sept 2026, 12:19 | 3,640 | +8 |
| 10 Sept 2026, 13:58 | 3,632 | +16 |
| 4 Sept 2026, 23:20 | 3,616 | +13 |
| 31 Aug 2026, 20:55 | 3,603 | +5 |
| 28 Aug 2026, 23:18 | 3,598 | +7 |
| 25 Aug 2026, 21:14 | 3,591 | +14 |
| 22 Aug 2026, 19:55 | 3,577 | +4 |
| 19 Aug 2026, 11:35 | 3,573 | +1 |
| 16 Aug 2026, 15:04 | 3,572 | -7 |
| 12 Aug 2026, 21:03 | 3,579 | -2 |
| 7 Aug 2026, 01:17 | 3,581 | +1 |
| 6 Aug 2026, 11:47 | 3,580 | first reading |
23 posts held, back to 30 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 3 pages 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 23 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
38 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 86.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 86.8% | |
| 👍 | 2 | 5.26% | |
| 🤣 | 2 | 5.26% | |
| 👎 | 1 | 2.63% |
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 15 of the 23 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 30 July 2026 to 7 August 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.
[이더리움 초기 투자자, $910만 LIT 매수] 이더리움 초기 투자자(OG)로 알려진 익명 주소가 최근 2개월간 총 $910만을 투입해 391만 LIT를 매수했다고 룩온체인이 전했다. 평균 매수가는 2.33달러이며, 해당 고래는 최근에도 LIT 매집을 지속하고 있는 것으로 나타났다. https://coinness.com/news/1164973
푸에고는 총 5,555개 중 5,305개가 민팅되며 약 95.5%의 민팅률로 종료됐다고 합니다. 민팅은 완전히 종료되어 앞으로 추가 발행은 없으며, 이후 공급량은 줄어들기만 하는 구조입니다. 여러 개를 민팅한 경우 보유 수량에 따라 더 많은 참여 권한을 받고, 이를 쌓아 FORGE의 상위 티어를 해금할 수 있다고 합니다. 현재 거래와 전송은 가능하며, 리빌은 내일 진행됩니다. 시즌 1 등록도 곧 시작될 예정입니다.
❤4
$UNITREE 거래 보상 이벤트 이벤트 기간 동안 Lighter에서 $UNITREE를 거래한 참여자들이 총 30,000 LIT의 보상풀을 나눠 받는 이벤트입니다. 기간 시작: 8월 7일 오전 9시 종료: 8월 17일 오전 8시 59분 한국시간 기준 총 10일 총보상: 30,000 LIT 거래량, 순위 등 구체적인 보상 산정 방식은 아직 공개되지 않았습니다. 자세한 내용이 나오는 대로 다시 공유드리겠습니다.
❤1
라이터 고래 다시 매수 시작 출금한 스테이블 70억정도 남아있음 전부 긁으면..? 😎😎😎😎😎😎 https://debank.com/profile/0x73781209f3b0f195d0d3fa9d6b95bb61c54c1ca6/history
❤1
이제 베리에이셔널, 익스텐디드, 라이즈, 퍼시피카 정도 남았는데 다들 잘됐으면 좋겠네요. Ostium도 예전에는 꽤 괜찮아 보였는데, 볼트 익스플로잇 이슈 터진 뒤로는 아예 후보 목록에도 없네요
❤1
Perp DEX 포인트 OTC 거래 가격 정리 현재 장외거래에서 형성된 것으로 알려진 Perp DEX별 포인트 가격 • Variational: 포인트당 $25~$30 • Extended: 포인트당 $2~$3 • Perpl: 포인트당 $5~$10 • Ondo Perps: 포인트당 $0.3~$0.5 • Rise: 포인트당 $5~$7.5 • Pacifica: 포인트당 $0.2~$0.3 • Nado: 포인트당 $0.4~$0.6 최근 에어드랍 메타가 Perp DEX로 몰리고 있는 가운데, 우선 Extended가 향후 몇 주 내 TGE를 준비 중이며 다른 프로젝트들도 순차적으로 에어드랍을 진행할 가능성이 있음 다만 OTC 가격은 공식 가격이 아니며 거래 상대방과 시장 상황에 따라 크게 달라질 수 있으니 참고용으로만 보는 게 좋음 출처
나여! wise 근데 누구시죠..[ReboundX AMA] 정보 장소 : 기분좋은 마곤 텔레그램 채팅방 긴급 AMA 기분좋은 마곤 / 햇재와 선동이 난무하는 각자 코인 선동방(live) 시간 : 8월 7일 금요일 오후 8시 Guest : wise degen AMA 라이브 도중 게릴라 상품 : 베스킨라빈스 20개, 커피 100잔 컨텐츠 소개 최근 크라임 코인매매부터, cashcat, marscoin 등의 핫한 밈코로 수억의 수익을 조용하게 올린 미친 폼의 Wise degen님이 ReboundX 트레이딩 웹 연동 후 실력이 드러나버리셨습니다.. 조용히 채널을 운영하면서 소통하시는데 누구신지 낱낱히 파헤쳐보려고 합니다. 풍문으로는 레전드 OG 빌더 출신이시라는데요? 선물 시장에서 살아남는 방법과 수익의 종갓집 양념비법을 훔치는 자리를 만들어 봤…
컬쳐랜드 상품권 쌀먹 공유 5만원짜리 상품권을 네이버 쿠폰어케어케 껴서 사면 대강 7%언저리 할인해서 살수있음 이거사서 어디쓰는지는 각자 다르긴한데 영화보거나 메이플캐시충전하거나 등등 검색해서 각자 알아서 쓰심대긴함 https://brand.naver.com/cultureland_gift/products/13684363908 매진대면 3만원권 사심댑니다 (링크)
MEXC에서는 호가가 얇아서 152M까지 다녀왔네요.
cashcat??????? 👀👀👀👀👀
아니 GRVT 상장은 아니지 진짜
나랑드 최저가 링크 찾아서 주문하는김에 링크남겨요 나랑드 제로 30캔 10,900원(배송비포함)
❤3
Showing the 12 most recent of 23 posts we hold for @nojobnoplan. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“머리나빠도 돈버는법” (@nojobnoplan), 3,673 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nojobnoplan.
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.