Telegram RegisterThe public register of Telegram
Telegram profile photo for SEBARLINKK

Channel

SEBARLINKK

@sebarlinkR

On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

4subscribers

-1 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-1002396216595
TypeChannel
Username@sebarlinkR
Created21 September 2024 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live12 October 2026
Measurements held3
Confirmed unchanged4 times, most recently 12 October 2026
On Telegramt.me/sebarlinkR

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 3 October 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

454.57 August 2026 — 5 subscribers13 August 2026 — 5 subscribers9 September 2026 — 4 subscribers7 August 20269 September 2026
3 measurements spanning 33 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 4–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 06:164-1
13 Aug 2026, 02:485no change
7 Aug 2026, 13:415first reading

Engagement

2 posts held, back to 21 September 2024 — 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 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 2 posts for this entry, the most recent from 21 September 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Sept 2024, 11:47 UTC≈26,500 viewsread 13 August 2026

🔺 🔔💥🔥🔆💧𝗔𝗖𝗖 𝗦𝗘𝗥𝗘𝗡𝗧𝗔𝗞!! 🔺🔺 𝐖𝐎𝐖𝐎𝐖𝐎 @OFCRASIOVEGASS 𝐋𝐀𝐆𝐈 𝐎𝐏𝐄𝐍 𝐌𝐄𝐌 𝐍𝐈𝐇𝐇𝐇 𝐀𝐘𝐎 𝐉𝐎𝐈𝐍𝐍 𝐓𝐔𝐍𝐆𝐆𝐔 𝐀𝐏𝐀 𝐋𝐀𝐆𝐈𝐈 ❔❔mau masuk sq tapi takut? gass langsung masuk ke cc ini aja, cc tapi keren kaya sq && anti kacang rebus💠💠 https://t.me/+7KzWs6A103A5NGM1 https://t.me/+7KzWs6A103A5NGM1 https://t.me/+7KzWs6A103A5NGM1 𝑨𝒀𝑶 𝑺𝑨𝒀𝑨𝑵𝑮 𝑱𝑶𝑰𝑵𝑵 ♦️ 𝑪𝑪 𝑪𝑬𝑪𝑨𝑵 𝑪𝑶𝑮𝑨𝑵, 𝑴𝑨𝑺𝑨 𝑮𝑨𝑴𝑨𝑼 𝑱𝑫𝑰 𝑺𝑨𝑳𝑨𝑯 𝑺𝑨𝑻𝑼𝑵𝒀𝑨?? 🤭🤭 COLLAB TERUS + MAPII EVERYDAYYY GUYYSS🔺 ❗️➥𝐟𝐫𝐞𝐞 𝐜𝐢𝐧𝐥…

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

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.

“SEBARLINKK” (@sebarlinkR), 4 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/sebarlinkR.

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.