Telegram RegisterThe public register of Telegram
Telegram profile photo for SERDADU PARTNERSHIP

Channel

SERDADU PARTNERSHIP

@serdadupartnership

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

6subscribers

+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-1001383311890
TypeChannel
Username@serdadupartnership
Descriptionconnected to @SERDADUBASE ⎙ : @SERDADUPARTNERBOT
CreatedBetween 1 March 2018 and 26 February 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/serdadupartnership

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 6 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:026no change
7 Aug 2026, 00:156first reading

Engagement

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

Recent posts

4 Nov 2021, 13:14 UTC88 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O8 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. KAMPUNG JAEYONG ㅤ ⎙ : @KAMPUNGJAEYONG ㅤ ⎙ : @KJYMPPSBOT O2. BUMI ㅤ ⎙ : @BUMIOFC ㅤ ⎙ : @ASISTENBUMIBOT O3. 𝐂𝐑𝐘𝐒𝐓𝐀𝐍 𝐒𝐐'𝟏𝟐 ㅤ ⎙ : @CRYSTANSQ ㅤ ⎙ : @MPPSCRYSTANBOT ㅤ • 𝐋𝐎𝐕𝐄 𝐏𝐀𝐂𝐊 ㅤ ⎙ : @L0VEPACK ㅤ • 𝐋𝐀𝐏𝐀𝐊 𝐂𝐑𝐘𝐒𝐓𝐀𝐍 ㅤ ⎙ : @LAPAKCRYSTAN O4. Ɲ𝗘𝗢 𝗕𝗟𝗢𝗢𝗗 𝗗𝗥𝗘𝗔𝗠𝗦 ㅤ ⎙ : @OFCNBD ㅤ ⎙ : @PSNBDAEWBOT ㅤ • STAR …

31 Oct 2021, 08:48 UTC87 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O7 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. 𝐖inata 𝐄vent 𝐎rganizer ㅤ ⎙ : @winataorganizer ㅤ ⎙ : @winatampps_bot O2. 𝗢𝗙𝗖 𝗝𝗔𝗘𝗬𝗢𝗡𝗚 𝗖𝗜𝗧𝗬 ㅤ ⎙ : @ofcJjaeyongcity ㅤ ⎙ : @mppsjaeyongcitybot O3. DISTRICT NCT ㅤ ⎙ : @NCTDOFC ㅤ ⎙ : @DISTRICTMPBOT O4. 𝐌Λ𝐑𝐊Ø𝐆𝐀𝐍𝐊 ㅤ ⎙ : @MARKOGANK ㅤ ⎙ : @TEMANMARKO_BOT O5. KENTHA SQ ㅤ ⎙ : @KENTHASQ ㅤ ⎙ : @kenthamp_bo…

27 Oct 2021, 06:39 UTC74 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O6 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. 𝐎𝐅𝐂 𝐁𝐔𝐓𝐓𝐄𝐑𝐅𝐋𝐘 𝐕𝐈𝐋𝐋𝐀𝐆𝐄 ㅤ ⎙ : @BUTTERFLYVILLAGE ㅤ ⎙ : @PSBV_BOT O2. 𝐓𝐇𝐄 𝐄𝐀𝐒𝐓𝐖𝐎𝐎𝐃 𝐋𝐈𝐎𝐍 𝐁𝐋𝐀𝐂𝐊 ㅤ ⎙ : @OFCTELB ㅤ ⎙ : @Mppstelbbot O3. 𝐊O𝐒A𝐍 𝐓A𝐄J𝐄𝐍 ㅤ ⎙ : @ofckosantaejen ㅤ ⎙ : @mppskstjn_bot O4. 𝐎𝐅𝐂 𝐀𝐑𝐆𝐎𝐒 𝐔𝐍𝐈𝐓𝐄𝐃 ㅤ ⎙ : @argosunited ㅤ ⎙ : @AUNITEDPS_BOT O5. DISTRICT NAEZY ㅤ ⎙ : @naezyofc ㅤ ⎙ : @PSNA…

26 Oct 2021, 04:08 UTC76 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O5 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. CARNEVALE EVENT ORGANIZER ㅤ ⎙ : @CEOFC ㅤ ⎙ : @MPSCARNEVALEBOT O2. ✮‌ - 𝐓𝑹𝑬𝚨N‌CT‌I‌𝐙 ㅤ ⎙ : @OFCTREANCTIZ ㅤ ⎙ : @TAENZMPPS_BOT O3. REGIO KTH ㅤ ⎙ : @REGIOKTH ㅤ ⎙ : @PSREGIOKTHBOT O4. REVOLUSI ㅤ ⎙ : @OFCREVOLUSI ㅤ ⎙ : @REVPSBOT O5. DHAMARĀYU ㅤ ⎙ : @DHAMARAYU ㅤ ⎙ : @DHAMARAYUPSBOT O6. 775 scöt…

25 Oct 2021, 10:12 UTC72 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O4 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. The Bubbles Organizer ㅤ ⎙ : @THEBUBBLESEOOFC ㅤ ⎙ : @PSMPSBUBBLESBOT O2. 𝐎𝐅𝐂 𝐒𝐀𝐑𝐕𝐄𝐆𝐀𝐒🇦🇱 ㅤ ⎙ : @SEINDAHSENYUMANMU ㅤ ⎙ : @SARVEGASMPPSBOT O3. 𝐆𝐀𝐑𝐅𝐈𝐄𝐋𝐀𝐍𝐃 𝐅𝐈𝐑𝐄 ㅤ ⎙ : @GARFIELANDOFC ㅤ ⎙ : @MPPSGFFBOT O4. BANDAR KAJEN ㅤ ⎙ : @BANDARKAJEN ㅤ ⎙ : @MPPSBANDARKAJENBOT O5. SCARLAS ㅤ ⎙ : @SCARLAS ㅤ ⎙ : @S…

25 Oct 2021, 10:12 UTC78 viewsread 12 August 2026

⚔️ LIST PARTNERSHIP @SERDADUBASE. ┏┈┈┈┈┈┈┈┈┈┈┈┓ ↳ HALAMAN O3 ┗┈┈┈┈┈┈┈┈┈┈┈┛ O1. NOMINMARK VILLAGE ㅤ ⎙ : @NMMVILLAGE ㅤ ⎙ : @NMMVPSBOT ㅤ • DISTRICT TRAUMREICH ㅤ ⎙ : @TRAUMREICHOFC ㅤ ⎙ : @NMMVPSBOT ㅤ • NEO CHROME ㅤ ⎙ : @NEOCHROME ㅤ ⎙ : @NMMVPSBOT O2. M A L E (libur) ㅤ ⎙ : @OFFICIALMALE ㅤ ⎙ : @MPPSMALEBOT O3. OFC BE SUCCESSFUL ㅤ ⎙ : @OFFICIALBSGROUP ㅤ ⎙ : @PARTNERBSBOT O4.…

Showing the 12 most recent of 20 posts we hold for @serdadupartnership. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“SERDADU PARTNERSHIP” (@serdadupartnership), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/serdadupartnership.

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.