Dazzle is available tonight! Sweet 18yo with top tier GFE. wa.link/terminal21

Channel
#2 Terminal21
@beautyvaultHQ
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
6,982subscribers
+372 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003011833655 |
|---|---|
| Type | Channel |
| Username | @beautyvaultHQ |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/beautyvaultHQ |
Topic
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 04:38 | 6,982 | +32 |
| 11 Sept 2026, 10:18 | 6,950 | +80 |
| 7 Sept 2026, 00:16 | 6,870 | +47 |
| 2 Sept 2026, 14:57 | 6,823 | +31 |
| 30 Aug 2026, 23:08 | 6,792 | +25 |
| 27 Aug 2026, 19:18 | 6,767 | +27 |
| 24 Aug 2026, 14:57 | 6,740 | +22 |
| 20 Aug 2026, 17:23 | 6,718 | +58 |
| 17 Aug 2026, 12:49 | 6,660 | -7 |
| 14 Aug 2026, 06:57 | 6,667 | +46 |
| 10 Aug 2026, 21:11 | 6,621 | +11 |
| 7 Aug 2026, 13:13 | 6,610 | no change |
| 7 Aug 2026, 12:01 | 6,610 | first reading |
Engagement
45 posts held, back to 6 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 10 pages 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 45 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 49s
- Average length
- 12s
Measured directly from 9 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.
Reaction mix
22 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 90.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 90.9% | |
| 🔥 | 2 | 9.09% |
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 17 of the 45 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 45 most recent posts we hold, published 6 August 2026 to 20 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.
Recent posts
🥂🥂 SPECIAL PROMO 🥂🥂 Venus 100/45/1 Jazz 100/45/1 Josie 100/45/1 Ruth 110/45/1 Ivory 110/45/1 Dazzle 120/45/1 wa.link/terminal21
Let's come play w Venus! 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
❤1
Jazz. She's a keeper 😉 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
❤1
Ivory is accepting all races now! http://wa.link/terminal21
❤2
Ruth 🔥 tingtong babe! 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
Dazzle. Top GFE! 💘 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
#2 Terminal21 pinned Deleted message
Jazz. Jin Hojiak!! 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
Ivory. Enjoy a long deep fk... 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
River. No words can describe. 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
❤1
Dazzle, 18yo very willing to service! 💬 Bookings: wa.link/terminal21 📸 Full Gallery: https://y.hn/babehause 🚬: wa.link/sgboss 🔓 Bypass Channel Block: https://y.hn/bypasstelegram
Showing the 12 most recent of 45 posts we hold for @beautyvaultHQ. 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.
Posts edited after publishing
@beautyvaultHQ edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 August 2026
Forward network
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“#2 Terminal21” (@beautyvaultHQ), 6,982 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/beautyvaultHQ.
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.