Telegram RegisterThe public register of Telegram
Telegram profile photo for VIDIO BOKEP LOKAL OFC

Bot

VIDIO BOKEP LOKAL OFC

@ASPANFILEKU_Bot

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

68,020monthly users

-12,342 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID8335707074
TypeBot
Username@ASPANFILEKU_Bot
First recorded11 August 2026
Last confirmed live18 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/ASPANFILEKU_Bot

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

64,94081,10573,022.57 August 2026 — 80,362 monthly users8 August 2026 — 81,093 monthly users9 August 2026 — 81,105 monthly users10 August 2026 — 80,965 monthly users11 August 2026 — 80,965 monthly users12 August 2026 — 80,501 monthly users15 August 2026 — 79,356 monthly users17 August 2026 — 78,582 monthly users18 August 2026 — 78,288 monthly users20 August 2026 — 78,143 monthly users21 August 2026 — 78,038 monthly users23 August 2026 — 78,090 monthly users24 August 2026 — 78,818 monthly users25 August 2026 — 79,012 monthly users26 August 2026 — 78,996 monthly users28 August 2026 — 78,904 monthly users29 August 2026 — 78,776 monthly users31 August 2026 — 78,832 monthly users1 September 2026 — 78,669 monthly users3 September 2026 — 77,251 monthly users7 September 2026 — 78,073 monthly users10 September 2026 — 77,655 monthly users12 September 2026 — 77,489 monthly users14 September 2026 — 77,152 monthly users15 September 2026 — 76,814 monthly users18 September 2026 — 77,880 monthly users30 September 2026 — 74,140 monthly users6 October 2026 — 73,280 monthly users10 October 2026 — 72,170 monthly users13 October 2026 — 71,011 monthly users16 October 2026 — 69,449 monthly users18 October 2026 — 69,203 monthly users19 October 2026 — 68,333 monthly users23 October 2026 — 67,090 monthly users24 October 2026 — 66,066 monthly users25 October 2026 — 65,652 monthly users27 October 2026 — 64,940 monthly users27 October 2026 — 66,598 monthly users28 October 2026 — 67,173 monthly users30 October 2026 — 66,201 monthly users1 November 2026 — 67,778 monthly users3 November 2026 — 66,605 monthly users4 November 2026 — 66,867 monthly users6 November 2026 — 66,766 monthly users7 November 2026 — 66,608 monthly users8 November 2026 — 66,014 monthly users9 November 2026 — 66,680 monthly users11 November 2026 — 66,071 monthly users14 November 2026 — 66,372 monthly users18 November 2026 — 68,020 monthly users68,0207 August 202618 November 2026
50 measurements spanning 102 days, net -12,342. 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 62,515–83,530 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
18 Nov 2026, 01:5168,020+1,648
14 Nov 2026, 23:1466,372+301
11 Nov 2026, 22:0666,071-609
9 Nov 2026, 22:1566,680+666
8 Nov 2026, 13:2066,014-594
7 Nov 2026, 05:3666,608-158
6 Nov 2026, 02:3766,766-101
4 Nov 2026, 06:0766,867+262
3 Nov 2026, 02:1666,605-1,173
1 Nov 2026, 01:0867,778+1,577
30 Oct 2026, 21:4566,201-972
28 Oct 2026, 23:5767,173+575
27 Oct 2026, 22:3966,598+1,658
27 Oct 2026, 01:2164,940-712
25 Oct 2026, 01:3765,652-414
24 Oct 2026, 03:1966,066-1,024
23 Oct 2026, 01:1167,090-1,243
19 Oct 2026, 18:4068,333-870
18 Oct 2026, 18:3869,203-246
16 Oct 2026, 21:5669,449first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

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

“VIDIO BOKEP LOKAL OFC” (@ASPANFILEKU_Bot), 68,020 monthly users as measured 18 November 2026. Telegram Register, tgregister.com/channel/ASPANFILEKU_Bot.

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.