Telegram RegisterThe public register of Telegram
Telegram profile photo for A&M Telegram Delivery

Channel

A&M Telegram Delivery

@AyMTelegramDelivery

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

411subscribers

-17 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001209652534
TypeChannel
Username@AyMTelegramDelivery
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/AyMTelegramDelivery

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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

411428419.56 August 2026 — 428 subscribers7 August 2026 — 428 subscribers14 August 2026 — 427 subscribers23 August 2026 — 422 subscribers7 September 2026 — 418 subscribers14 September 2026 — 417 subscribers28 September 2026 — 416 subscribers9 October 2026 — 411 subscribers6 August 20269 October 2026
8 measurements spanning 64 days, net -17. 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 408–431 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 12:15411-5
28 Sept 2026, 10:02416-1
14 Sept 2026, 18:59417-1
7 Sept 2026, 15:37418-4
23 Aug 2026, 01:03422-5
14 Aug 2026, 15:35427-1
7 Aug 2026, 13:43428no change
6 Aug 2026, 21:17428first reading

Engagement

17 posts held, back to 4 August 2022 — 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 17 posts for this entry, the most recent from 12 October 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Oct 2022, 13:57 UTC461 viewsread 6 August 2026

Buena Día!😁 Pide con AyM Telegram Delivery y te llevamos hasta tu casa los mejores platillos así como los vinos y bebidas que desees!! En breve te actualizamos las ofertas de nuestros establecimientos 🤩👇 @Fuumiyaki 🍣 @MercyBar 🌊 @TaqueroMucho Pide a domicilio sin salir de Telegram con @AyM_Manager

1 Oct 2022, 15:20 UTC689 viewsread 6 August 2026

Buena Día!😁 Pide con AyM Telegram Delivery y te llevamos hasta tu casa los mejores platillos así como los vinos y bebidas que desees!! En breve te actualizamos las ofertas de nuestros establecimientos 🤩👇 @Fuumiyaki 🍣 @MercyBar 🌊 @TaqueroMucho Pide a domicilio sin salir de Telegram con @AyM_Manager

21 Aug 2022, 04:20 UTC338 viewsread 6 August 2026
Forwarded from @ReiSushi_BarPhoto

Comida China de @ReiSushi_Bar Pida por @AyM_Manager

21 Aug 2022, 04:20 UTC377 viewsread 6 August 2026
Forwarded from @ReiSushi_BarPhoto

Photo, posted without a caption

21 Aug 2022, 04:20 UTC304 viewsread 6 August 2026
Forwarded from @ReiSushi_BarPhoto

Entrantes de @ReiSushi_Bar Pida por @AyM_Manager

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“A&M Telegram Delivery” (@AyMTelegramDelivery), 411 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/AyMTelegramDelivery.

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.