Telegram RegisterThe public register of Telegram

Bot

pizza 🍕

@kpixabot

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

19,172monthly users

-1,538 since we began measuring on 3 November 2026

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

Register entry

Telegram ID8599539619
TypeBot
Username@kpixabot
First recorded3 November 2026
Last confirmed live17 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/kpixabot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 17 November 2026 and assigned it the closest of 31 fixed categories, at 98% 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

18,54321,30219,922.53 November 2026 — 20,710 monthly users3 November 2026 — 20,710 monthly users4 November 2026 — 21,245 monthly users5 November 2026 — 21,302 monthly users7 November 2026 — 19,444 monthly users8 November 2026 — 19,753 monthly users9 November 2026 — 19,261 monthly users11 November 2026 — 19,047 monthly users14 November 2026 — 18,543 monthly users17 November 2026 — 19,172 monthly users19,1723 November 202617 November 2026
10 measurements spanning 15 days, net -1,538. 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 18,129–21,716 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
17 Nov 2026, 22:2919,172+629
14 Nov 2026, 15:1118,543-504
11 Nov 2026, 12:4819,047-214
9 Nov 2026, 16:4719,261-492
8 Nov 2026, 12:0719,753+309
7 Nov 2026, 07:3119,444-1,858
5 Nov 2026, 06:2021,302+57
4 Nov 2026, 05:1721,245+535
3 Nov 2026, 02:2720,710no change
3 Nov 2026, 02:1720,710first 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“pizza 🍕” (@kpixabot), 19,172 monthly users as measured 17 November 2026. Telegram Register, tgregister.com/channel/kpixabot.

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.