Telegram RegisterThe public register of Telegram
Telegram profile photo for PizzaBot Portal πŸ•

Channel

PizzaBot Portal πŸ•

@pizzabotsol

On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Citations Β· Cite this entry

161subscribers

-8 since we began measuring on 7 August 2026

Risers and fallers across the register Β· movement among entries of Under 1,000.

Register entry

Telegram ID-1002018111010
TypeChannel
Username@pizzabotsol
Created7 May 2024 β€” measured β€” dated from the channel’s first post
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 5 September 2026
On Telegramt.me/pizzabotsol

Growth

1611691657 August 2026 β€” 169 subscribers8 August 2026 β€” 169 subscribers14 August 2026 β€” 163 subscribers21 August 2026 β€” 161 subscribers7 August 202621 August 2026
4 measurements spanning 13 days, net -8. 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 160–170 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 00:43161-2
14 Aug 2026, 21:57163-6
8 Aug 2026, 15:16169no change
7 Aug 2026, 12:44169first reading

Engagement

11 posts held, back to 7 May 2024 β€” the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute β€” we hold 11 posts for this entry, the most recent from 8 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 20s
Average length
52s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel β€” not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no β‰ˆ mark.

Reaction mix

126 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ”₯5644.4%
❀3830.2%
😎1411.1%
πŸ‘129.52%
πŸ‘43.17%
πŸ‘Œ21.59%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities β€” πŸ™ is thanks in one channel and mourning in another β€” so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one β€” 4.34K, 1.2M β€” so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post β€” not by adding up the per-emoji breakdown above β€” those same posts carry 126 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 7 May 2024 to 8 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Jun 2025, 10:08 UTC93 views4 reactionsread 8 August 2026
Forwarded from @WatcherGuruVideo

Buying a Domino's pizza with Bitcoin back in 2010, when it was worth $0.96 @WatcherGuru

πŸ”₯4

19 May 2025, 17:44 UTC161 views3 reactionsread 8 August 2026
Video

How many $PIZZA can you buy with 10,000 $BTC? πŸ•

πŸ”₯3

19 Dec 2024, 15:53 UTC263 views6 reactionsread 8 August 2026
Photo

Photo, posted without a caption

πŸ‘4πŸ”₯2

16 Dec 2024, 10:42 UTC346 views6 reactionsread 8 August 2026
Photo

$PIZZA =10,000 BTC again πŸ•πŸ«΅πŸ»

πŸ‘3πŸ”₯3

16 Nov 2024, 14:02 UTC530 views24 reactionsread 8 August 2026
Video

We are determined to bring original $PIZZA value to 10,000 BTC. $900,000,000 πŸ’ΈπŸ’° JOIN the Revolution!

πŸ”₯15❀8πŸ‘1

11 Sept 2024, 18:10 UTCβ‰ˆ1,050 views23 reactionsread 8 August 2026
Video

Last 24M $PIZZA for grab πŸ•πŸ˜ŽπŸ’° @sol_pizzabot

❀14πŸ”₯5πŸ‘4

16 Aug 2024, 10:00 UTC964 views11 reactionsread 8 August 2026
Photo

Join PizzaBot Sniper Community πŸ•

❀7πŸ”₯4

14 May 2024, 15:07 UTCβ‰ˆ1,420 views17 reactionsread 8 August 2026
Video

How to buy $PIZZA ? πŸ”₯πŸš€

πŸ”₯9😎8

14 May 2024, 12:16 UTCβ‰ˆ2,250 views12 reactionsread 8 August 2026
Photo

πŸ•πŸ”₯Exciting News! Our telegram trading bot is now live at @Sol_PizzaBot, offering buy & burn πŸ”₯ on Solana! Plus, you can also join our presale directly on the same bot! We’ve allocated 100,000,000 $PIZZA tokens for presale, but hurry-it ends in just 2 days! Don’t miss out! πŸš€ @pizzabotsol

πŸ”₯7❀5

8 May 2024, 20:22 UTC890 views20 reactionsread 8 August 2026
Photo

Introducing PizzaBot: Your Crypto Sniper Community’s Ultimate Solution! πŸ• PizzaBot brings together the crypto sniper community, addressing their trading challenges with innovative features. Our upcoming upgrades include PizzaSniper bot that auto snipes based on specific conditions, PizzaParty bot that can be assigned to a trading group for collaborative trading, PizzaScanner bot that will scan the market for new opp…

😎6❀4πŸ‘4πŸ”₯4πŸ‘Œ2

Showing the 11 most recent of 11 posts we hold for @pizzabotsol. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked β‰ˆ was rounded by Telegram before we ever saw it β€” t.me prints views in full below 1,000 and to three significant figures above, so β‰ˆ1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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 21 August 2026 β€” this entry's latest reading, not the date you are reading this.

β€œPizzaBot Portal πŸ•β€ (@pizzabotsol), 161 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/pizzabotsol.

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.