Telegram RegisterThe public register of Telegram

Channel

PARTNERSHIP KADIN

@kadinpartner

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

3subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001544526864
TypeChannel
Username@kadinpartner
CreatedBetween 1 August 2021 and 13 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/kadinpartner

Growth

310 August 2026 — 3 subscribers13 August 2026 — 3 subscribers10 August 202613 August 2026
2 measurements spanning 3 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 17:323no change
10 Aug 2026, 22:463first reading

Engagement

20 posts held, back to 13 December 2021the 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 27 December 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
2

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

27 Dec 2021, 01:19 UTC171 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 11 ▬▬▬▬▬▬ ➕ O1. ↳@ofccadenzagnk ➣ @mppscdz_bot O2. ↳ ➣ O3. ↳ ➣ O4. ↳ ➣ O5. ↳ ➣ O6. ↳ ➣ O7. ↳ ➣ 08. ↳ ➣ O9. ↳ : ➣ 1O. ↳ ➣

18 Dec 2021, 08:54 UTC149 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 10 ▬▬▬▬▬▬ ➕ O1. ↳ @OFCVAGARYSQ @OFCVAGARYHOSPITAL @OFCVAGARYBAR ➣ @ofcvagarymppsbot O2. ↳ @ArikaHospital @JASAKURIRRP @SPARKLINGACADEMY ➣ @mppsunitbot O3. ↳ @kotabujang ➣ @pskotabjbot O4. ↳ @ARCALAPATI ➣ @arcalapatiMpps_bot O5. ↳ @LANGUEPAISACD ➣@LANGUEPAISPS_BOT O6. ↳ @LEIDTERS ➣@SAPIENSPSBOT O7. ↳@luxuryDWO ➣ @ldwompp

14 Dec 2021, 05:43 UTC123 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 9 ▬▬▬▬▬▬ ➕ O1. ↳ @OFCDUNRIDE ➣ @DUNRIDEPSBOT O2. ↳ @QuinciasOfc ➣ @MondiasMppsbot O3. ↳ @OFCVANTEJEN ➣ @VTJENROBOT O4. ↳ @OFCWIZCT ➣ @wizctmppsbot O5. ↳ @Inf1nitySpace @HitlerBase ➣@AceMpsBot O6. ↳ @OFCDRAXERTY ➣ @DRAXERTYPSBOT O7. ↳ @OFCKILLERDARKSIDE ➣ @partnershipkdsbot 08. ↳ @OFCKAVILAR ➣ @MPPSKAVILAR_BOT O9. ↳ @JaeroseCentury ➣ @Ja

13 Dec 2021, 12:23 UTC103 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 8 ▬▬▬▬▬▬ ➕ O1. ↳ @ofckingkth ➣ @KGKTHmppsbot O2. ↳ @CBROYAUME ➣ @CBRMPPSROBOT O3. ↳ @vkjrenhome ➣ @mppsvkjrhome_bot O4. ↳ @KANIGARATEAM ➣ @KANIGARAMPPS_BOT O5. ↳ @ofccastor ➣@castorpsbot O6. ↳ @galaxyinternasional ➣@MpHexIntUn_bot O7. ↳@gorasixofc @snacthofc ➣ @gorshipbot 08. ↳ @EAGLECAVEOFC ➣ @ofcmppsecv_bot O9. ↳ @VRXDUOFC ➣ @WSTPARTNER_

13 Dec 2021, 10:06 UTC75 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 7 ▬▬▬▬▬▬ ➕ O1. ↳ @OVERKILLOFC ➣ @OVERKILLSROBOT O2. ↳ @AGORAOFC ➣ @mpagorabot O3. ↳ @EAGLEREDD ➣ @HUNTEREAGLEPS_BOT O4. ↳ @ARSENICEO ➣ @ARSENICPARTNERBOT O5. ↳ @HWEOFC ➣@MPPSMWEBOT O6. ↳ @ofcdmcl ➣@Mppsdrmscstl_bot O7. ↳@LesserEvilCH @LesserEvilEO ➣ @MppsLe_bot 08. ↳ @ECLADCORP @ECLAD @ECLADELIVERY @BLACKSWANEO

13 Dec 2021, 06:56 UTC64 viewsread 13 August 2026

PARTNERSHIP KADIN ➕▬▬▬▬▬▬ 5 ▬▬▬▬▬▬ ➕ O1. ↳ @NEOJOURNEY ➣ @MPPSJNEOBOT O2. ↳ @JAEROSETOWN @ROSEANNETOWN ➣ @JAEROSETOWNMPPS_BOT O3. ↳ @gkthmu @ofcttaennie ➣ @gkthmpps_bot O4. ↳ @OFCALESTRA @OFCAROCE ➣ @MPPSALESTRA_BOT O5. ↳ @grixenchannel ➣@grixenmppsbot O6. ↳ @MIGHTYKINGSKTH ➣@mppsmkkthbot O7. ↳@SERDADUBASE ➣ @SERDADUPARTNERBOT 08. ↳ @YERIJAEMARK

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

“PARTNERSHIP KADIN” (@kadinpartner), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/kadinpartner.

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.