Telegram RegisterThe public register of Telegram
Telegram profile photo for arsip @naciros

Channel

arsip @naciros

@jokimlyesha

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

1subscribers

-175 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001608170023
TypeChannel
Username@jokimlyesha
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/jokimlyesha

Growth

117688.59 August 2026 — 176 subscribers9 August 2026 — 175 subscribers25 August 2026 — 164 subscribers31 August 2026 — 156 subscribers9 September 2026 — 1 subscribers9 August 20269 September 2026
5 measurements spanning 31 days, net -175. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 11:371-155
31 Aug 2026, 07:44156-8
25 Aug 2026, 01:17164-11
9 Aug 2026, 18:12175-1
9 Aug 2026, 02:01176first reading

Engagement

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

Recent posts

7 Aug 2026, 17:47 UTC18 viewsread 9 August 2026

tanyain duls stok nya yhh bub😇 kadang kesalip sama yang lain

7 Aug 2026, 06:32 UTCviews —

✿⠟🪻🐰 Toko—Nayes 𓂂˙ ♫ pinned «Ready WDP fast : 26.000 - 29.000 slow : 22.500 - 24.500 semi : 25.000 - 26.000 1id1x : 18.500 - 21.000 fast = proses 5m – 1j slow = proses 3 – 4h semi = proses 1 – 2h 1id1x = proses 3 – 4h»

7 Aug 2026, 06:32 UTC25 viewsread 9 August 2026

Ready WDP fast : 26.000 - 29.000 slow : 22.500 - 24.500 semi : 25.000 - 26.000 1id1x : 18.500 - 21.000 fast = proses 5m – 1j slow = proses 3 – 4h semi = proses 1 – 2h 1id1x = proses 3 – 4h

28 Jun 2026, 16:22 UTCviews —

✿⠟🪻🐰 Toko—Nayes 𓂂˙ ♫ pinned «DISCORD NEEDS — VILOG Decoration 33.000 IDR ➡️ 23k Decoration 39.500 IDR ➡️ 29k Decoration 52.000 IDR ➡️ 42k Decoration 65.000 IDR ➡️ 55k Decoration 71.000 IDR ➡️ 60k Decoration 78.000 IDR ➡️ 65k Decoration 91.000 IDR ➡️ 80k Decoration 96.000 IDR ➡️ 85k Decoration…»

28 Jun 2026, 15:19 UTC69 viewsread 9 August 2026

DISCORD NEEDS — VILOG Decoration 33.000 IDR ➡️ 23k Decoration 39.500 IDR ➡️ 29k Decoration 52.000 IDR ➡️ 42k Decoration 65.000 IDR ➡️ 55k Decoration 71.000 IDR ➡️ 60k Decoration 78.000 IDR ➡️ 65k Decoration 91.000 IDR ➡️ 80k Decoration 96.000 IDR ➡️ 85k Decoration 100.000 IDR ➡️ 90k Decoration 145.000 IDR ➡️ 120k > Bundle lainnya pake harga satuan Nitro Boost (Gift) ➡️ 87k (nogar) Nitro Boost 3 Month ➡️ 55k (Cek A

27 Jun 2026, 11:18 UTC55 viewsread 9 August 2026

Ready starlight Sl basic po 1b — 33k Sl basic pertengahan bulan — 35k Sl basic fast (delay 8d) — 38k Sl prem (po) — 80k

Showing the 12 most recent of 19 posts we hold for @jokimlyesha. 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 1 registered channel — 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“arsip @naciros” (@jokimlyesha), 1 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/jokimlyesha.

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.