Telegram RegisterThe public register of Telegram
Telegram profile photo for CHECKS

Channel

CHECKS

@checcksa

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 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-1002024503456
TypeChannel
Username@checcksa
CreatedBetween 1 November 2023 and 2 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/checcksa

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:321no change
7 Aug 2026, 12:311first reading

Engagement

20 posts held, back to 2 April 2024the 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 20 posts for this entry, the most recent from 8 May 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
21

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

8 May 2024, 16:51 UTC180 viewsread 14 August 2026

🚀 XCrypto чек на 5 USDT (455.50₽) 🎁 Внутри чека : 15000 активация(й) по 0.000333333 USDT (0.03₽) с реферальной наградой 0.00001333 USDT (0.00₽) https://t.me/xCrUSDBot?start=Cheque-Vs05XfxSimE

8 May 2024, 12:49 UTC165 viewsread 14 August 2026

Мультичек на сумму 0.01 TON ≈ 0.06 USD Сумма одной активации: 0.0001 TON Количество активаций: 100

29 Apr 2024, 10:05 UTC121 viewsread 14 August 2026

A cheque for 50000000.0 RELDT Activations count: 500. Single activation: 100000.0 RELDT 📌 Only for subscribers: auto_club_sng

21 Apr 2024, 08:56 UTC140 viewsread 14 August 2026

A cheque for 485000000.0 RELDT Activations count: 485. Single activation: 1000000.0 RELDT 📌 Only for subscribers: m_club_sng, crypto_indu, checks_previmi

20 Apr 2024, 08:34 UTC296 viewsread 14 August 2026

Мультичек на сумму 0.01 TON ≈ 0.06 USD Сумма одной активации: 0.0001 TON Количество активаций: 100

19 Apr 2024, 18:56 UTC258 viewsread 14 August 2026

Мультичек на сумму 0.01 TON ≈ 0.06 USD Сумма одной активации: 0.0001 TON Количество активаций: 100

19 Apr 2024, 17:33 UTC237 viewsread 14 August 2026

Мультичек на сумму 0.01 TON ≈ 0.06 USD Сумма одной активации: 0.0001 TON Количество активаций: 100

14 Apr 2024, 11:28 UTC174 viewsread 14 August 2026

🚀 XCrypto чек на 0.001700000 ETH (468.08₽) 🎁 Внутри чека : 12500 активация(й) по 0.000000136 ETH (0.04₽) с реферальной наградой 0.00000001 ETH (0.00₽) https://t.me/xCrUSDBot?start=Cheque-XUFVvT6DkZM

10 Apr 2024, 16:14 UTC226 viewsread 14 August 2026

🚀 XCrypto чек на 0.040000000 TON (24.80₽) 🎁 Внутри чека : 2100 активация(й) по 0.000019048 TON (0.01₽) с реферальной наградой 0.00000076 TON (0.00₽) https://t.me/xCrUSDBot?start=Cheque-bZhMDJS3GAn

9 Apr 2024, 17:17 UTC255 viewsread 14 August 2026

🚀 XCrypto чек на 0.002706460 ETH (853.68₽) 🎁 Внутри чека : 20000 активация(й) по 0.000000135 ETH (0.04₽) с реферальной наградой 0.00000001 ETH (0.00₽) https://t.me/xCrUSDBot?start=Cheque-VxpBFfB5AGx

8 Apr 2024, 15:55 UTC257 viewsread 14 August 2026

🚀 XCrypto чек на 0.002793430 ETH (923.50₽) 🎁 Внутри чека : 20000 активация(й) по 0.000000140 ETH (0.05₽) с реферальной наградой 0.00000001 ETH (0.00₽) https://t.me/xCrUSDBot?start=Cheque-WQpISHMOPcH

7 Apr 2024, 15:39 UTC185 viewsread 14 August 2026

🚀 XCrypto чек на 0.000030000 ETH (9.26₽) 🎁 Внутри чека : 1000 активация(й) по 0.000000030 ETH (0.01₽) с реферальной наградой 0.00000000 ETH (0.00₽) https://t.me/xCrUSDBot?start=Cheque-03k3hqeUGMf

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

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

“CHECKS” (@checcksa), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/checcksa.

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.