Telegram RegisterThe public register of Telegram

Channel

Artquack Archive

@Quackhive

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002241893615
TypeChannel
Username@Quackhive
Created9 December 2024 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/Quackhive

Growth

18 August 2026 — 1 subscribers14 August 2026 — 1 subscribers8 August 202614 August 2026
2 measurements spanning 6 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:001no change
8 Aug 2026, 10:471first reading

Engagement

16 posts held, back to 9 December 2024 — 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 pageof 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 16 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
10
Links
1

Lifetime counters from Telegram’s own channel header, read 14 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

2 Apr 2026, 01:53 UTC25 viewsread 14 August 2026
Forwarded from @ArtquaackPhoto

Photo, posted without a caption

6 Jan 2025, 07:43 UTC87 viewsread 14 August 2026
Forwarded from @ArtquaackPhoto

Yoooo! @Artquaack is seeking mutuals. If you're a fellow vibing with art, let's get a subs-for-subs exchange going! Please contact the following: – @Muscleo – @ArtquackBot Accept Art Comm and Art gallery channels 🙌🏻 and please use your main account. Thanks!

9 Dec 2024, 02:35 UTC131 viewsread 14 August 2026

For Mutual Data, please fill with the form below Business/Art Acc : Business/Art Channel : HFW Bot : Link for mutual data : 𓅭𓅭𓅭𓅭𓅭 @Artquaack

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

Republishes

Channels on the register whose posts this channel has forwarded.

Arquè. CLOSE
@Artquaack · 29410 posts

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.

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

“Artquack Archive” (@Quackhive), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Quackhive.

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.