Telegram RegisterThe public register of Telegram
Telegram profile photo for Karta - Crypto card & wallet

Bot

Karta - Crypto card & wallet

@karta

2 usernames

On this record: Topic · Growth · Engagement · Citations · Cite this entry

31,946monthly users

+1,612 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID7810267753
TypeBot
Usernames@karta @KartaWalletBot
First recorded13 August 2026
Last confirmed live28 September 2026
Measurements held47
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/karta

Topic

Crypto & trading — 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 9 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.

Growth

30,33436,65933,496.56 August 2026 — 30,334 monthly users7 August 2026 — 30,404 monthly users7 August 2026 — 30,404 monthly users8 August 2026 — 31,720 monthly users9 August 2026 — 31,720 monthly users10 August 2026 — 31,707 monthly users11 August 2026 — 31,707 monthly users13 August 2026 — 31,707 monthly users14 August 2026 — 31,707 monthly users14 August 2026 — 32,595 monthly users14 August 2026 — 32,595 monthly users15 August 2026 — 33,021 monthly users16 August 2026 — 33,021 monthly users18 August 2026 — 33,409 monthly users18 August 2026 — 33,409 monthly users19 August 2026 — 33,675 monthly users19 August 2026 — 33,675 monthly users20 August 2026 — 33,823 monthly users20 August 2026 — 33,823 monthly users23 August 2026 — 34,423 monthly users23 August 2026 — 34,423 monthly users24 August 2026 — 34,833 monthly users24 August 2026 — 34,833 monthly users26 August 2026 — 34,882 monthly users26 August 2026 — 34,882 monthly users28 August 2026 — 36,659 monthly users28 August 2026 — 36,659 monthly users29 August 2026 — 36,452 monthly users30 August 2026 — 36,452 monthly users31 August 2026 — 36,235 monthly users31 August 2026 — 36,235 monthly users1 September 2026 — 34,769 monthly users1 September 2026 — 34,769 monthly users3 September 2026 — 34,697 monthly users5 September 2026 — 33,380 monthly users6 September 2026 — 33,380 monthly users7 September 2026 — 33,072 monthly users9 September 2026 — 33,072 monthly users12 September 2026 — 31,406 monthly users12 September 2026 — 31,927 monthly users13 September 2026 — 31,927 monthly users15 September 2026 — 31,541 monthly users15 September 2026 — 31,388 monthly users17 September 2026 — 31,398 monthly users17 September 2026 — 31,625 monthly users25 September 2026 — 31,345 monthly users28 September 2026 — 31,946 monthly users31,9466 August 202628 September 2026
47 measurements spanning 54 days, net +1,612. 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”. The vertical axis spans 29,385–37,608 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 47
Measured (UTC)Monthly usersChange
28 Sept 2026, 22:3831,946+601
25 Sept 2026, 05:0231,345-280
17 Sept 2026, 20:4031,625+227
17 Sept 2026, 10:1831,398+10
15 Sept 2026, 19:2131,388-153
15 Sept 2026, 08:0031,541-386
13 Sept 2026, 20:1631,927no change
12 Sept 2026, 18:0031,927+521
12 Sept 2026, 00:0131,406-1,666
9 Sept 2026, 15:0033,072no change
7 Sept 2026, 23:2133,072-308
6 Sept 2026, 09:4233,380no change
5 Sept 2026, 01:0033,380-1,317
3 Sept 2026, 22:4234,697-72
1 Sept 2026, 15:1334,769no change
1 Sept 2026, 03:5934,769-1,466
31 Aug 2026, 17:4336,235no change
31 Aug 2026, 03:0536,235-217
30 Aug 2026, 01:2736,452no change
29 Aug 2026, 19:0436,452first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

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.

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

“Karta - Crypto card & wallet” (@karta), 31,946 monthly users as measured 28 September 2026. Telegram Register, tgregister.com/channel/karta.

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.