Telegram RegisterThe public register of Telegram
Telegram profile photo for Baked Beans Returns Announcements

Channel

Baked Beans Returns Announcements

@BakedBeansProjectAnnouncements

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

375subscribers

-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-1001509973930
TypeChannel
Username@BakedBeansProjectAnnouncements
CreatedBetween 1 July 2021 and 6 July 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 14 September 2026
On Telegramt.me/BakedBeansProjectAnnouncements

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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

3753833797 August 2026 — 383 subscribers7 August 2026 — 383 subscribers23 August 2026 — 379 subscribers29 August 2026 — 376 subscribers6 September 2026 — 375 subscribers7 August 20266 September 2026
5 measurements spanning 31 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 374–384 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 22:01375-1
29 Aug 2026, 10:14376-3
23 Aug 2026, 00:14379-4
7 Aug 2026, 02:30383no change
7 Aug 2026, 01:32383first reading

Engagement

20 posts held, back to 6 July 2022the 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 20 posts for this entry, the most recent from 4 May 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

110 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 44.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏4944.5%
🔥2220.0%
👍1917.3%
1412.7%
🎉43.64%
🤩21.82%

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 13 of the 20 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 110 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 July 2022 to 4 May 2024, 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

29 Apr 2024, 16:31 UTC603 views2 reactionsread 7 August 2026

Baked beans merch store live. Store link on dapp www.bakedbeans.app

2

29 Apr 2024, 02:01 UTC605 views4 reactionsread 7 August 2026

Buy back 5 BNB done straight to TVL @bakedbeansreloaded

🔥4

28 Apr 2024, 00:51 UTC582 views2 reactionsread 7 August 2026

We told you first here as soon as we launched. It's still only almost 2000 bnb. Still you know I early. Don't sit on sidelines, join the Telegram, understand and take a call. We don't want our OG community to be left out.

🔥2

26 Apr 2024, 01:10 UTC481 views0 reactionsread 7 August 2026

1300 BNB TVL Soon 1500 BNB You guys were informed first. Still Early. Join the Telegram https://t.me/bakedbeansreloaded

23 Apr 2024, 11:07 UTC468 views5 reactionsread 7 August 2026

Please join vc https://t.me/+PSQEukHnuBE2NTY1

3👍2

22 Apr 2024, 14:38 UTC699 views1 reactionsread 7 August 2026

PRESENTING TO YOU : BAKED BEANS RELOADED Hey there, beloved Baked Beans family! We've been on an incredible journey together, haven't we? From the early days of sowing our first beans to watching our garden flourish beyond our wildest dreams. It's been a ride filled with ups and downs, but through it all, our community has remained the heart and soul of Baked Beans. We're reaching out to reignite that spark and br

1

21 Apr 2024, 03:38 UTC391 views5 reactionsread 7 August 2026

Keep the notifications on for this announcement channel 🔥

🔥4🤩1

Showing the 12 most recent of 20 posts we hold for @BakedBeansProjectAnnouncements. 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.

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.

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

“Baked Beans Returns Announcements” (@BakedBeansProjectAnnouncements), 375 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/BakedBeansProjectAnnouncements.

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.