Telegram RegisterThe public register of Telegram
Telegram profile photo for 크립토 표류기🐸

Channel

크립토 표류기🐸

@cryptodrifters

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

685subscribers

-4 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-1001711305190
TypeChannel
Username@cryptodrifters
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/cryptodrifters

Growth

685690687.57 August 2026 — 689 subscribers7 August 2026 — 689 subscribers8 August 2026 — 690 subscribers23 August 2026 — 689 subscribers29 August 2026 — 688 subscribers7 September 2026 — 685 subscribers7 August 20267 September 2026
6 measurements spanning 31 days, net -4. 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 684–691 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 00:16685-3
29 Aug 2026, 19:12688-1
23 Aug 2026, 02:34689-1
8 Aug 2026, 01:19690+1
7 Aug 2026, 07:46689no change
7 Aug 2026, 07:39689first reading

Engagement

17 posts held, back to 26 July 2026the 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 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

24 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 95.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2395.8%
👍14.17%

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 7 of the 17 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 24 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 26 July 2026 to 5 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.

Recent posts

5 Aug 2026, 16:54 UTC112 viewsread 7 August 2026

류기 평단은 5M 2만불 진입 끝까지 간다 씨발

5 Aug 2026, 05:50 UTC156 viewsread 7 August 2026
Photo

아... 진짜 조온나 달다... Frong 안샀던 흑우 없제...

3 Aug 2026, 08:42 UTC192 viewsread 7 August 2026
Photo

0x6245e67affA44a23077f0Ea7f981a8DC743a0c47 이거 나만 먹여줄 것 같음?

1 Aug 2026, 19:00 UTC238 views5 reactionsread 7 August 2026
Photo

이럴 줄 알았음…. 병신들이 내가 한통속은 무슨 한통속임 ㅋㅋㅋㅋㅋㅋㅋㅋ 정치질로 쫓겨난지가 언젠데 비트마트 한국 직원들한테 물어봐라 ㅋㅋㅋㅋㅋㅋㅋㅋㅋ 심지어 내가 멋 모르고 쫓겨나고 나서 죽닥치고 있었을 때 그사람이 한국 직원들 회의 소집해서 내가 거래소에 심각한 피해를 줘서 쫓아냈다고 까지 했다 ㅅㅂㅋㅋㅋㅋㅋ 그거 안 믿은 직원 몇명은 듣고 싸해서 다 탈출하고 못믿은 병신들이나 남아서 있다가 다 해고당한거지 ㅋㅋㅋㅋ

5

30 Jul 2026, 18:47 UTC248 views2 reactionsread 7 August 2026
Photo

업비트 일처리 빠르노… 업비트한테 전화와서 통화하는데 목소리가 존나 자다깬 목소리 같아 보이더라

2

29 Jul 2026, 12:01 UTC290 views7 reactionsread 7 August 2026

옆에서 모든 과정을 지켜본 솔트랑 프로는 졸업하면 시원하게 포르쉐 한대씩 쏠게요. 글 안지움 이제 딱 3.3배만 더 벌면 저도 조일현좌 따라가겠습니다

7

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“크립토 표류기🐸” (@cryptodrifters), 685 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/cryptodrifters.

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.