Telegram RegisterThe public register of Telegram
Telegram profile photo for ARCΛNA

Channel

ARCΛNA

@arcanaoi

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

31subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003750649175
TypeChannel
Username@arcanaoi
CreatedBetween 1 February 2026 and 17 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/arcanaoi

Growth

303331.510 August 2026 — 30 subscribers10 August 2026 — 31 subscribers11 August 2026 — 31 subscribers18 August 2026 — 33 subscribers1 September 2026 — 32 subscribers9 September 2026 — 31 subscribers3110 August 20269 September 2026
6 measurements spanning 31 days, net +1. 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 30–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 18:5931-1
1 Sept 2026, 05:0832-1
18 Aug 2026, 12:3433+2
11 Aug 2026, 03:3131no change
10 Aug 2026, 12:1031+1
10 Aug 2026, 00:1630first reading

Engagement

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

Reaction mix

99 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 25.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 57986462856113102712525.3%
custom 52019180550844759442323.2%
custom 57989113237481791342222.2%
custom 58326484808368205922121.2%
custom 530118587755529948833.03%
custom 530082550832432898922.02%
custom 579854850209088309922.02%
custom 583265176219183496211.01%

Custom emoji. Every row above is a 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 12 of the 20 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 99 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 17 April 2026 to 8 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

8 Aug 2026, 19:25 UTCviews —1 reactionsread 11 August 2026

Posted without readable text

custom 52019180550844759441

17 Jul 2026, 00:17 UTC91 views1 reactionsread 11 August 2026
Sticker

Sticker, posted without a caption

custom 57986462856113102711

15 Jul 2026, 13:02 UTC374 views14 reactionsread 11 August 2026
Photo

’ what made us fight for the arcana? ’ 👠 wondering why? LORE. PART 1. COMING SOON.

custom 57986462856113102715custom 58326484808368205925custom 57989113237481791343custom 52019180550844759441

8 Jul 2026, 13:19 UTC192 views1 reactionsread 11 August 2026

наша перша перемога у шоу!! дуже вдячні усім за підтримку 🌹

custom 58326484808368205921

26 Jun 2026, 14:00 UTC348 views13 reactionsread 11 August 2026
File

𝖈𝖍𝖆𝖕𝖙𝖊𝖗 𝟏: 𝖉𝖗𝖆𝖜 𝖆 𝖈𝖆𝖗𝖉. 🤍🤍🤍🤍 𝔱𝔥𝔢 𝔣𝔬𝔬𝔩. 🤍🤍🤍🤍🤍🤍🤍🤍 🎲 — 🏮𝓇𝒸𝒶𝓃𝒶 🌹 🌟 OT6 >> we caught the fool — the wild hunt continues 🌫️ 🤍 @arcanaoi 🏴 @dAdeleLabels

custom 57989113237481791346custom 52019180550844759443custom 58326484808368205923custom 57986462856113102711

26 Jun 2026, 14:00 UTC320 views13 reactionsread 11 August 2026
File

𝖈𝖍𝖆𝖕𝖙𝖊𝖗 𝟏: 𝖉𝖗𝖆𝖜 𝖆 𝖈𝖆𝖗𝖉. 🤍🤍🤍🤍 𝔱𝔥𝔢 𝔣𝔬𝔬𝔩. 🤍🤍🤍🤍🤍🤍🤍🤍 🎲 — 🏮𝓇𝒸𝒶𝓃𝒶 🌹 🌟 OT6 >> the chase led us deeper than we expected 🌫️ 🤍 @arcanaoi 🏴 @dAdeleLabels

custom 58326484808368205925custom 57989113237481791344custom 57986462856113102713custom 52019180550844759441

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

Names

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

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

“ARCΛNA” (@arcanaoi), 31 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/arcanaoi.

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.