Telegram RegisterThe public register of Telegram
Telegram profile photo for CRYPTO-AI PAYMENTS

Channel

CRYPTO-AI PAYMENTS

@cryptolitecoin_ai

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

27subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001424234806
TypeChannel
Username@cryptolitecoin_ai
DescriptionCRYPTO-AI LTC verified payments channel. ✅ @cryptoAI_newsfeed
CreatedBetween 1 April 2019 and 16 August 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 October 2026
Measurements held2
On Telegramt.me/cryptolitecoin_ai

Growth

2711 Aug 2026, 22:17 — 27 subscribers11 Aug 2026, 22:30 — 27 subscribers11 Aug 2026, 22:1711 Aug 2026, 22:30
2 measurements taken within a single day. 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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:3027no change
11 Aug 2026, 22:1727first reading

Engagement

20 posts held, back to 16 August 2019 — 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 16 August 2019. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
≈1,710

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Recent posts

16 Aug 2019, 09:20 UTC741 viewsread 11 August 2026

☔ WOW! Galileo Robarts reinvested 0.00623067 LTC (0.46$) from balance.

16 Aug 2019, 09:18 UTC728 viewsread 11 August 2026

☔ WOW! Gorkemtek reinvested 0.29436505 LTC (21.78$) from balance.

16 Aug 2019, 09:00 UTC737 viewsread 11 August 2026

☔ WOW! almahyra reinvested 0.008 LTC (0.59$) from balance.

16 Aug 2019, 08:52 UTC733 viewsread 11 August 2026

☔ WOW! Aisha Madinatou reinvested 0.002 LTC (0.15$) from balance.

16 Aug 2019, 08:43 UTC732 viewsread 11 August 2026

☔ WOW! Olands reinvested 0.00219368 LTC (0.16$) from balance.

16 Aug 2019, 08:40 UTC682 viewsread 11 August 2026

💧 WOW! Vladislavs invested 2.05000000 LTC (149.71$) from an external Litecoin wallet! Welcome to CRYPTO-AI Vladislavs. TXID: 92f19bd85191418f6368a0ded1923e7a0ebd9d6bdeb02195d6e77852d3410c7e

16 Aug 2019, 08:29 UTC425 viewsread 11 August 2026

☔ WOW! Davo04 reinvested 0.00344139 LTC (0.25$) from balance.

16 Aug 2019, 08:15 UTC353 viewsread 11 August 2026

☔ WOW! emreozkans reinvested 0.00146589 LTC (0.11$) from balance.

16 Aug 2019, 07:57 UTC323 viewsread 11 August 2026

☔ WOW! atsushi_kenzo reinvested 0.02888322 LTC (2.12$) from balance.

16 Aug 2019, 07:54 UTC298 viewsread 11 August 2026

☔ WOW! Rakun reinvested 0.00194908 LTC (0.14$) from balance.

16 Aug 2019, 07:40 UTC261 viewsread 11 August 2026

☔ WOW! vinicius9725 reinvested 0.00222916 LTC (0.17$) from balance.

16 Aug 2019, 07:33 UTC264 viewsread 11 August 2026

💧 WOW! Alexander Peiffer invested 0.00636000 LTC (0.47$) from an external Litecoin wallet! Welcome to CRYPTO-AI Alexander Peiffer. TXID: 7e8a5e47f0525345d27287f23ad18eda221c4e1d9aa01065b22e291ab2e3b0b9

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

Mentions

Named by 1 registered channel — 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.

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.

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

“CRYPTO-AI PAYMENTS” (@cryptolitecoin_ai), 27 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/cryptolitecoin_ai.

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.