Telegram RegisterThe public register of Telegram
Telegram profile photo for LEVIEOSTRIX ARCHIVES

Channel

LEVIEOSTRIX ARCHIVES

@levieostrix_atb

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

2subscribers

+0 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-1001589173565
TypeChannel
Username@levieostrix_atb
Created12 September 2021measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live6 September 2026
Measurements held2
On Telegramt.me/levieostrix_atb

Growth

27 August 2026 — 2 subscribers13 August 2026 — 2 subscribers7 August 202613 August 2026
2 measurements spanning 7 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”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 20:092no change
7 Aug 2026, 01:222first reading

Engagement

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

What this channel posts

Links
1

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

27 Jul 2026, 20:17 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

25 May 2023, 15:52 UTC146 viewsread 13 August 2026
File

ㅤ 𝗖𝗔𝗡𝗗𝗜𝗗𝗔𝗧𝗘 𝗠𝗘𝗠𝗕𝗘𝗥 ㅤㅤ 𝗟𝗘𝗩𝗜𝗘𝗢𝗦𝗧𝗥𝗜𝗫 ㅤㅤ ━━━━━◤ ★ ◢━━━━━ ★𝐏ut dn candidate #CALVXMEMB jika sedang oplink, gunakan #LVXOPLINK ★ 𝐏ut dn : lvx or 188 (tap autocopy) ★ 𝐄xample : lvx or 188 mano put it at the very front of your name. ★ 𝐀ttentionequip your attribute properly. prospective members must use the opmem and oplink attributes until there is a directive to release. ❙❚❙❚❘❙❘❚❘❙❘❚❘❙❘❚❙❚❘❙❘❚❙❙❚

15 Mar 2022, 16:16 UTC261 viewsread 13 August 2026

FORMAT : I'm @.use qualified and ready to become a Levieos figters! send to @LEVIEOSTRIXOFC_BOT

16 Feb 2022, 12:45 UTC514 viewsread 13 August 2026

ㅤㅤㅤ 𝗥𝗘𝗦𝗜𝗚𝗡𝗔𝗧𝗜𝗢𝗡 𝗟𝗘𝗧𝗧𝗘𝗥 Melalui surat ini, saya di sini dengan (nama) meminta izin untuk left dari @LEVIEOSTRIX_OFC, karena (alasan) dan saya dengan segera melepaskan semua atribut yang terkait dengan @LEVIEOSTRIX_OFC terimakasih telah memberi kesempatan kepada saya untuk bergabung dan menjadi bagian dari levieos, Thus I submit this letter of self-reference, if there are wrong words, I apologize. Thank you for your

18 Nov 2021, 02:29 UTC≈1,310 viewsread 13 August 2026
File

buat yang tidak bisa mengedit idc bisa kunjungi web di bawah ini https://twb.nz/levieostrix13

14 Sept 2021, 07:56 UTC≈1,990 viewsread 13 August 2026

ㅤㅤ✘ 𝗥𝗨𝗟𝗘𝗦 𝗢𝗣𝗠𝗘𝗠𝗕 / 𝗢𝗣𝗟𝗜𝗡𝗞 ✘ ━━━━━━◤ ★ ◢━━━━━━ • all gender allowed. • wajib subs ch @LEVIEOSTRIX_OFC @TONGKRONGANLEVIEOSTRIX @OFC_LEVIEOSTRIX • menggunakan atribut yang sudah disiapkan • niat dan siap untuk berbaur dengan semua member • wajib mengikuti semua event yg sudah di adakan • utamakan solidaritas dan kesopanan • bisa menjaga nama baik LEVIEOSTRIX • tidak cepu, two face or baperan. • bu

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

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“LEVIEOSTRIX ARCHIVES” (@levieostrix_atb), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/levieostrix_atb.

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.