Telegram RegisterThe public register of Telegram
Telegram profile photo for Lololoshka YouTube

Channel

Lololoshka YouTube

@Lololoshka_lovelyy_video

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

3,008subscribers

-195 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002426936879
TypeChannel
Username@Lololoshka_lovelyy_video
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live19 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Lololoshka_lovelyy_video

Topic

Gaming — 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 14 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

3,0083,2033,105.57 August 2026 — 3,203 subscribers11 August 2026 — 3,188 subscribers14 August 2026 — 3,174 subscribers17 August 2026 — 3,160 subscribers20 August 2026 — 3,144 subscribers23 August 2026 — 3,132 subscribers26 August 2026 — 3,124 subscribers30 August 2026 — 3,108 subscribers1 September 2026 — 3,092 subscribers6 September 2026 — 3,075 subscribers10 September 2026 — 3,075 subscribers11 September 2026 — 3,055 subscribers15 September 2026 — 3,043 subscribers19 September 2026 — 3,008 subscribers7 August 202619 September 2026
14 measurements spanning 42 days, net -195. 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 2,979–3,232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 06:203,008-35
15 Sept 2026, 02:413,043-12
11 Sept 2026, 08:183,055-20
10 Sept 2026, 23:523,075no change
6 Sept 2026, 04:413,075-17
1 Sept 2026, 17:443,092-16
30 Aug 2026, 03:453,108-16
26 Aug 2026, 20:243,124-8
23 Aug 2026, 18:283,132-12
20 Aug 2026, 08:473,144-16
17 Aug 2026, 13:463,160-14
14 Aug 2026, 12:583,174-14
11 Aug 2026, 07:113,188-15
7 Aug 2026, 19:003,203first 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.

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

“Lololoshka YouTube” (@Lololoshka_lovelyy_video), 3,008 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Lololoshka_lovelyy_video.

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.