Channel
@lCap0ne
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
75subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002770118033 |
|---|---|
| Type | Channel |
| Username | @lCap0ne |
| Created | Between 1 June 2025 and 8 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/lCap0ne |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 03:09 | 75 | -1 |
| 9 Aug 2026, 21:00 | 76 | no change |
| 7 Aug 2026, 17:06 | 76 | first reading |
10 posts held, back to 8 August 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 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 10 posts for this entry, the most recent from 27 August 2025. An engagement rate over an empty window would be a number about nothing.
10 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 4 | 40.0% | |
| ❤ | 3 | 30.0% | |
| 😭 | 2 | 20.0% | |
| 🌚 | 1 | 10.0% |
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 4 of the 10 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 8 August 2025 to 27 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
@Chucky_bf is the same @lCap0ne Polish child (Scammer) Found old DF account from stealer logs, changed username to impersonate Leakbase admin and begin milking idiots like him. He still crying about Tailmon that he also impersonating him. but failed to hide his silliness 😂 You can see Knox from DF has shared the same IP used by lCap0ne and Chucky_BF: 5.173.145.43 (Poland, Warsaw) For further confirmation you can …
🤣2❤1😭1
lCap0ne thought is a good idea to come back with same username and with the same shit opsec. Of course he will login to DF with his real IP. Retard kid will never learn his lesson. Here is ISP info: { "ip": "5.173.145.43", "hostname": "user-5-173-145-43.play-internet.pl", "city": "Warsaw", "region": "Mazovia", "country": "PL", "loc": "52.2298,21.0118", "org": "AS39603 P4 Sp. z o.o.", "postal": "00-002…
Photo, posted without a caption
Sticker, posted without a caption
❤1
File, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
😭1
This account was owned by a scammer "Kaught" and "lCap0ne" Ironically he got "Kaught" and exposed by @tailmn (tailmon.is) Phone number: +48666125976 ( T-mobile Poland ) He also using his bybit account under his real name. USDT: TUQA5G3TYRS3hvnStGLxjdFwpTse8sbvDW BTC: 1HfcEiJsvzSWfEUjSWgZFtSUCF6PdbhtBe ETH: 0x2b43e8741e0f251537d54098a103d047e95870d2
Yeah, I forgot to mention that @breachforumshn also belongs to this scammer and of course its not official Breachforums channel. GET REKT 😛
"Oh no, my sweet Al Kapuśniaczek! Alka Pona, why won't you answer? My pretty Caponka left me! Please come back! Kapuńska my darling just pick up the phone!" [Frantically dialing phone] "She won't answer to any of her names... my beautiful Kapusta is really gone..." 😭
🤣2❤1🌚1
Showing the 10 most recent of 10 posts we hold for @lCap0ne. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Chucky_BF / lCap0ne Exposed 🚨” (@lCap0ne), 75 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/lCap0ne.
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.