Telegram RegisterThe public register of Telegram
Telegram profile photo for The Booking Bible - Waiting List

Channel

The Booking Bible - Waiting List

@TBBWaitingList

On this record: Growth · Engagement · Posts · Cite this entry

656subscribers

-5 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-1001284843134
TypeChannel
Username@TBBWaitingList
Created26 December 2021measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/TBBWaitingList

Growth

656661658.57 August 2026 — 661 subscribers8 August 2026 — 661 subscribers14 August 2026 — 657 subscribers22 August 2026 — 656 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -5. 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 655–662 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 19:04656-1
14 Aug 2026, 21:45657-4
8 Aug 2026, 02:35661no change
7 Aug 2026, 15:51661first reading

Engagement

8 posts held, back to 26 December 2021the 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.

ERR · 30 days
47.8%
avg views ÷ 656 subscribers
Avg views / post
313
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 8 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 August 2026
Posts held8 (26 December 20212 August 2026)
Views total940
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

2 Aug 2026, 08:11 UTC218 viewsread 8 August 2026
Photo

3/3 from the matchday channel. You can gain instant access here: https://sublaunch.com/thebookingbiblematchday

29 Jul 2026, 08:06 UTC400 viewsread 8 August 2026
Photo

For anyone that missed out on the main channel, my matchday channel is OPEN and access is instant. Attached are the stats from last season. You can join here: http://sublaunch.com/thebookingbiblematchday

28 Jul 2026, 09:48 UTC322 viewsread 8 August 2026

Sorry for those that missed out - demand is crazy right now and it’s the only way to make it fair. I’ll try open another spot before the season starts.

29 Jun 2026, 07:55 UTC764 viewsread 8 August 2026

For those wondering, I will be opening limited spaces at the end of July ahead of the start of the new football season.

9 Apr 2024, 11:27 UTC≈9,520 viewsread 8 August 2026

The group is currently FULL. I will post any opportunities to join in this group.

Showing the 8 most recent of 8 posts we hold for @TBBWaitingList. 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.

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

“The Booking Bible - Waiting List” (@TBBWaitingList), 656 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/TBBWaitingList.

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.