Telegram RegisterThe public register of Telegram
Telegram profile photo for sahabat ikan🐠

Channel

sahabat ikan🐠

@sahabatikan

On this record: Growth · Engagement · 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-1003755648543
TypeChannel
Username@sahabatikan
Created11 February 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/sahabatikan

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, 23:342no change
7 Aug 2026, 03:112first reading

Engagement

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

Recent posts

11 Feb 2026, 12:34 UTC307 views0 reactionsread 13 August 2026

🎣bubbyfish friend🐠 🫧 @seyifies 🫧 @juninoPack 🫧 @wolfvyies 🫧 @doulfy 🫧 @typoplum 🫧 @mounrevoir 🫧 @heartsys 🫧 @findthenote 🫧 @westlinne 🫧 @mapwood 🫧 @mittyroll 🫧 @gearpacks 🫧 @joOoyyies 🫧 @shamyse 🫧 @clooudlets 🫧 @rrabbitc 🫧 @pyumbis 🫧 @rinehelper 🫧 @nameideasc 🫧 @cokiiesboom 🫧 @losymaid 🫧 @hamsterials 🫧 @Muythical 🫧 @adourlush 🫧 @hanoous 🫧 @chaeryist 🫧 @plibisanja 🫧 @harviette 🫧 @jolynesy 🫧 @tulipella 🫧 @louriette 🫧

11 Feb 2026, 12:32 UTC250 viewsread 13 August 2026

open moots bisa hubungi @sobatmancingbot sertakan @ch dan @.bothfw hanya menerima ch freebies and helps!! untuk hfw akan dihapus ketika sudah 1×24jam

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

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.

“sahabat ikan🐠” (@sahabatikan), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sahabatikan.

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.