Telegram RegisterThe public register of Telegram
Telegram profile photo for Connor's Catalogue

Channel

Connor's Catalogue

@MageyChannelThah

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

29subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001436525254
TypeChannel
Username@MageyChannelThah
DescriptionChannels owned by me aka Connor and the ones I'm an admin in.
Created28 October 2018 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/MageyChannelThah

Growth

299 August 2026 — 29 subscribers11 August 2026 — 29 subscribers9 August 202611 August 2026
2 measurements spanning 2 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 28–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:3229no change
9 Aug 2026, 10:5629first reading

Engagement

18 posts held, back to 28 October 2018 — 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 18 posts for this entry, the most recent from 5 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
8

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

8 Jan 2020, 05:59 UTCviews —

Connor's Catalogue pinned «Replacement channels for; Lewdiful Ladies, Wallpaper Dump, and My Sleep/Relaxation playlist are now live. Lewdiful Ladies 2.0: @LadyLewdiful Wallpaper Dump 2.0: @WowPapers Sleep/Chill playlist 2.0: @ChillaxBro»

Showing the 12 most recent of 18 posts we hold for @MageyChannelThah. 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Connor's Catalogue” (@MageyChannelThah), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/MageyChannelThah.

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.