Telegram RegisterThe public register of Telegram

Channel

ARSIP LOSKON

@loskonarsip

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

5subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002147549552
TypeChannel
Username@loskonarsip
CreatedBetween 1 April 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/loskonarsip

Growth

565.56 August 2026 — 6 subscribers12 August 2026 — 6 subscribers13 August 2026 — 5 subscribers6 August 202613 August 2026
3 measurements spanning 7 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 5–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:575-1
12 Aug 2026, 19:486no change
6 Aug 2026, 13:196first reading

Engagement

12 posts held, back to 25 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 5 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 07s
Average length
25s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

5 Jul 2025, 05:05 UTC98 viewsread 12 August 2026
Forwarded from @ofcsensusPhoto

Photo, posted without a caption

5 Jul 2025, 05:05 UTC99 viewsread 12 August 2026
Forwarded from @loskonbysSticker

Sticker, posted without a caption

5 Jul 2025, 05:05 UTC99 viewsread 12 August 2026
Forwarded from @loskonbysPhoto

w nya apa? waduh comeback kita

5 Jul 2025, 05:04 UTC96 viewsread 12 August 2026
Forwarded from @offcpahayPhoto

ㅤ ㅤ♡ ❍ ⌲ •• 𝗟𝗶𝗸𝗲𝗱 𝗯𝘆 @loskonbys and 3.789.999 others. ➥ PAHÃY × LOSKONBOYS

5 Jul 2025, 05:04 UTC86 viewsread 12 August 2026
Forwarded from @loskonbysPhoto

ㅤ ㅤ LOSKON – PAHĀY t.me/loskonbys – t.me/offcpahay

5 Jul 2025, 05:04 UTC86 viewsread 12 August 2026
Forwarded from @loskonbysSticker

Sticker, posted without a caption

5 Jul 2025, 05:04 UTC90 viewsread 12 August 2026
Forwarded from @loskonbysPhoto

ㅤ LOSKON Ft. SAMPOΞRNA ㅤ Kita gak butuh banyak suara, ㅤ cukup deru mesin dan sebat bareng

5 Jul 2025, 05:04 UTC91 viewsread 12 August 2026
Forwarded from @loskonbysSticker

Sticker, posted without a caption

18 May 2025, 12:12 UTC86 viewsread 12 August 2026
Video

ini jj kmrin yak di gc gabisa ngirim video @ChildHold @lutoIol @addhif R pahay , abim

6 May 2025, 02:58 UTC88 viewsread 12 August 2026
Forwarded from @ofclextroFile

♡ ㅤㅤ ❍ㅤㅤ ⌲ •• ⎙ liked by @OFCLEXTRO and 254.887.231 others 🌟 ─ ·  · Special collaboration with @ofclextro! Really glad to team up and build stronger connections between our squad and others through this collab. Thanks a lot for being part of it — looking forward to the next one. See you brosist! 🌟 ─ ·  · spesial tag : @lilholex @untoldrpw @diesatcom @tracoxx @ofcramoneszz @usbalak @

6 May 2025, 02:58 UTC94 viewsread 12 August 2026
Forwarded from @jabierofcFile

‘‘ⓘ─── COLLABORATION AL JABIER @jabierofc 🤩🤩 inviting the active squad on @telegram to collaboration as a sign of unity. " special tag " : @costelord @thefoger @baceno @offcmohay @berculley @TheCoolerMange @unitedcoser @untoldrpw @ofcramoneszz @wardoettpride @ofcinfinite @ofcgorvez @ofclextro @loskonbys @lilholex @TheStormbrings @laskayefolks @diesatcom @offcpahay 🤩 from our side, we hope we will meet in other col

25 Apr 2025, 03:28 UTC94 viewsread 12 August 2026
Forwarded from @swimfiveFile

⭐️as a representative of @swimfive 😒 I would like to express my deepest gratitude to all team members who have participated in this collaboration, the dedication, hard work, and spirit of togetherness that you have shown means a lot to our shared success, see you in the next collaboration y'all SPECIAL TAG 🦋 @wardoettpride @bertyies @loskonbys @ofceldefeat @stacrank @thescattles @lazeraxofc @falbosboys @untoldrpw @of

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

Citation-graph rank

Citation-graph rank — 752,627 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

“ARSIP LOSKON” (@loskonarsip), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/loskonarsip.

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.