🟢 IN Transaction From: 0x42128424380c39fd46937941369e24d6da049955 To: 0x628a6fe299589b4b5a67d4b43ccdcb4821b3d80c Amount: 363340.17259051
![Telegram profile photo for Jasmy [BIFF Cap.]](https://cdn.tgregister.com/av/07/0735cc307fa2b34ee6277ab940045e2eeda0f43efd4684ed4a9aba5e9d33fda6.jpg)
Channel
Jasmy [BIFF Cap.]
@jasmy_biff
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6subscribers
+0 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 | -1001932984938 |
|---|---|
| Type | Channel |
| Username | @jasmy_biff |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jasmy_biff |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:02 | 6 | no change |
| 7 Aug 2026, 05:03 | 6 | first reading |
Engagement
20 posts held, back to 10 March 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 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 20 posts for this entry, the most recent from 10 March 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
🟢 IN Transaction From: 0xfa4d81487ece32e95ae2bee5fc860f189fe163d8 To: 0x34b68b86dfdb2bc111b20c9f88475218dced1653 Amount: 2954906.0
🔴 OUT Transaction From: 0x2cf451e6856d9b8f04ff57b9100da5ae4923a6ce To: 0xfa4d81487ece32e95ae2bee5fc860f189fe163d8 Amount: 2954906.0
🔴 OUT Transaction From: 0xfe2fff5c0b676a873d05e2066bc685375ea4b038 To: 0x40c9574709cf9756d36792c535c6216c1a08d96d Amount: 21854.56916
🔴 OUT Transaction From: 0x628a6fe299589b4b5a67d4b43ccdcb4821b3d80c To: 0xa67c3ea2877140dd2274f7da79cec336d8f4683b Amount: 3600000.0
🔴 OUT Transaction From: 0x1d2a9df4e0d5f0493daeda94f589f00697c40f9d To: 0xf53b90605e3e48d5f015a4451118d93565dc23e1 Amount: 1022749.2799999999
🟢 IN Transaction From: 0xa9d1e08c7793af67e9d92fe308d5697fb81d3e43 To: 0xa5690aa07a23aafd5982c0b7edfd757ab17156f7 Amount: 11512454.84960813
🟢 IN Transaction From: 0x17de1a2ce20b2c50022c8704863bd02068347c1d To: 0xc93115d7f25bbb8a4cf964743337d3769af9ac84 Amount: 194014.2725047
🔴 OUT Transaction From: 0x2cf451e6856d9b8f04ff57b9100da5ae4923a6ce To: 0x41fbba5cb38d22b2d80606406944cedd7c97f6f9 Amount: 3509743.88290961
🟢 IN Transaction From: 0x6c69fa64ec451b1bc5b5fbaa56cf648a281634be To: 0xe4516477adacc6682cf18069475f676a5b5667f9 Amount: 344329.5453668895
🔴 OUT Transaction From: 0x09363887a4096b142f3f6b58a7eed2f1a0ff7343 To: 0x7593aa3fcb8781a24625b43bc1c3c6f270817fc8 Amount: 81367.15520908
🟢 IN Transaction From: 0xa9d1e08c7793af67e9d92fe308d5697fb81d3e43 To: 0xa5690aa07a23aafd5982c0b7edfd757ab17156f7 Amount: 11713214.645181578
Showing the 12 most recent of 20 posts we hold for @jasmy_biff. 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.
Citation-graph rank
Citation-graph rank — 1,338,304 of 1,627,445entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 3 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Jasmy [BIFF Cap.]” (@jasmy_biff), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/jasmy_biff.
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.