Channel name was changed to «귤귤»

Channel
귤귤
@BAJINO1_NO1
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
237subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002312366114 |
|---|---|
| Type | Channel |
| Username | @BAJINO1_NO1 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/BAJINO1_NO1 |
Topic
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 23 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 09:56 | 237 | -4 |
| 28 Sept 2026, 13:22 | 241 | -6 |
| 2 Sept 2026, 18:27 | 247 | +1 |
| 27 Aug 2026, 11:53 | 246 | -1 |
| 14 Aug 2026, 17:08 | 247 | -4 |
| 8 Aug 2026, 09:31 | 251 | no change |
| 7 Aug 2026, 17:12 | 251 | first reading |
Engagement
19 posts held, back to 24 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 19 posts for this entry, the most recent from 13 October 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
365 reactions across 17 posts, in 17 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 146 | 40.0% | |
| 👍 | 73 | 20.0% | |
| 🔥 | 52 | 14.2% | |
| 👏 | 35 | 9.59% | |
| 🥰 | 13 | 3.56% | |
| 🖕 | 11 | 3.01% | |
| 😱 | 9 | 2.47% | |
| 👎 | 5 | 1.37% | |
| 😡 | 4 | 1.10% | |
| 🫡 | 4 | 1.10% | |
| 😁 | 3 | 0.822% | |
| 🆒 | 2 | 0.548% | |
| 💩 | 2 | 0.548% | |
| 💯 | 2 | 0.548% | |
| 🤣 | 2 | 0.548% | |
| 🎃 | 1 | 0.274% | |
| 😘 | 1 | 0.274% |
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 17 of the 19 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 365 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 September 2025 to 13 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Channel photo updated
이제부터 테러는 예약제 궁금한건 존나게 많고 하고는 싶은데 막상 금액들으니 안하는 분들이 많기때문에 단순문의는 차단합니다 내 시간이 존나게 아까우니 그렇게 하는거니 이해 바랍니다 일일히 대답하는거 좆같으니 접고싶은마음도 있음
❤11🔥8👍5🤣2
Signed 인력사무소
10월10일부터 정상영업 그전엔 불가합니다 참고바랍니다
❤7👍5🔥5
Signed 인력사무소
꽁까이패드 사고조 거래주의 나까마100%
❤7👍6🔥5
Signed 인력사무소
사기꾼한테 사기친건 정의 아닙니까
❤18🔥6👍5🖕5👎2🥰2😡1
Signed 인력사무소
꽁까이 통신 안전한거면 너거애미껄로 개통ㄱㄱ 신분증줘 개통해줄게
🔥10👏8❤5🖕3😡3👎2
Signed 인력사무소
사기당했다는 사람아 듣거라 1번.빗썸장을 샀는데 국민이 링걸린거 국민장주가 이런게 처음이 아니라는 훈육했다(국민고객센터) 핑계그만 쳐대라.지가 유리한쪽으로만 이야기하는 씹쓰레기야 하루살이새끼 2번.유심 사기당했다는 베트콩아 찡찡대는거. 보기싫어서 차단 300가지고 ㅂㅅ새끼가 너때문에 피눈물 나는사람들 적선했다고 생각해라 그리고 니가 스팸뜨거나 보피자나 개씹자슥아 300은 잘쓸께 그리고 사기당한게 자랑이냐 병신새끼야 쪽팔린줄 알아야지 니가하면로맨스 내가하면 사기냐 씹새끼야 사기당한게 자랑이라고 이놈저놈ㅋㅋ 떠벌리냐.본방본방 거리네ㅋㅋ병신새끼 추신:두 병신 교육완료 끝
❤9👍6🥰5🖕3💩2👎1🔥1😁1
Signed 인력사무소
트랜스젠더 있으면 연락주세요 이상한거 아닙니다
❤5👍4👏4😘1
Signed 인력사무소
추석테러세트 예약받습니다
❤8👍5🔥5
Signed 인력사무소
꼭 그렇게 20만원을 가져가야 속이 후련했냐~이씹새끼야
❤8🔥7👍6
Signed 인력사무소
제사이트앞장 선착순 이체 하루5000-1억사이이체만 장난치면 집에불지릅니다 완료
❤3👍3🥰3
Signed 인력사무소
Showing the 12 most recent of 19 posts we hold for @BAJINO1_NO1. 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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“귤귤” (@BAJINO1_NO1), 237 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/BAJINO1_NO1.
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.