Telegram RegisterThe public register of Telegram
Telegram profile photo for 바칼리의 단도박 일지 -> 일기

Channel

바칼리의 단도박 일지 -> 일기

@Bakalieee

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

240subscribers

-2 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-1003170903098
TypeChannel
Username@Bakalieee
CreatedBetween 1 September 2025 and 17 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/Bakalieee

Growth

2402422417 August 2026 — 242 subscribers8 August 2026 — 242 subscribers15 August 2026 — 240 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -2. 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 240–242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 13:46240-2
8 Aug 2026, 09:47242no change
7 Aug 2026, 17:31242first reading

Engagement

19 posts held, back to 17 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 11 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

130 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 86.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11286.2%
👍1310.0%
🔥53.85%

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 9 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 130reactions 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 17 October 2025 to 11 November 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

11 Nov 2025, 09:07 UTC379 views5 reactionsread 8 August 2026

Lisk는 Ethereum 기반 OP Stack 체인이라 구조가 Base, Optimism이랑 동일한 Optimistic Rollup 즉, 출금할 때 기본적으로 7일 대기(Challenge Period) 가 걸리는 구조라, 공식 브릿지로 바로 출금해도 일주일은 묶이게 되어 있음. 빠른 출금을 노리고 Across Fast Bridge를 쓰면 이게 Relayer가 자기 돈으로 먼저 보내주는 구조라 풀 유동성(LP) 이 비어 있으면 송금이 안 됨. 결국 “풀 빈 거 모르고 브릿지 걸었다가 자금 묶임” 상황 결론적으로 자금은 7일 뒤에 돌아오긴 함, 근데 이런 구조를 미리 알았으면 묶이는 일은 없었을 듯. 다음부터는 1️⃣ 브릿지 걸기 전에 across.to/bridge 들어가서 풀 유동성 체크 2️⃣ “Built with OP Stack”이

5

11 Nov 2025, 09:05 UTC319 viewsread 8 August 2026

두업님 채팅방이 진짜 고수분들 많은듯 흐린눈 하고 보면 도움되는 정보가 많다 말은 험악한데 코린이 질문도 은근 잘받아줌

11 Nov 2025, 09:05 UTC303 views0 reactionsread 8 August 2026
Photo

무지성 리스크 스왑했는데 이거 1주일뒤에 들어오나요? 아

11 Nov 2025, 08:03 UTC288 viewsread 8 August 2026

메간 선물박스 휭휭 돌리면서 집에서 나왔는데 그때 바로 전남친을 마주쳤어요 개당황스럽다

27 Oct 2025, 11:15 UTC333 viewsread 8 August 2026

관리자님 저희팀 10명 중에서 1명이 자기 KYC 가 안됐다고 꼬장 부린답시고 포스팅 자기꺼 5개를 싹 삭제해서 저희팀 9명이 할당을 못 받았어요 이거 혹시 구제 안될까요? 너무 억울한데

27 Oct 2025, 09:39 UTC359 viewsread 8 August 2026
Forwarded from @cryptopandannPhoto

Opinion 코드 오픈 https://app.opinion.trade/ 코드: INTERN 저번에도 몇시간 컷이었으니 빠르게 ㄱㄱ

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

Forward network

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.

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

“바칼리의 단도박 일지 -> 일기” (@Bakalieee), 240 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Bakalieee.

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.