Telegram RegisterThe public register of Telegram
Telegram profile photo for Aurum Official English Channel

Channel

Aurum Official English Channel

@aurum_eng

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

27,122subscribers

+1,536 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002206852301
TypeChannel
Username@aurum_eng
DescriptionAurum: Pioneering AI-Driven Solutions for Crypto Asset Management https://linktr.ee/aurum_ecosystem
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live1 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/aurum_eng

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 12 August 2026 and assigned it the closest of 31 fixed categories, at 78% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

25,58627,24526,415.57 August 2026 — 25,586 subscribers7 August 2026 — 25,586 subscribers8 August 2026 — 25,642 subscribers9 August 2026 — 25,686 subscribers10 August 2026 — 25,744 subscribers11 August 2026 — 25,807 subscribers12 August 2026 — 25,868 subscribers14 August 2026 — 25,909 subscribers15 August 2026 — 25,935 subscribers17 August 2026 — 25,986 subscribers18 August 2026 — 26,048 subscribers19 August 2026 — 26,095 subscribers20 August 2026 — 26,154 subscribers21 August 2026 — 26,206 subscribers22 August 2026 — 26,242 subscribers24 August 2026 — 26,295 subscribers25 August 2026 — 26,317 subscribers26 August 2026 — 26,334 subscribers27 August 2026 — 26,358 subscribers28 August 2026 — 26,367 subscribers29 August 2026 — 26,383 subscribers30 August 2026 — 26,405 subscribers31 August 2026 — 26,462 subscribers1 September 2026 — 26,532 subscribers2 September 2026 — 26,583 subscribers4 September 2026 — 26,619 subscribers6 September 2026 — 26,665 subscribers9 September 2026 — 26,928 subscribers12 September 2026 — 27,050 subscribers13 September 2026 — 27,097 subscribers15 September 2026 — 27,127 subscribers17 September 2026 — 27,160 subscribers28 September 2026 — 27,217 subscribers5 October 2026 — 27,192 subscribers9 October 2026 — 27,177 subscribers13 October 2026 — 27,185 subscribers14 October 2026 — 27,202 subscribers15 October 2026 — 27,227 subscribers16 October 2026 — 27,233 subscribers17 October 2026 — 27,245 subscribers18 October 2026 — 27,237 subscribers20 October 2026 — 27,226 subscribers22 October 2026 — 27,212 subscribers23 October 2026 — 27,207 subscribers24 October 2026 — 27,205 subscribers24 October 2026 — 27,199 subscribers26 October 2026 — 27,188 subscribers27 October 2026 — 27,181 subscribers28 October 2026 — 27,173 subscribers29 October 2026 — 27,170 subscribers30 October 2026 — 27,146 subscribers31 October 2026 — 27,132 subscribers1 November 2026 — 27,122 subscribers27,1227 August 20261 November 2026
53 measurements spanning 85 days, net +1,536. 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 25,337–27,494 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)SubscribersChange
1 Nov 2026, 03:2927,122-10
31 Oct 2026, 04:0827,132-14
30 Oct 2026, 06:0627,146-24
29 Oct 2026, 03:2827,170-3
28 Oct 2026, 04:0627,173-8
27 Oct 2026, 02:0527,181-7
26 Oct 2026, 01:4827,188-11
24 Oct 2026, 23:5927,199-6
24 Oct 2026, 00:5527,205-2
23 Oct 2026, 00:0927,207-5
22 Oct 2026, 00:5827,212-14
20 Oct 2026, 19:3027,226-11
18 Oct 2026, 15:4127,237-8
17 Oct 2026, 17:0527,245+12
16 Oct 2026, 14:3527,233+6
15 Oct 2026, 17:0927,227+25
14 Oct 2026, 19:2827,202+17
13 Oct 2026, 10:2927,185+8
9 Oct 2026, 09:1427,177-15
5 Oct 2026, 00:1627,192first reading

Engagement

37 posts held, back to 31 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 132 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
79.1%
avg views ÷ 27,122 subscribers
Avg views / post
21,500
4 posts measured
Reaction rate
1.38%
reactions ÷ views · ER floor
Posts in window
4
of 37 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 October 2026
Posts held37 (31 July 2026 – 16 October 2026)
Views total85,800
Reactions total1,183
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Nov 2026, 15:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,420
Videos
≈48
Links
≈221

Lifetime counters from Telegram’s own channel header, read 1 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

18,075 reactions across 37 posts, in 6 distinct kinds. The most used accounts for 47.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8,52547.2%
👍3,90721.6%
🔥2,06911.4%
👏1,6889.34%
💯9575.29%
🤩9295.14%

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 37 of the 37 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 18,075 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 37 most recent posts we hold, published 31 July 2026 to 16 October 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

16 Oct 2026, 15:33 UTC≈19,700 views183 reactionsread 1 November 2026
Photo

AURUM UPDATE – STARTING IN 30 MINUTES Our AURUM Update with Andrew Isaacs, COO of AURUM Foundation and Co-Founder of Neyro, starts in just 30 minutes! Join us for the latest updates on the audit and recovery process, recent developments, and the next steps for AURUM and Neyro. 🔗 https://us06web.zoom.us/j/86099165198 See you in 30 minutes!

❤98👍33🔥21👏17💯7🤩7

15 Oct 2026, 15:53 UTC≈20,300 views232 reactionsread 1 November 2026
Photo

AURUM UPDATE – RESCHEDULED TO FRIDAY Partners, please note an important schedule change! Today’s AURUM Update with Andrew Isaacs has been rescheduled to Friday, October 16. New important details have emerged regarding the ongoing audit and recovery process. To ensure that we can share the most complete and up-to-date information with our community, we have decided to move the session to Friday. The session will t…

❤102👍66🔥22🤩16👏15💯11

14 Oct 2026, 14:38 UTC≈19,000 views295 reactionsread 1 November 2026
Photo

AURUM UPDATE – RESCHEDULED TO TOMORROW Partners, please note an important schedule change! Today’s AURUM Update with Andrew Isaacs has been rescheduled to tomorrow, Thursday, October 15. The session will take place at the same time. Andrew will share the latest developments within AURUM, provide updates on the ongoing audit and recovery process, and outline the next steps toward restoring operations and further d…

👍124❤103🔥26👏22💯10🤩10

12 Oct 2026, 15:34 UTC≈26,800 views473 reactionsread 1 November 2026
Photo

AURUM UPDATE – WEDNESDAY Partners, We invite you to join our upcoming AURUM Update with Andrew Isaacs, COO of AURUM Foundation and Co-Founder of Neyro. During this session, Andrew will provide an overview of the latest developments within AURUM, share updates on the ongoing audit and recovery process, and discuss the next steps toward restoring operations and further developing AURUM and Neyro infrastructure. 🗓 D…

❤257👍126👏32🔥30💯15🤩13

22 Sept 2026, 15:34 UTC≈42,500 views435 reactionsread 1 November 2026
Photo

AURUM UPDATE – STARTING IN 30 MINUTES The AURUM Update with Andrew Isaacs starts in just 30 minutes. During the session, Andrew will share the latest AURUM updates, including progress across the audit and recovery process, recent developments, and the next steps as AURUM continues the gradual restoration of its products and infrastructure. 🎙 Speaker: Andrew Isaacs — COO of AURUM Foundation and Co-Founder of Neyro …

❤222👍65👏43🔥43💯32🤩30

21 Sept 2026, 13:34 UTC≈44,000 views418 reactionsread 1 November 2026
Photo

AURUM UPDATE – RESCHEDULED TO TUESDAY Partners, Please note that today’s AURUM Update with Andrew Isaacs has been rescheduled to tomorrow, Tuesday, September 22. During the session, Andrew will share the latest AURUM updates, including progress across the audit and recovery process, recent developments, and the next steps as AURUM continues the gradual restoration of its products and infrastructure. 🗓 Date: Tuesd…

❤150👍115🔥56👏46🤩26💯25

21 Sept 2026, 08:40 UTC≈32,600 views346 reactionsread 1 November 2026
Photo

AURUM UPDATE – TODAY Partners, We invite you to join a special AURUM Update with Andrew Isaacs, COO of AURUM Foundation and Co-Founder of Neyro. During the session, Andrew will share the latest AURUM updates, including progress across the audit and recovery process, recent developments, and the next steps as AURUM continues the gradual restoration of its products and infrastructure. 🗓 Date: today 🕓 Time: • 6 PM …

❤223👍61🔥37👏19🤩6

18 Sept 2026, 17:55 UTC≈41,500 views751 reactionsread 1 November 2026
Photo

AURUM UPDATE – MONDAY Partners, We invite you to join a special AURUM Update with Andrew Isaacs, COO of AURUM Foundation and Co-Founder of Neyro. During the session, Andrew will share the latest AURUM updates, including progress across the audit and recovery process, recent developments, and the next steps as AURUM continues the gradual restoration of its products and infrastructure. 🗓 Date: Monday, September 21 …

❤329👍231🔥103👏47💯21🤩20

11 Sept 2026, 05:10 UTC≈48,000 views1,047 reactionsread 1 November 2026
Photo

AURUM Audit Update: First Phase Completed We are pleased to confirm that the first phase of the AURUM audit has been completed. As part of this process, the team has been working to restore access to company accounts that were temporarily frozen on centralized exchanges. ❗️IMPORTANT UPDATE Following the completion of the first audit phase, one of the centralized exchanges has already restored access to the AURUM a…

❤647👍207🔥78👏55💯33🤩27

1 Sept 2026, 07:06 UTC≈60,000 views1,161 reactionsread 1 November 2026
Photo

AURUM Balances Moving to the New Back Office We are pleased to announce that, as part of the ongoing AURUM recovery process, all existing user balances are being transferred to the new secure Back Office. This transition is another important step in moving AURUM to the updated infrastructure and continuing the recovery process. All balances will be transferred to the new Back Office, providing users with access to…

❤635👍231🔥100👏93💯54🤩48

25 Aug 2026, 18:02 UTC≈56,300 views705 reactionsread 1 November 2026
Photo

AURUM Update Regarding Tag Markets We would like to provide an important update regarding the previously announced cooperation with Tag Markets. Following the initial agreement, both teams began preparations for the technical integration. Dedicated communication channels were established, and discussions around the infrastructure, the proposed $5 million trading account, and the integration process were actively un…

❤326👍182👏69🔥56💯41🤩31

24 Aug 2026, 15:32 UTC≈37,400 views317 reactionsread 1 November 2026
Photo

AURUM AUDIT UPDATE STARTS IN 30 MINUTES In just 30 minutes, join us for a special global AURUM Audit Update with Andrew Isaacs, COO of AURUM Foundation and Co-Founder of Neyro. During the session, Andrew will provide the latest updates on the ongoing audit, share the progress made across the recovery process, and outline the next steps as AURUM continues working toward the secure and gradual restoration of its prod…

❤155🤩47👍40💯39👏18🔥18

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

Posts edited after publishing

@aurum_eng edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
24 August 2026

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

“Aurum Official English Channel” (@aurum_eng), 27,122 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/aurum_eng.

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.