Telegram RegisterThe public register of Telegram
Telegram profile photo for Oqtepa Lavash | Delivery

Bot

Oqtepa Lavash | Delivery

@oqtepalavash_bot

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

48,098monthly users

+530 since we began measuring on 6 August 2026

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

Register entry

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

Topic

Ecommerce storefront — 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 59% 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

42,76755,82649,296.56 August 2026 — 47,568 monthly users6 August 2026 — 47,628 monthly users8 August 2026 — 47,849 monthly users9 August 2026 — 47,201 monthly users10 August 2026 — 46,109 monthly users11 August 2026 — 44,947 monthly users12 August 2026 — 44,947 monthly users14 August 2026 — 45,089 monthly users15 August 2026 — 44,518 monthly users17 August 2026 — 44,404 monthly users18 August 2026 — 44,355 monthly users19 August 2026 — 43,739 monthly users21 August 2026 — 43,846 monthly users24 August 2026 — 43,124 monthly users25 August 2026 — 42,941 monthly users26 August 2026 — 42,767 monthly users27 August 2026 — 45,029 monthly users29 August 2026 — 45,598 monthly users30 August 2026 — 46,106 monthly users2 September 2026 — 48,110 monthly users5 September 2026 — 47,225 monthly users9 September 2026 — 48,146 monthly users11 September 2026 — 49,033 monthly users13 September 2026 — 49,627 monthly users15 September 2026 — 51,160 monthly users16 September 2026 — 53,023 monthly users19 September 2026 — 53,255 monthly users25 September 2026 — 55,826 monthly users4 October 2026 — 53,686 monthly users8 October 2026 — 53,659 monthly users13 October 2026 — 54,211 monthly users16 October 2026 — 52,997 monthly users17 October 2026 — 52,548 monthly users19 October 2026 — 51,230 monthly users21 October 2026 — 51,202 monthly users22 October 2026 — 51,439 monthly users24 October 2026 — 51,223 monthly users26 October 2026 — 51,076 monthly users27 October 2026 — 50,499 monthly users29 October 2026 — 50,221 monthly users31 October 2026 — 50,192 monthly users1 November 2026 — 50,107 monthly users3 November 2026 — 49,367 monthly users5 November 2026 — 49,150 monthly users7 November 2026 — 49,281 monthly users8 November 2026 — 49,394 monthly users9 November 2026 — 49,795 monthly users11 November 2026 — 50,056 monthly users14 November 2026 — 50,104 monthly users18 November 2026 — 48,098 monthly users48,0986 August 202618 November 2026
50 measurements spanning 104 days, net +530. 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 40,808–57,785 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, 00:5048,098-2,006
14 Nov 2026, 18:2850,104+48
11 Nov 2026, 19:4950,056+261
9 Nov 2026, 21:5949,795+401
8 Nov 2026, 12:2049,394+113
7 Nov 2026, 07:5649,281+131
5 Nov 2026, 09:0949,150-217
3 Nov 2026, 05:4149,367-740
1 Nov 2026, 08:5950,107-85
31 Oct 2026, 10:4650,192-29
29 Oct 2026, 12:5850,221-278
27 Oct 2026, 12:0950,499-577
26 Oct 2026, 11:4151,076-147
24 Oct 2026, 13:2651,223-216
22 Oct 2026, 10:0451,439+237
21 Oct 2026, 03:1851,202-28
19 Oct 2026, 23:4751,230-1,318
17 Oct 2026, 18:4852,548-449
16 Oct 2026, 15:2752,997-1,214
13 Oct 2026, 03:1154,211first 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 16 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.

“Oqtepa Lavash | Delivery” (@oqtepalavash_bot), 48,098 monthly users as measured 18 November 2026. Telegram Register, tgregister.com/channel/oqtepalavash_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.