4703630000075693|09|26|167 Approved✅

Channel
LIVE CC | FREE LIVE CC
@liveccfreelivecc
On this record: Topic · Growth · Engagement · Posts · Cite this entry
15subscribers
-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 | -1002161991494 |
|---|---|
| Type | Channel |
| Username | @liveccfreelivecc |
| Created | Between 1 June 2024 and 2 August 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 18 November 2026 |
| On Telegram | t.me/liveccfreelivecc |
Topic
Hacking & security — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 17:45 | 15 | -1 |
| 17 Sept 2026, 21:00 | 16 | -1 |
| 11 Aug 2026, 20:30 | 17 | no change |
| 7 Aug 2026, 18:36 | 17 | first reading |
Engagement
20 posts held, back to 2 August 2024 — 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 2 April 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
5137787901232808|10|29|207 Approved✅
5524330358722541|06|26|324 Approved✅
5521910657604673|04|29|430 Approved✅
5133060011836239|01|30|359 Approved✅
4427422137741982|02|31|855 Approved✅
5177465402192372|03|29|368 Approved✅
Card -» 4100390614725469|11|28|555 Status -» 𝗔𝗽𝗽𝗿𝗼𝘃𝗲𝗱 ✅ Response -» Approved Gateway -» Braintree Auth BIN Info -» VISA - CREDIT - TRADITIONAL Bank -» CITIBANK, N.A.- COSTCO Country -» UNITED STATES 🇺🇸
Card -» 4271783848973728|04|28|984 Status -» 𝗔𝗽𝗽𝗿𝗼𝘃𝗲𝗱 ✅ Response -» Approved Gateway -» Braintree Auth BIN Info -» VISA - DEBIT - CLASSIC Bank -» REGIONS BANK Country -» UNITED STATES 🇺🇸 Time -» 12.6s Seconds
5220940201012861|02|31|525 Approved✅
CC: 5404044989456743|08|2028|643 Status: Approved ✅ Response: Card added Gateway: Stripe Bank: FIRST HAWAIIAN BANK Category: RETAIL Type: DEBIT DEBIT MASTERCARD ENHANCED Country: UNITEDSTATES - 840 Took: 5.13s
LIVE CC | FREE LIVE CC pinned Deleted message
Showing the 12 most recent of 20 posts we hold for @liveccfreelivecc. 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“LIVE CC | FREE LIVE CC” (@liveccfreelivecc), 15 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/liveccfreelivecc.
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.