Telegram RegisterThe public register of Telegram
Telegram profile photo for Nubecula: Announcements

Channel

Nubecula: Announcements

@NubeculaAnnouncements

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

63subscribers

+0 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-1001918734344
TypeChannel
Username@NubeculaAnnouncements
CreatedBetween 1 April 2023 and 9 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live7 October 2026
Measurements held4
Confirmed unchanged2 times, most recently 7 October 2026
On Telegramt.me/NubeculaAnnouncements

Topic

Software piracy — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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

626362.57 August 2026 — 63 subscribers10 August 2026 — 63 subscribers23 August 2026 — 62 subscribers25 September 2026 — 63 subscribers7 August 202625 September 2026
4 measurements spanning 49 days. 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–63 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 17:5863+1
23 Aug 2026, 06:1462-1
10 Aug 2026, 03:1763no change
7 Aug 2026, 09:2963first reading

Engagement

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

Reaction mix

41 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 73.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3073.2%
👏614.6%
👍37.32%
🙏24.88%

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 11 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 41 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 9 May 2023 to 1 July 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

1 Jul 2025, 14:37 UTC526 views0 reactionsread 10 August 2026

Auto Order Doordash bot is back! » @NubeculaII_Bot - Delivery and Pickup - NEW $20-$25 subtotals - 40% OFF w FREE DELIVERY - Automatically places the order for you (no more long wait times, and messed up orders) - NEW Credit deposit feature for crypto (keep a balance you can instantly use to place an order) - Use the built in support system by clicking the speech bubble for any assistance w the bot USA ONLY 24/7 …

Signed Nube

14 Apr 2025, 21:32 UTC235 views3 reactionsread 10 August 2026

In regards to Grubhub Pickup: As of today; I will stop accepting orders from all locations that are listed as open for 24 hours. The reasoning provided is that these stores operate in a way which is obstructive to my current process. This leads to several complications. Regarding one of those complications; with consideration towards my process, I make it a point to try and maximize the anonymity of the customer. …

👍3

Signed Nube

29 Apr 2024, 01:11 UTC731 views4 reactionsread 10 August 2026

Nubecula will be closed indefinitely. Until I have the time and ability to operate the service in a sufficient manner; the service will remain closed. Loyalty Customers: My older customers or customers high in loyalty are invited to join my loyalty channel. In this channel I will have trusted staff that may take your orders whenever they're active, however it's not a guarantee. I will continue to do some orders fro…

❤4

Signed Nubek

3 Feb 2024, 01:37 UTC377 views2 reactionsread 10 August 2026

Bot is down at the moment. Should be back up soon

❤2

Signed Nubek

2 Dec 2023, 18:24 UTC626 viewsread 10 August 2026
Photo

New Service: Stop&Shop Offering groceries, home essentials, and more at 50% of the total. Order via the bot » @Nubecula_bot

Signed Nubek

9 Nov 2023, 17:50 UTC476 viewsread 10 August 2026
Photo

New Service: Doordash Retail Offering groceries, Sephora, and electronics. Order via the bot » @Nubecula_bot

Signed Nubek

23 Oct 2023, 21:36 UTC333 viewsread 10 August 2026

Now offering Taco Bell pickup 50% off with a $30 minimum total Order via the bot » @Nubecula_bot

Signed Nubek

18 Oct 2023, 19:27 UTC354 viewsread 10 August 2026

Check out our new Loyalty system by messaging @Nubecula_bot and typing /loyalty Referrals = credits

Signed Nubek

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

26 May 2023, 23:18 UTCFinal Results19 voters

At what time would you prefer us to open services for Grubhub?

  1. 10:30 CDT26%
  2. 11:00 CDT5%
  3. 12:00 CDT5%
  4. 13:00 CDT21%
  5. don't care nerd42%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 9 May 2023 to 1 July 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Nubecula: Announcements” (@NubeculaAnnouncements), 63 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/NubeculaAnnouncements.

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.