😐 [쌀먹] 금연길라잡이 2026년 3분기 만족도조사 경품 네이버페이 5천원권 × 100명 일정 진행 중 ~ 9/30(수) 발표 10/8(목) 개별 안내 참여 방법 1️⃣ 「금연길라잡이」에 회원가입하고 로그인 2️⃣ 「만족도조사」 문항 작성하고 제출하면 응모 끝 #기프티콘 #이벤트 #상품권
👍1

Channel
@GemHive
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
24,227subscribers
-721 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001515736467 |
|---|---|
| Type | Channel |
| Username | @GemHive |
| Description | DM for Promotion or AD @gemhive88 ☑️ Twitter : https://x.com/gemhive99 |
| Created | 13 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/GemHive |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 25 Sept 2026, 21:00 | 24,227 | +423 |
| 19 Sept 2026, 05:56 | 23,804 | -327 |
| 16 Sept 2026, 17:20 | 24,131 | -542 |
| 14 Sept 2026, 18:56 | 24,673 | +776 |
| 13 Sept 2026, 05:41 | 23,897 | -194 |
| 11 Sept 2026, 11:21 | 24,091 | -595 |
| 8 Sept 2026, 18:55 | 24,686 | -472 |
| 5 Sept 2026, 10:39 | 25,158 | -281 |
| 3 Sept 2026, 12:39 | 25,439 | +869 |
| 2 Sept 2026, 09:13 | 24,570 | -185 |
| 1 Sept 2026, 07:44 | 24,755 | -111 |
| 31 Aug 2026, 05:13 | 24,866 | -156 |
| 30 Aug 2026, 07:02 | 25,022 | +1,003 |
| 29 Aug 2026, 03:53 | 24,019 | -240 |
| 28 Aug 2026, 01:16 | 24,259 | -387 |
| 27 Aug 2026, 00:52 | 24,646 | -433 |
| 26 Aug 2026, 03:34 | 25,079 | -249 |
| 25 Aug 2026, 04:58 | 25,328 | +1,039 |
| 24 Aug 2026, 05:34 | 24,289 | -235 |
| 22 Aug 2026, 15:24 | 24,524 | first reading |
870 posts held, back to 5 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 60 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.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 870 (5 August 2026 – 27 September 2026) |
| Views total | 219,076 |
| Reactions total | 1,216 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 12:26 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 27 September 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 29 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.
8,246 reactions across 850 posts, in 14 distinct kinds. The most used accounts for 39.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,220 | 39.0% | |
| 👍 | 2,014 | 24.4% | |
| 👌 | 713 | 8.65% | |
| 🔥 | 550 | 6.67% | |
| ❤🔥 | 401 | 4.86% | |
| ☃ | 312 | 3.78% | |
| 🎄 | 250 | 3.03% | |
| 🎉 | 244 | 2.96% | |
| 🎅 | 228 | 2.76% | |
| 👏 | 189 | 2.29% | |
| 😁 | 66 | 0.8% | |
| 🥰 | 34 | 0.412% | |
| 🕊 | 16 | 0.194% | |
| 🥴 | 9 | 0.109% |
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 870 of the 870 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 8,557 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 870 most recent posts we hold, published 5 August 2026 to 27 September 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.
😐 [쌀먹] 금연길라잡이 2026년 3분기 만족도조사 경품 네이버페이 5천원권 × 100명 일정 진행 중 ~ 9/30(수) 발표 10/8(목) 개별 안내 참여 방법 1️⃣ 「금연길라잡이」에 회원가입하고 로그인 2️⃣ 「만족도조사」 문항 작성하고 제출하면 응모 끝 #기프티콘 #이벤트 #상품권
👍1
😐 [쌀먹] 한국건강증진개발원 제13차 미래 건강전략 포럼 경품 애플워치 × 1명, 가습기 × 1명 기프트카드 1만원권 × 10명 커피쿠폰 × 90명 일정 사전등록 ~ 9/30(수) 14시 발표 추첨 후 개별 안내 참여 방법 1️⃣ 「사전등록 폼」에 참석 방법·성명·연락처 적어 제출하면 응모 끝 2️⃣ 9/30(수) 14시 포럼을 「유튜브」 생중계로 보면 실시간 이벤트·만족도조사 경품까지 응모 ➡️ 「포럼 안내 페이지」 #기프티콘 #이벤트 #커피
👍1
😐 [쌀먹] 부산진구 취업이야기 유튜브 구독 이벤트 경품 네이버페이 1만원권 × 100명 일정 진행 중 ~ 9/27(일) 발표 10/2(금) 개별 알림 참여 방법 1️⃣ 「부산진구」 유튜브 채널 구독 2️⃣ 「네이버폼」 설문지 작성하고 제출 3️⃣ 「이벤트 영상」에 취업 응원 댓글 남기면 응모 끝 #기프티콘 #이벤트 #상품권
❤1👍1
美 30년물 5.5% 돌파, 2004년 이후 처음 출처 금리 급등의 원인이 인플레보다 '미국 경제가 강한 탓'이라는 쪽으로 무게가 실리는 분위기. • 30년물 5.495% (주간 +16.8bp) • 주중 5.50% 상향 돌파 → 2004년 6월 이후 처음 • 10년물 5.164%, 주중 5.20% (2007년 6월 이후 최고) • 2년물 4.856% · 6주 연속 상승 • 9월 합성 PMI 58.4 → 62개월 최고 • 10/2 9월 고용보고서, 10월 연준 인상 베팅 우세
☃1❤🔥1🎄1👍1
ONDO, XRP 제치고 국내 관심지수 1위 출처 관심지수는 조회수가 아니라 실제로 오간 거래대금이 기준. • ONDO 84.2점, 국내 거래비중 4.92% (677억) • 2위 WLD 82.9 (1765억) · 3위 FIL 82.1 • 국내 편중 STX 19.4배 · ONDO 19.1배 · WLD 18.9배 • 국내 5개 거래소/바이낸스 비중 22.2% (30일 전 6.0%) • 김프 최고 AVAX +0.95%
☃1🎄1👍1
😐 [쌀먹] KT Y 유튜브 크리에이터와 함께 빛나는 Y 경품 BBQ 황금올리브치킨+콜라 × 100명 메가MGC 아메리카노 × 쇼츠 참여자 전원 크리에이터와 특별한 하루 × 25명 일정 진행 중 ~ 9/27(일) 발표 10월 1주차 이후 순차 개별 안내 참여 방법 1️⃣ 「응모폼」에서 함께하고 싶은 크리에이터 고르고 신청 사연 쓰면 응모 끝 2️⃣ 「홍보 영상」에 응원 댓글 남기고 캡처해 폼에 첨부 3️⃣ 「내가 가장 빛나는 10초」 쇼츠에 해시태그 「#KTY #Y10주년 #해피버스데이Y」 달아 올리고 주소를 폼에 첨부하면 커피 증정 ※ 만 19~34세만 참여 가능 ➡️ 「이벤트 페이지」 #기프티콘 #치킨 #커피
❤1👌1👍1
😐 [쌀먹] 교육부 2026년 제3회 특별성과 국민투표 경품 모바일 상품권 × 50명 일정 진행 중 ~ 9/30(수) 23시 발표 심사 종료 후 개별 안내 참여 방법 1️⃣ 「국민심사 페이지」 접속하고 소통24 「로그인」 2️⃣ 특별성과 사례 18건 확인하고 점수 주면 응모 끝! #기프티콘 #이벤트 #상품권
❤3👍1
😐 [쌀먹] 서울시 내 손안에 서울 퀴즈 풀고 가게 4주차 경품 서울사랑상품권 5천원권 × 50명 일정 진행 중 ~ 9/28(월) 17시 발표 9/29(화) 이벤트 페이지 게시 참여 방법 1️⃣ 「네이버폼」에 빈칸 퀴즈 정답과 개인정보 입력 2️⃣ 제출하면 응모 끝! ※ 정답 「마음」 #기프티콘 #이벤트 #상품권
❤3👍1👏1🔥1
😐 [쌀먹] 진천군 공식 SNS 친구 맺는 날 경품 다이소 상품권 5천원권 × 200명 일정 진행 중 ~ 10/4(일) 발표 10/7(수) 이내 개별 안내 참여 방법 1️⃣ 「진천군 유튜브」 구독 2️⃣ 「추석밥상, 긴급구조 119」 홍보영상 좋아요 3️⃣ 「네이버폼」 작성하고 제출하면 응모 끝! #기프티콘 #이벤트 #상품권
❤4👍1👏1🔥1
😐 [쌀먹] 축산환경관리원 축산환경 우수사례 공모전 국민심사 경품 이디야 커피쿠폰 1만원권 × 100명 일정 진행 중 ~ 10/11(일) 발표 심사 종료 후 개별 안내 참여 방법 1️⃣ 「국민심사 페이지」 접속하고 소통24 「로그인」 2️⃣ 「깨끗한 축산농장」 「경축순환농업」 후보작을 분야별 1건씩 투표하면 응모 끝! #기프티콘 #이벤트 #커피
❤4👍1👏1🔥1
😐 [쌀먹] 한국도로교통공단 ESG 이해관계자 설문조사 경품 커피 기프티콘 × 100명 일정 진행 중 ~ 9/30(수) 발표 추첨 후 개별 문자 참여 방법 1️⃣ 「설문조사」에서 ESG 문항에 응답 (3~5분) 2️⃣ 휴대전화 번호 남기고 제출하면 응모 끝! #기프티콘 #이벤트 #커피
❤2👍2
[리마인드] 연휴 숙제, 돈 안 드는 웨이트리스트 두 개 해치우기 Jumper • 9/29 (화) Legion 세일 확정 • 3년 무토큰으로 브릿지 누적 $25B 넘게 돌린 곳이라 XP 홀더 처우가 최대 관심사 1️⃣ 웨이트리스트에 X 연결, 초대 많을수록 순위 위로 2️⃣ Legion 가입하고 X·지갑 연결해 스코어 미리 계산 SmartX • YZi Labs 투자받은 온체인 소셜 트레이딩 앱, 앱 출시 전 웨이트리스트만 열림 • 상위 100위 Genesis 100, 5,000위 안이면 얼리 액세스에 수수료 20~50% 할인, 보상 풀 최대 10,000 USDT 1️⃣ 웨이트리스트에서 트레이더 성향 테스트 6문항 2️⃣ 이메일 인증하면 끝, 결과 이미지 X에 올리면 랭킹 활성화 #Jumper #SmartX #웨이트리스트
❤3🎄1👌1👍1
Showing the 12 most recent of 870 posts we hold for @GemHive. 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.
@GemHive 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 64 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 2 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.
@GemHive named 8 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“젬하 크립토(GemHive)🦄 경제적 자유 이루기” (@GemHive), 24,227 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/GemHive.
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.