Channel
@juicybio
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,859subscribers
-17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002077582441 |
|---|---|
| Type | Channel |
| Username | @juicybio |
| Created | 9 February 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/juicybio |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 22:38 | 1,859 | -2 |
| 24 Aug 2026, 18:03 | 1,861 | -5 |
| 21 Aug 2026, 10:34 | 1,866 | -3 |
| 18 Aug 2026, 06:23 | 1,869 | -3 |
| 14 Aug 2026, 23:47 | 1,872 | -4 |
| 11 Aug 2026, 09:17 | 1,876 | -1 |
| 8 Aug 2026, 10:03 | 1,877 | +1 |
| 7 Aug 2026, 15:47 | 1,876 | no change |
| 7 Aug 2026, 15:34 | 1,876 | first reading |
19 posts held, back to 9 February 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 19 posts for this entry, the most recent from 16 August 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 videos 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.
199 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 60.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 120 | 60.3% | |
| 🔥 | 45 | 22.6% | |
| 👍 | 8 | 4.02% | |
| 😁 | 8 | 4.02% | |
| 🤯 | 7 | 3.52% | |
| 🥰 | 7 | 3.52% | |
| 👏 | 4 | 2.01% |
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 18 of the 19 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 199reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 9 February 2024 to 16 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.
🚀 Big News: TrafficRecovery™ is Now FREE on All Paid Plans Plus - we have also updated our pricing across all plans. So now is the best time to start earning with our affiliate program. 👉 Start here: Affiliate Article 🔒If you created an account on or before Aug 15, 2025: ✅ You keep the original, cheaper pricing, forever ✅ Applies even if you’ve never subscribed or cancel and return later ✅ TrafficRecovery™ is n…
❤21🔥3👍1👏1
🚀 Direct Links Are Back on Juicy.bio You asked, we delivered. Direct Linking is now live again and better than ever. ✅ Fully Meta-Compliant We rebuilt the system from the ground up to meet Meta’s latest policies on adult content. Any 18+ content is automatically flagged and gated with a fast, high-converting age check. ✅ Compatible with Traffic Recovery & Deeplinking The new 18+ gate is designed for speed and full…
❤8👍3🔥1
🚨Big Update: New Affiliate System is LIVE!🚨 We’ve officially upgraded our affiliate system to Tolt—a major improvement over the old setup. It’s faster, more reliable, and comes with automated payouts. 👉 To start using the new system, follow these simple steps: https://help.juicy.bio/en/articles/11364343-juicy-affiliate-program-how-it-works 🧾 Pending commissions from the old system? If you had any unpaid affiliat…
❤10
JUICY.BIO 🤝🏼 TXT.COM - SMS Deeplinks Are Live! We just dropped a new update! You can now add SMS buttons to your landing pages. When a visitor taps it, it instantly opens their Messages app with your number pre-filled. Works on both iOS and Android. 🚀Why this is big We’ve partnered with TXT.COM — a platform that lets creators chat and sell content directly over text, with built-in payment support. - Texts get way…
❤8🔥3😁2
Hey everyone, We’ve been rolling out some big upgrades to Juicy over the past couple of weeks: 🚀 New Servers with Faster Speeds On June 27, Juicy traffic surged from 50k to 1M daily visitors. We’ve since completely overhauled our infrastructure with vastly improved performance. Expect much faster load times and better conversions! 🌍Alternate domains In case our domain gets restricted on a social media platform, we…
❤7😁1
🚨 Two Critical Announcements 1. Meta Compliance Update — Completed ✅ We’ve finished updating all user links. Every direct link has now been converted into a Landing Page that includes an 18+ age warning screen when clicking on adult links — fully compliant with Meta’s latest content guidelines. Meta’s new enforcement policies clearly state that any redirect to adult content must be preceded by a visible warning. S…
❤11🔥1
🚨 Urgent Update: Direct Links Are Being Phased Out We’ve received reliable information that Meta will begin banning direct deep links to adult content within a few days. This could result in potential shadowbans and account restrictions. Furthermore, their new guidelines state that any adult link in a Link-in-bio style page (even in custom domains) that lacks an “I’m 18+” confirmation window is also at risk for sha…
❤9😁2
Everything is fully back and operational for the past 30 mins 🚀
🔥6🤯1😁1
❗Attention! Our servers are currently under attack by DDoS, resulting in page lag. Our team is actively working on resolving the issue as soon as possible. Thank you.
❤7😁2
Use the code “BUILTDIFFERENT” to get 50% off your first purchase
❤7
🚨 Industry Update 🚨 One of the biggest link-in-bio platforms just got banned by Instagram. While others go down, Juicy.bio is alive and thriving. Fully operational. No disruptions. Built different. Keep building. We’ve got your back. — Team Juicy 💦
🔥5❤3
🍒 Standard Link-In-Bio's are killing your OnlyFans conversions Watch this 👇 Video 1: Linktree, Beacons & Hoo-be = 💀 ✖️ Visitor clicks your link ✖️ Forced to select platform (OnlyFans) ✖️ Then enters Date of Birth manually ✖️ Taps Continue to load a second redirect ✖️ Opens in Instagram’s in-app browser (user is automatically logged out of OnlyFans) ✖️ Has to manually log in — if they even bother ✖️ Result: Lost atte…
❤6🥰4
Showing the 12 most recent of 19 posts we hold for @juicybio. 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 — 77,422 of 1,626,935entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Juicy.bio” (@juicybio), 1,859 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/juicybio.
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.