Channel

Bigo|Tango|Live18+ | Pulsz Биго|Танго|Биголайв 👧🏼🔞 Pulsz

@bgtt18

On this record: Growth · Engagement · Cite this entry

6,458subscribers

+189 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	-1001448447626
Type	Channel
Username	@bgtt18
Created	Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	28 August 2026
Last confirmed live	28 August 2026
Measurements held	9
On Telegram	t.me/bgtt18

Growth

9 measurements spanning 21 days, net +189. 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 6,238–6,505 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
28 Aug 2026, 19:27	6,458	no change
27 Aug 2026, 08:45	6,458	-6
24 Aug 2026, 17:03	6,464	-10
20 Aug 2026, 21:15	6,474	+35
18 Aug 2026, 03:12	6,439	+90
15 Aug 2026, 02:28	6,349	+59
11 Aug 2026, 13:57	6,290	+20
8 Aug 2026, 07:04	6,270	+1
7 Aug 2026, 14:14	6,269	first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

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.