Telegram RegisterThe public register of Telegram
Telegram profile photo for CryptoLudik

Channel

CryptoLudik

@CryptoLudik8

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

66subscribers

-3 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-1002365666582
TypeChannel
Username@CryptoLudik8
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/CryptoLudik8

Topic

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 28 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.

Growth

6569677 August 2026 — 69 subscribers10 August 2026 — 69 subscribers23 August 2026 — 68 subscribers31 August 2026 — 66 subscribers2 October 2026 — 65 subscribers12 October 2026 — 66 subscribers667 August 202612 October 2026
6 measurements spanning 66 days, net -3. 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 64–70 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 15:1466+1
2 Oct 2026, 01:4065-1
31 Aug 2026, 11:1666-2
23 Aug 2026, 22:5568-1
10 Aug 2026, 00:3169no change
7 Aug 2026, 16:3769first reading

Engagement

20 posts held, back to 4 November 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 20 posts for this entry, the most recent from 21 January 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

74 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2635.1%
❤2128.4%
👻68.11%
👀45.41%
👍34.05%
🤗34.05%
🥴34.05%
🔥22.70%
🤩22.70%
💔11.35%
😱11.35%
🤔11.35%
🤪11.35%

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

Measured over the 20 most recent posts we hold, published 4 November 2025 to 21 January 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

21 Jan 2026, 14:18 UTC157 views5 reactionsread 10 August 2026

Очікую 2500$-2600$ по Ефіру, від куплю на останні копійки, далі тільки вгору ТОТАЛЬНИЙ ХОЛД, ПЕРЕМОГА БУДЕ💪

❤2👻2👍1

4 Dec 2025, 12:16 UTC218 views4 reactionsread 10 August 2026
Photo

До 6,000$ рукою подати, а ви нервували😄

😁3💔1

24 Nov 2025, 17:14 UTC216 views4 reactionsread 10 August 2026

Це ж памп буде, правильно?

😁3❤1

24 Nov 2025, 17:14 UTC197 views3 reactionsread 10 August 2026
Forwarded from @voynareal

⚡️Адміністрація США готується оголосити й визнати існування інопланетного життя, — The Economic Times 🇺🇦Реальна Війна | Підписатись

😁3

22 Nov 2025, 10:38 UTC165 views4 reactionsread 10 August 2026
Photo

Я не нервую, все по плану, я не нервую, Ефір виросте, нижче уже не буде, я відчуваю, все добре, 800$ за 1 ефір неможливо, неможливо…

😁3❤1

21 Nov 2025, 13:51 UTC139 views4 reactionsread 10 August 2026

SOL також на 500$ добрав

❤2👻1🤩1

21 Nov 2025, 13:44 UTC133 views4 reactionsread 10 August 2026

Відкупив Ефір ще на 1000$, запас хода ще норм, чекаємо

👀3😱1

18 Nov 2025, 07:19 UTC134 views3 reactionsread 10 August 2026

Ринок то походу прав, але Ефіру взагалі по барабану, 3000$ залізно стоїть😐

❤1👍1👻1

14 Nov 2025, 12:59 UTC142 views3 reactionsread 10 August 2026

О вищі сили, дайте зайти в ефір ще по 2500$-2700$. Я зі спокійною душею піду грати в майнкрафт і оформляти перед замовлення на теслу😎

❤1🤩1😁1

14 Nov 2025, 12:42 UTC127 views4 reactionsread 10 August 2026
Photo

ЗАТАРИЛИСЬ, СЮЮЮДААААА💰 По солані точка входу прям кайф, Ефір показує силу, не вистачило впевненості чекати 2900$, хоча думаю до 3000$-3050$ впаде

👻2❤1😁1

13 Nov 2025, 09:19 UTC95 views4 reactionsread 10 August 2026

фух бля, я заєбався з цією «кріптовалютою», пора на пенсію😄

🥴2❤1😁1

13 Nov 2025, 09:01 UTC92 views3 reactionsread 10 August 2026

Просто мислі в слух… Якщо зараз купити Ефір на $5к, то продавши по $6к в разі вильоту я зароблю 3.500$ + 3,000-4,000$ з солани. Вийде +-7,000$ профіту. Якщо посерднитися по 2900$ на 6,000$, то уже продавши по 6,000$ профіт буде складати +- 10,000$ + 3,000$-4,000$ з солани. За таким методом виходить ахуєть скільки бабла, так чому я тоді сиджу і чекаю 3к🤴 В той же час, якщо дочекатися 3к, то це мега консервативно, т…

❤1🤔1🤪1

Showing the 12 most recent of 20 posts we hold for @CryptoLudik8. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“CryptoLudik” (@CryptoLudik8), 66 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/CryptoLudik8.

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.