Telegram RegisterThe public register of Telegram
Telegram profile photo for Aux Records

Channel

Aux Records

@aux_records

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

475subscribers

+11 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002259510334
TypeChannel
Username@aux_records
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/aux_records

Growth

464475469.57 August 2026 — 464 subscribers8 August 2026 — 464 subscribers14 August 2026 — 465 subscribers22 August 2026 — 467 subscribers30 August 2026 — 471 subscribers8 September 2026 — 474 subscribers14 September 2026 — 475 subscribers7 August 202614 September 2026
7 measurements spanning 38 days, net +11. 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 462–477 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 20:16475+1
8 Sept 2026, 06:16474+3
30 Aug 2026, 15:36471+4
22 Aug 2026, 15:44467+2
14 Aug 2026, 16:49465+1
8 Aug 2026, 04:48464no change
7 Aug 2026, 19:05464first reading

Engagement

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

Reaction mix

103 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 37.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3937.9%
custom 52652493536137425311918.4%
custom 53056411716854995101817.5%
custom 52650463820492712651615.5%
👍98.74%
👎10.971%
🔥10.971%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 5 of the 5 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 103 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 10 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Aug 2026, 12:59 UTC117 views26 reactionsread 8 August 2026
Photo

В наличии! Базовая футболка от Aux Records Размеры от L до XXL Цвета: orange, royal, red, navy, charchol grey Цена - 2000₽ По поводу приобретения писать @Rednec_KKK

custom 526504638204927126586custom 53056411716854995106custom 52652493536137425315👎1

29 Jul 2026, 06:55 UTC350 views27 reactionsread 8 August 2026
File

File, posted without a caption

10custom 52652493536137425318custom 52650463820492712654custom 53056411716854995104🔥1

29 Jul 2026, 06:55 UTC264 views16 reactionsread 8 August 2026
Photo

Raze - Bio-Raze E.P. Original Gabber Records - OG010 #Gabber #Hardcore Tracklist: 1. Raze Your Mind - 180 BPM 2. Party - 170 BPM 3. In Effect - 200 BPM 4. Insects - 200 BPM 5. Hear This - 170 BPM All tracks written, produced and mastered by Timofey Emelyanenko Design by Artem Makashov Published by Aux Distribution Release link: band.link/raze_bio_raze_e_p Contacts: [email protected] t.me/aux_records

6custom 52652493536137425314custom 53056411716854995104custom 52650463820492712652

10 Jul 2026, 07:15 UTC≈1,410 views18 reactionsread 8 August 2026
File

File, posted without a caption

9👍5custom 53056411716854995102custom 52650463820492712651custom 52652493536137425311

10 Jul 2026, 07:15 UTC≈1,570 views16 reactionsread 8 August 2026
File

File, posted without a caption

8👍4custom 53056411716854995102custom 52650463820492712651custom 52652493536137425311

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

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

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“Aux Records” (@aux_records), 475 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/aux_records.

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.