Channel
@klefkey
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
128subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003995066504 |
|---|---|
| Type | Channel |
| Username | @klefkey |
| Created | Between 1 April 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/klefkey |
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 13:17 | 128 | -3 |
| 14 Sept 2026, 05:20 | 131 | -3 |
| 5 Sept 2026, 20:15 | 134 | +2 |
| 29 Aug 2026, 19:25 | 132 | -4 |
| 22 Aug 2026, 12:46 | 136 | +4 |
| 15 Aug 2026, 01:22 | 132 | +8 |
| 9 Aug 2026, 02:47 | 124 | no change |
| 7 Aug 2026, 18:21 | 124 | +2 |
| 7 Aug 2026, 12:29 | 122 | first reading |
20 posts held, back to 5 August 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
22 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 77.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 77.3% | |
| 👍 | 4 | 18.2% | |
| 🔥 | 1 | 4.55% |
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 11 of the 20 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 August 2026 to 8 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Gn. Thank you again for the feedback today. It goes straight into the queue, and most of it is already fixed. Tomorrow brings something we think you'll enjoy. Worth waking up for. We work on this every day, for you. See you in the morning.
❤1
Dev rewards collected and distributed. 32.6 SOL, split across the four public wallets as always. Growth 60% — 19.56 SOL https://solscan.io/tx/3vkBa2t5xaujJGAy4CrCsLM5eGrUL2Tbs9Kr8BG6YKk6hyDmS3oPwRe8nCBWQFcTzhcmSHPVm289goM1xM1CtZFz Team 25% — 8.15 SOL https://solscan.io/tx/3HUnucM3RdmWhA4v3K91VamXS1que6GGqUobuBZnrkWDsSAFSPQS3P93oTVwVPFZtGmzGUcmtRuAUS9rKGaPJohV Product 10% — 3.26 SOL https://solscan.io/tx/2k4SL6PPrX…
First Key is live. Six builders on Solana. Fifty USDC of Klef credit each. Roughly 45 million tokens on Opus 5. Full rules and applications are in the thread on X. Everything happens there. https://x.com/getKlef/status/2086078604211867790 Go read it, then apply. We're picking six.
Gm Today we're fixing what you reported in the app beta. Every message got read, most are already in the queue. A small addition to web chat lands this weekend. Small, but you'll use it every day. We're also expanding what $KLEF actually does inside Klef. New places where the token matters. We'll show them when they're live, not before. Rest up. We're working.
Gn. We're still getting your feedback and we're grateful for every bit of it. We already know about the issues in the app, but we're holding updates so you're not forced to re-download it ten times a day. So today and tomorrow we gather feedback, and over the weekend we ship new versions with all the fixes rolled in. The goal: submit to Google Play next week, and put out a clean, polished iOS version too. And we h…
❤1🔥1
The first Klef mobile beta is here 📱 This is a beta, so it won't be perfect yet, and that's exactly where you come in. Try it, break it, and send us anything you find. We'll be running hot fixes all weekend so it's polished and ready to submit to Google Play next week, with an iOS app in the works right after. Download it now: · from our site, klefkey.xyz · in the Integrations tab · or via our Linktree: https://lin…
👍2
The spam label on $KLEF is officially gone ✅ Thank you to everyone who flagged it and helped us push this through, we hear you, and we act on it. And thank you Phantom for the quick fix. Cleaner, clearer, and verified across the board.
Transparency isn't a promise. It's a wallet you can watch. From now on, 5% of every deposit goes here to buy back $KLEF, live, on-chain, fully public. No manual claims, no "trust us" That $KLEF is what we pay back to you as cashback, and the more you hold, the higher your cashback and discounts when you use Klef. The wallet, watch every buyback in real time: 94fPVwZmnMweXSy7JyucXVXTxrECsftK3feBYHErgnCx Every $KLEF…
Pushing an update now. The site may be down for a couple of minutes. Back shortly
Gm. Here's today's plan. 1. More backend refinement under the hood. 2. Our transparent buyback system goes live. Until now buybacks were manual, from today they run automatically and anyone can verify them on-chain. 3.Possibly the first Android beta of the Klef app. Let's get to it.
👍2
Gn. Sneak peek from mobile: image gen running clean on your phone. The first open beta is coming soon, and when it drops it'll be live for everyone straight from our site, no waiting. For Google Play we'll need 12 testers who install and use the app for 14 days straight to unlock the store listing. If you're up for it, you'd be directly helping us get there, and we might run an event around it. Rest up. See you to…
Update is live. If you signed up with email, you now have your own wallet built in. Fund it, then send to Klef through the top-up form, in USDC or SOL. You can also top it up by card with our new provider MoonPay, and export your private key anytime. Your wallet, your keys. And for everyone, the top-up flow got a cleaner, simpler redesign. All built to make Klef effortless on mobile.
Showing the 12 most recent of 20 posts we hold for @klefkey. 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.
Named by 5 registered channels — 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Klef” (@klefkey), 128 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/klefkey.
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.