Channel

Kos blue

@kaxlopsia

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

15subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID	-1001543824068
Type	Channel
Username	@kaxlopsia
Created	Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	14 August 2026
Last confirmed live	15 August 2026
Measurements held	2
Confirmed unchanged	1 time, most recently 15 August 2026
On Telegram	t.me/kaxlopsia

Growth

2 measurements taken within a single day. 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 14–16 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
15 Aug 2026, 00:38	15	no change
14 Aug 2026, 12:16	15	first reading

Engagement

20 posts held, back to 18 February 2025 — the 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 20 posts for this entry, the most recent from 25 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 May 2026, 03:01 UTC15 viewsread 14 August 2026

Hai, banyak usn baru belum aku update, nanti yuaa aku sdang sibuxx

16 Jan 2026, 16:45 UTC49 viewsread 14 August 2026

@ angppau adopted! Thank you so much kak K, i hope you have a nice day🫶🏻

14 Dec 2025, 12:47 UTC55 viewsread 14 August 2026

@ larakatseyye @ lafortezasophia @ megankatseyee @ jeongyoonchaek @ jeongyyonchae adopted! Thank you so much Kak C, i hope you have a nice day! 💖

10 Nov 2025, 02:39 UTC65 viewsread 14 August 2026

Semua usn udah ada harga nya ya, kalian bisa cek, itu harga sementara, bisa naik/turun atau bisa juga jadi NFS sesuai mood ku😁, selagi masih ada harganya di lesgoin ajaaaaaaa😋

10 Nov 2025, 02:28 UTC60 viewsread 14 August 2026

Mentemen, aku masih aktif ya, dan semua usn ku juga masih adaaaa

10 Jun 2025, 05:23 UTC88 viewsread 14 August 2026

@.waomin adoptep! Thank you so much Kak L, i hope you have a nice day💖

9 Jun 2025, 13:04 UTC83 viewsread 14 August 2026

Temen-temen, kalau ingin tanya harga atau lainnya bisa langsung ke bot yaa @asajhibot soalnya kalau di board aku jarang lihat

2 Mar 2025, 05:19 UTC102 viewsread 14 August 2026

Boleh tanya² ya mentemen, kalau malu bisa ke board yang di pinned🫶🏻

2 Mar 2025, 05:18 UTC100 viewsread 14 August 2026

Yeay done rombak

18 Feb 2025, 09:36 UTC106 viewsread 14 August 2026

Sticker

Sticker, posted without a caption

18 Feb 2025, 09:36 UTC97 viewsread 14 August 2026

ㅤㅤㅤㅤ Username Sold ㅤㅤㅤㅤ

18 Feb 2025, 09:36 UTC95 viewsread 14 August 2026

Sticker

Sticker, posted without a caption

Showing the 12 most recent of 20 posts we hold for @kaxlopsia. 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 — 45,341 of 1,481,502entries 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.

Mentions

Named by 54 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Kos blue” (@kaxlopsia), 15 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/kaxlopsia.

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.