from the top!

Channel
LuckyChuninCCG Claims
@LUCKYCHUNINCLAIMS
On this record: Topic · Growth · Engagement · Posts · Cite this entry
13subscribers
-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 | -1003340908257 |
|---|---|
| Type | Channel |
| Username | @LUCKYCHUNINCLAIMS |
| Created | Between 1 November 2025 and 18 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 12 October 2026 |
| On Telegram | t.me/LUCKYCHUNINCLAIMS |
Topic
Gaming — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 23:01 | 13 | -1 |
| 9 Sept 2026, 21:55 | 14 | -1 |
| 11 Aug 2026, 23:46 | 15 | no change |
| 7 Aug 2026, 18:18 | 15 | first reading |
Engagement
20 posts held, back to 18 January 2026 — 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 18 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
LuckyChuninCCG Claims pinned «LUCKYCHUNINCCG 1st EVER CLAIM SALE 18 JAN 2026 9PM ORs/ARs/GPs/LRs/MRs cards this time round! Before we start, let's keep these in mind as we go~ 1. First come first serve! Fastest fingers to replies "Claim" to the post gets the card. 2. Most cards have…»
thank u to everyone who joined our first claim sale!! i'll bill all claims by the end of the night thank you! ❤️
[FREEBIES] for those who claimed something. FCFS please leave some for others too haha if end of the night no one take, feel free to claim all
MR-008 SUSANOO SASUKE $30 - SUPER RARE only 1 in stock
and last but not least, the big banger of the night:
MR-012 REANIMATED ITACHI $15
MR-011 EIGHT GATES MIGHT GUY $10
MR-009 MINATO KCM2 $10
MR-003 HASHIRAMA SENJU $10
mooooving on to the last rarity - MR 😄
LR-004 ITACHI BLISTER PACK $10
Showing the 12 most recent of 20 posts we hold for @LUCKYCHUNINCLAIMS. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“LuckyChuninCCG Claims” (@LUCKYCHUNINCLAIMS), 13 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/LUCKYCHUNINCLAIMS.
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.