Telegram RegisterThe public register of Telegram
Telegram profile photo for BettingBaas (FREE)

Channel

BettingBaas (FREE)

@BettingBaasNLVIP

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Telegram's recommendations · Cite this entry

7,480subscribers

-30 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-1002163783132
TypeChannel
Username@BettingBaasNLVIP
DescriptionWij zijn de Speler Schoten Specialist! 🕵️‍♂️ 📲 Voorspellingen op basis van betrouwbare analyses 📥 Vragen? Stuur een bericht via @BettingBaasNL
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/BettingBaasNLVIP

Topic

Gambling & betting — 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 95% 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 the other topics.

Growth

7,4807,6337,556.57 August 2026 — 7,510 subscribers7 August 2026 — 7,510 subscribers10 August 2026 — 7,535 subscribers14 August 2026 — 7,529 subscribers17 August 2026 — 7,530 subscribers20 August 2026 — 7,518 subscribers24 August 2026 — 7,546 subscribers27 August 2026 — 7,545 subscribers30 August 2026 — 7,559 subscribers2 September 2026 — 7,568 subscribers6 September 2026 — 7,576 subscribers11 September 2026 — 7,607 subscribers14 September 2026 — 7,630 subscribers19 September 2026 — 7,633 subscribers30 September 2026 — 7,610 subscribers6 October 2026 — 7,603 subscribers13 October 2026 — 7,586 subscribers16 October 2026 — 7,573 subscribers19 October 2026 — 7,566 subscribers24 October 2026 — 7,545 subscribers27 October 2026 — 7,542 subscribers30 October 2026 — 7,526 subscribers1 November 2026 — 7,508 subscribers5 November 2026 — 7,488 subscribers8 November 2026 — 7,480 subscribers7 August 20268 November 2026
25 measurements spanning 93 days, net -30. 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 7,457–7,656 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
8 Nov 2026, 17:367,480-8
5 Nov 2026, 06:207,488-20
1 Nov 2026, 21:597,508-18
30 Oct 2026, 06:447,526-16
27 Oct 2026, 15:057,542-3
24 Oct 2026, 22:367,545-21
19 Oct 2026, 00:367,566-7
16 Oct 2026, 09:477,573-13
13 Oct 2026, 08:217,586-17
6 Oct 2026, 17:397,603-7
30 Sept 2026, 01:177,610-23
19 Sept 2026, 09:377,633+3
14 Sept 2026, 22:007,630+23
11 Sept 2026, 16:227,607+31
6 Sept 2026, 22:367,576+8
2 Sept 2026, 18:577,568+9
30 Aug 2026, 14:187,559+14
27 Aug 2026, 19:047,545-1
24 Aug 2026, 18:487,546+28
20 Aug 2026, 21:327,518first reading

Engagement

130 posts held, back to 28 July 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.95%
avg views ÷ 7,480 subscribers
Avg views / post
445
51 posts measured
Reaction rate
2.80%
reactions ÷ views · ER floor
Posts in window
53
of 130 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. It is computed over the 47 of 51 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 November 2026
Posts held130 (28 July 2026 – 9 November 2026)
Views total22,710
Reactions total617
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 20:00 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.

What this channel posts

Photos
≈2,450
Videos
≈9
Links
≈8

Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

2,632 reactions across 116 posts, in 7 distinct kinds. The most used accounts for 91.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,39491.0%
🔥1505.70%
👌281.06%
🤝210.798%
🤩190.722%
🏆160.608%
🍾40.152%

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 118 of the 130 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 2,632 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 130 most recent posts we hold, published 28 July 2026 to 9 November 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

Telegram’s own ‘edited’ marker: 10 of 53 posts held from the last 30 days (18.9%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 19:49 UTCviews —

BettingBaas (FREE) pinned «Blijven liken strijders, deze gratis bet willen jullie niet missen!»

9 Nov 2026, 17:41 UTC144 views13 reactionsread 9 November 2026

Blijven liken strijders, deze gratis bet willen jullie niet missen!

❤13

9 Nov 2026, 13:20 UTC255 views7 reactionsread 9 November 2026
Photo

Daar gaan we weer, een héérlijke tennistip om de dag mee te beginnen! 🔥 De komende 3 dagen zullen er voornamelijk tennistips komen, zorg dat je meldingen aan staan want we gaan weer een WINSTREAK bouwen! 💚

❤5🔥2

9 Nov 2026, 09:33 UTC307 views2 reactionsread 9 November 2026
Photo

Wat een heerlijke tips! 🔥 De penalty van Twente was heel welkom in de laatste minuten, verder waren het weer ijzersterke tips! Een prachtige week gehad, donderdag beginnen de interlands weer. Tot nu tijd helaas geen voetbal, maar onze tennis-expert gaat heerlijke tips delen! 💚

❤1🔥1

9 Nov 2026, 09:05 UTC281 views4 reactionsread 9 November 2026
Photo

99% VERDUBBELAAR ✅ Wat de verdubbelaar betreft was het ook weer een fantastische week. De laatste 5 gingen allemaal groen! Vaak maken we het niet moeilijker dan moet maar om deze consistent te winnen is natuurlijk heerlijk! Gefeliciteerd strijders! 💚

❤4

9 Nov 2026, 08:26 UTC211 views3 reactionsread 9 November 2026
Photo

GRATIS SPELER SCHOTEN TIP! ✅ Met zo’n prachtige analyse wisten we eigenlijk al wel dat dit goed moest komen. Uiteindelijk wist Weidmann na 46 minuten al 2 keer te schieten en schoot hij in totaal zelfs 4 keer. 🤝 We gaan deze week misschien weer zo’n tip gratis delen! 💚

❤2🔥1

8 Nov 2026, 09:27 UTC385 views3 reactionsread 9 November 2026
Photo

99% VERDUBBELAAR! ✅ Goedemorgen strijders, dat deze tip goed gaat is natuurlijk geen verassing meer. Maar op een prachtige dag als gisteren hadden we helaas wel meer winst verwacht, jammer. Vandaag nog 1 prachtige dag voordat we donderdag aan de interlandperiode beginnen, wij gaan er alles aan doen om het weekend fantastisch af te sluiten! 💚

❤2🔥1

7 Nov 2026, 09:45 UTC484 views6 reactionsread 9 November 2026
Photo

De laatste dagen waren we weer on-fire met het ODD 6.00 PAKKET! 🔥 Vandaag komt écht de beste van deze week! 🤝

❤5🔥1

7 Nov 2026, 09:00 UTC427 views4 reactionsread 9 November 2026
Photo

Een prachtige vrijdag ✅ Dat de 99% verdubbelaars de laatste tijd wel heel makkelijk groen gaan is geen verassing meer. 🤝 Maar ook deze prachtige high stake odd 3.00 was natuurlijk een hele mooie! 🔥

🔥3❤1

7 Nov 2026, 08:46 UTC339 views2 reactionsread 9 November 2026
Photo

Goedemorgen strijders! ☕️ Deze tennistip hadden jullie nog van ons tegoed. Luca maakte het voor thuispubliek enorm spannend maar dat zijn de mooiste! Hopelijk hebben jullie allemaal geen al te grote kater, want deze zaterdag is een speciale! Be ready! 🔥

❤1🔥1

Showing the 12 most recent of 130 posts we hold for @BettingBaasNLVIP. 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 recorded as deleted after publishing

We recorded 14 posts on @BettingBaasNLVIP as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
19 hours
Seen missing in the last 30 days
9

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Sportybet booking codes
@sporty_bet · 123,226
Telegram ranks this channel #77 of 79 here — alongside 78 others — read 14 August 2026
Bet36_bet365 uk
@bet365_betting_Tips1 · 74,931
Telegram ranks this channel #79 of 85 here — alongside 84 others — read 19 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“BettingBaas (FREE)” (@BettingBaasNLVIP), 7,480 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/BettingBaasNLVIP.

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.