Channel
@B4U_Hotels
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
104subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002143117572 |
|---|---|
| Type | Channel |
| Username | @B4U_Hotels |
| Description | Information to speed things along at booking time! |
| Created | Between 1 November 2023 and 14 March 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/B4U_Hotels |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 09:31 | 104 | no change |
| 7 Aug 2026, 12:24 | 104 | first reading |
19 posts held, back to 14 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 19 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
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.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Booking Info / Requirements HUB pinned «GIVEAWAY ALERT POSTED IN @NCXGIVEAWAYS http://t.me/@NCXGIVEWAYS https://t.me/ncxgiveaways/5573»
GIVEAWAY ALERT POSTED IN @NCXGIVEAWAYS http://t.me/@NCXGIVEWAYS https://t.me/ncxgiveaways/5573
Booking Info / Requirements HUB pinned Deleted message
### Effortless Bookings Await with NightCX Bookings! 🌎✨ Fast, easy & trustworthy. Secure transactions with @CoinEscrowBot. ### Worldwide Services 🌟 - Flights & Hotels 🛫🏨 - Ikea (US) & Airbnb 🛍🏡 - Tickets & Car Rentals 🎟🚗 ### Guidelines 📝 - Be prepared - Book 48hrs+ in advance for best rates - Last-minute bookings available ### Pricing & Insurance ALWAYS INCLUDED💰✅ - Crypto: 40% fee - CashApp/Zelle: 50% fee (CASH…
Big vouch, easy check in, and easy flight, no troubles whatsoever. Always my goto guy! Big vouch for @hades155!
Booking Info / Requirements HUB pinned «✈️ Services I Offer: - Flights US-CA 🛫 - Hotels 🏨 - Ikea US 🛍 - Airbnb 🏡 - Gift Card Requests 🎁 - Tickets 🎟 - Rentals 🚗 - & Many More ✨ ⏳ Used any services such as Agoda or iKea? Let me know to save time! 💼 Insurance and Pricing: - All bookings are insured…»
✈️ Services I Offer: - Flights US-CA 🛫 - Hotels 🏨 - Ikea US 🛍 - Airbnb 🏡 - Gift Card Requests 🎁 - Tickets 🎟 - Rentals 🚗 - & Many More ✨ ⏳ Used any services such as Agoda or iKea? Let me know to save time! 💼 Insurance and Pricing: - All bookings are insured until checkout ✅ - Pricing: - 40% for Crypto 💰 - 50% for CashApp/Zelle 💵 unless stated otherwise DM: @Hades155
Booking Info / Requirements HUB pinned a photo
On for bookings! @hades155
Video, posted without a caption
Booking Info / Requirements HUB pinned «You can now place your orders in queue with our bot! @b4uBuddy_bot Automatically get it done and placed within a few hours!»
Showing the 12 most recent of 19 posts we hold for @B4U_Hotels. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Booking Info / Requirements HUB” (@B4U_Hotels), 104 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/B4U_Hotels.
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.