Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐Ÿฆข

Channel

๐Ÿฆข

@unionmoonless

On this record: Growth ยท Engagement ยท Posts ยท Citations ยท Cite this entry

2subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1004394500580
TypeChannel
Username@unionmoonless
Created26 July 2026 โ€” measured โ€” dated from the channelโ€™s first post
First recorded14 August 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 1 September 2026
On Telegramt.me/unionmoonless

Growth

121.510 August 2026 โ€” 1 subscribers14 August 2026 โ€” 1 subscribers24 August 2026 โ€” 2 subscribers10 August 202624 August 2026
3 measurements spanning 14 days, net +1. 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 1โ€“2 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 23:342+1
14 Aug 2026, 10:031no change
10 Aug 2026, 14:011first reading

Engagement

2 posts held, back to 26 July 2026 โ€” 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 2 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Jul 2026, 15:44 UTC25 viewsread 14 August 2026

๐Ÿฅน๐Ÿฅน๐Ÿฅน๐“œ๐’๐’๐’๐’๐’†๐’”๐’” ๐“Š๐’๐’Š๐’๐’๐’”๐Ÿฅน ๐Ÿฅน๐—ธ๐—ฎ๐˜๐—ฒ๐—ฟ๐—ฟ๐—บ๐—น ๐Š๐Ž๐•๐„๐—๐ˆ๐€ ๐…๐‹๐Ž๐Ž๐ƒ ๐ƒ๐€๐‘๐Š ๐๐ˆ๐†๐‡๐“ ๐’๐“๐€๐‘๐‘๐ˆ๐๐† ๐…๐‹๐Ž๐Ž๐ƒ ๐‘ถ๐‘ต๐’€๐‘ฟ ๐‘บ๐‘ช๐‘น๐‘ฐ๐‘ท๐‘ป.๐Ÿ•ฏ๏ธ ๐•๐„๐‹๐€๐‘๐ˆ๐’ ๐…๐‹๐Ž๐Ž๐ƒ ๐•ฏ๐–†๐–—๐– ๐–•๐–†๐–—๐–†๐–‰๐–Ž๐–˜๐–Š crossed sinners ๐’๐‚๐€๐‘๐‹๐„๐“ ๐Œ๐Ž๐Ž๐ ๐ฌ๐ญ๐ž๐ฒ๐ฆ๐จ๐ง ๐Ÿ๐ฅ๐จ๐จ๐

Showing the 2 most recent of 2 posts we hold for @unionmoonless. 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

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

โ€œ๐Ÿฆขโ€ (@unionmoonless), 2 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/unionmoonless.

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.