Telegram RegisterThe public register of Telegram
Telegram profile photo for AARDVARK

Channel

AARDVARK

@aardvarks

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

1,449subscribers

+22 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001201468840
TypeChannel
Username@aardvarks
Created11 May 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/aardvarks

Growth

1,4261,4491,437.56 August 2026 — 1,427 subscribers6 August 2026 — 1,427 subscribers6 August 2026 — 1,431 subscribers9 August 2026 — 1,428 subscribers12 August 2026 — 1,427 subscribers16 August 2026 — 1,426 subscribers19 August 2026 — 1,430 subscribers23 August 2026 — 1,434 subscribers26 August 2026 — 1,444 subscribers28 August 2026 — 1,443 subscribers1 September 2026 — 1,447 subscribers5 September 2026 — 1,449 subscribers6 August 20265 September 2026
12 measurements spanning 30 days, net +22. 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,423–1,452 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 10:011,449+2
1 Sept 2026, 05:571,447+4
28 Aug 2026, 21:531,443-1
26 Aug 2026, 06:361,444+10
23 Aug 2026, 06:591,434+4
19 Aug 2026, 07:531,430+4
16 Aug 2026, 18:031,426-1
12 Aug 2026, 18:461,427-1
9 Aug 2026, 16:021,428-3
6 Aug 2026, 15:141,431+4
6 Aug 2026, 07:481,427no change
6 Aug 2026, 05:471,427first reading

Engagement

16 posts held, back to 27 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 16 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Aug 2026, 18:51 UTC≈72 views6 reactionsread 6 August 2026
Forwarded from @bladesgosoft

https://www.youtube.com/watch?v=ZXeMW6SpSDI

4 Aug 2026, 10:45 UTC≈139 views3 reactionsread 6 August 2026

Если вдруг были мысли кормить трубкозуба или чесать манула Тимошу... https://t.me/Moscowzoo_official/11136

31 Jul 2026, 21:02 UTC≈194 views9 reactionsread 6 August 2026
Photo

заброшка дня: градирня электростанции IM в Шарлеруа, Бельгия → на карте Шарлеруа долгое время был одним из главных индустриальных центров Бельгии, а эта градирня — частью крупной угольной электростанции, построенной еще в 1921 году. Через нее проходили тысячи тонн воды, использовавшейся для охлаждения оборудования. Закрыли станцию в 2007 году

30 Jul 2026, 11:17 UTC≈264 views6 reactionsread 6 August 2026
Video

Торговцы ящерицами. Саудовская Аравия, 60е

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

Свидетели и Егоры
@swideteli · 22,5073 postsВольный художник | Вероника Шелухо
@nika_shelukhooo · 1832 postsSo far, so good
@the_high_council_of_frens · 12,7792 postsbat stash
@battnest · 41 postБОГЕМА ПИТЕРСКАЯ (нишевый телеграм-канал)
@bogemasranaya · 30,2731 postinto the void because i'm annoyed
@itvbia · 33,4601 postЦитаты Егора Летова в стиле metamodern ism
@letovmodern · 1431 postresort
@resortagain · 5,5441 postdefiantly reactionary
@shizorasisttalking · 121 postВОЛКОВ МЫСЛИ ВСЛУХ
@volkov_thoughts · 171 post

Republishes

Channels on the register whose posts this channel has forwarded.

soft blade (FKA depth and clarity)
@bladesgosoft · 6,5821 post

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

Names

Channels on the register whose handles appear in this channel's posts.

Московский зоопарк
@Moscowzoo_official · 159,8321 post

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

“AARDVARK” (@aardvarks), 1,449 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/aardvarks.

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.